ISTQB CTAL-TM Exam With Confidence Using Practice Dumps

In Agile, defects discovered within the same sprint may be fixed without formal reports, but:

“Defect reports are typically required for defects that cannot be fixed immediately, require additional discussion, or involve external parties.”

—ISTQB CTFL Syllabus 2018, Section 3.2.4

Thus,Option Ais the accurate and practical reflection of Agile defect handling.

Context Analysis:

Heavyweight risk-based techniques involve thorough, detailed analyses to identify and mitigate potential risks comprehensively.

Hazard analysis is a structured method to identify and address risks, commonly used in safety-critical domains.

Evaluation of Options:

A. Systematic software testing:

Incorrect. While methodical, it is not inherently a risk-based technique.

B. Pragmatic risk analysis:

Incorrect. This is a lightweight technique emphasizing practical application over detailed analysis.

C. Brainstorming:

Incorrect. While useful for generating ideas, it is not detailed enough to qualify as heavyweight.

D. Hazard analysis:

Correct. It is a formal and comprehensive approach, qualifying as a heavyweight technique.

Syllabus Alignment:

ISTQB highlights hazard analysis as a detailed, structured risk-based technique (TM-1.3.4).