CTFL-v4 Managing the Test Activities Practice Question
Which of the following metrics is the most effective for a test manager to report the current status of defect discovery and resolution during the monitoring phase?
⚠ Common exam trap
Candidates select static metrics like 'total defects found,' which do not account for the progress or velocity of the testing effort relative to the project timeline.
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
✓
Defect arrival and resolution rate trends over time.
Defect arrival and resolution rates provide a clear picture of the testing trajectory and software stability. Monitoring these metrics allows the test manager to identify trends, such as whether defect discovery is plateauing or if resolution is lagging behind discovery, enabling informed decisions regarding exit criteria and release readiness as per ISTQB standards for project control.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Total number of test cases executed against the total number of planned test cases.
Why it's wrong here
Test execution progress measures throughput but fails to indicate software quality. High execution rates might occur even if the software is severely buggy. Monitoring test progress without considering defect trends provides a misleading sense of readiness, as it ignores the actual stability and reliability of the system under test.
- ✓
Defect arrival and resolution rate trends over time.
Why this is correct
This trend analysis is critical for assessing the stability of the software. A high defect arrival rate combined with a slow resolution rate indicates significant stability issues. Tracking these metrics over time helps the test manager determine if the system is approaching a state where it is ready for release.
- ✗
The number of hours spent by developers on debugging.
Why it's wrong here
While this metric reflects developer effort, it does not directly correlate with software quality or testing progress. Debugging time can vary significantly based on developer experience or code complexity. It is an internal development metric rather than a test management metric used to assess the effectiveness of the testing process.
- ✗
The total number of requirements identified in the SRS document.
Why it's wrong here
Tracking the count of requirements is a project management or business analysis task rather than a test management task. It does not provide insight into testing progress, defect density, or the quality of the software build. It fails to show if the features are actually working as intended currently.
About these practice questions
One of 144 original CTFL-v4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.