CTFL-v4 Managing the Test Activities Practice Question
You are the Test Manager for an agile team delivering a mobile insurance claims app. The team tracks progress using a burn-down chart of test execution tasks and a defect report grouped by severity. At the sprint review, the Product Owner asks for a single indicator showing whether the remaining open defects are likely to block the sprint goal. Which test management artifact is MOST appropriate to present?
⚠ Common exam trap
The trap here is assuming that any defect-related chart satisfies a request about defect risk, when only a severity- and status-grouped view exposes unresolved blocking defects.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A defect status report showing open defects by severity and their resolution status.
The Product Owner needs an indicator of whether remaining defects threaten the sprint goal. A defect status report showing open defects by severity and resolution status directly exposes unresolved high-severity items that could block delivery, making it the most relevant artifact. Execution charts, density metrics, and full summary reports describe activity or aggregate quality but do not isolate the blocking risk.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A defect status report showing open defects by severity and their resolution status.
Why this is correct
A defect status report groups open defects by severity and resolution state, which directly reveals whether high-severity defects remain unresolved and could block the sprint goal. This gives the Product Owner a focused view of outstanding risk rather than general execution progress.
- ✗
A test summary report listing all test cases executed and their pass/fail status.
Why it's wrong here
A test summary report gives an overall assessment of testing against exit criteria, but a list of executed cases and their status does not isolate the open defects that threaten the sprint goal. Presenting it would bury the risk information the Product Owner asked for inside broader execution statistics.
- ✗
A defect density report showing defects per module of the claims app.
Why it's wrong here
Defect density reports defects relative to module size and is useful for comparing quality across components, but it does not show whether the currently open defects are severe enough to block the sprint goal. It aggregates historical data rather than the immediate risk profile the Product Owner needs for the release decision.
- ✗
A test progress burn-down chart showing the number of open test cases per day.
Why it's wrong here
A test progress burn-down chart tracks remaining test execution tasks over time, so it shows testing activity but not the risk that open defects pose to the sprint goal. Because the Product Owner specifically asks whether remaining defects will block delivery, this chart answers a different question and would leave the blocking risk invisible.
Visual reference
About these practice questions
This CTFL-v4 question is part of Courseiva's 144-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.