CTFL-v4 Managing the Test Activities Practice Question
Which TWO of the following are examples of test-monitoring metrics that a test manager should track?
⚠ Common exam trap
Candidates often select 'number of test cases written' or 'total defects found' as metrics. These are static counts that do not show progress or quality trends, unlike execution percentage and defect resolution ratios.
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
✓
Percentage of test cases executed.
Monitoring metrics provide objective evidence of project status. By tracking test execution progress and defect density, a manager can identify whether the testing effort is sufficient and if the software quality is improving. These metrics are fundamental for reporting to stakeholders, justifying decisions, and identifying the need for corrective action to keep the project on track and within the defined quality boundaries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Percentage of test cases executed.
Why this is correct
Tracking the percentage of test execution gives a clear view of how much of the planned work has been accomplished. This is a critical metric for understanding the schedule status and identifying if the team is behind, on track, or ahead of the projected timeline for the testing phase.
- ✗
Number of coffee breaks taken by the team.
Why it's wrong here
Coffee breaks are irrelevant to project metrics and quality assurance. Monitoring such data is invasive, unprofessional, and provides no insight into the testing effectiveness or the quality of the software. It can significantly damage team morale and trust, which are essential for a high-performing and collaborative testing organization.
- ✓
Number of defects found vs. number of defects resolved.
Why this is correct
This metric highlights the defect lifecycle and the stability of the software. If defects are being found much faster than they are being fixed, it indicates a bottleneck in the development process and a potentially unstable system, which the test manager must address to ensure the project remains on schedule.
- ✗
The favorite programming language of each tester.
Why it's wrong here
Personal preferences like programming language are not relevant to test management. While it is good to know a team's skills, this is not a monitoring metric for project progress or software quality. Including this in a status report is unprofessional and distracts from the actual goals of the test management process.
- ✗
The total cost of office supplies for the year.
Why it's wrong here
While budgeting for office supplies is an administrative cost, it is not a test-monitoring metric. Test monitoring should focus on software quality and the progress of the testing activities themselves. Tracking office supply costs does not help in understanding the defect density or the readiness of the system for release.
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.