CTFL-v4 Managing the Test Activities Practice Question
During a banking application project, the test manager notices that defect density in the payment module is twice as high as expected. How should the test manager apply risk-based testing to adjust the test plan?
⚠ Common exam trap
Candidates often choose 'stop testing' or 'immediately fix all defects.' These are not risk-based strategies; they ignore the need to re-evaluate priorities based on the new data about defect density.
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
✓
Analyze the high defect density to update risk assessments, prioritize additional testing on identified high-risk payment features, and inform stakeholders.
Risk-based testing involves prioritizing test execution based on product risks. When defect density spikes in a critical module, the test manager must re-evaluate product risks and redirect testing effort to find remaining failures. This ensures quality focus remains aligned with business exposure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immediately halt all testing across other modules and reallocate all resources exclusively to writing manual regression test scripts for the payment module.
Why it's wrong here
Halting all testing elsewhere creates blind spots in other modules that might also harbor critical defects. Resource reallocation should be targeted and proportional based on assessed risk levels rather than an extreme, blanket operational shutdown.
- ✓
Analyze the high defect density to update risk assessments, prioritize additional testing on identified high-risk payment features, and inform stakeholders.
Why this is correct
Risk-based testing uses observed defect density as an input to reassess likelihood. Updating risk assessments, re-prioritising testing toward the high-risk payment features, and informing stakeholders turns the metric into adjusted test effort, which is the prescribed response.
- ✗
Delegate all defect root cause analysis entirely to the software development team while continuing test execution strictly according to the initial schedule.
Why it's wrong here
Risk-based testing requires the test manager to re-prioritise and reallocate test effort toward the high-defect payment module; delegating analysis and holding the schedule leaves that risk untreated. It tempts because developers do fix root causes, but that is remediation, not test-plan adjustment.
- ✗
Reduce the entry criteria for the payment module to allow faster sign-off and recover lost project schedule time without altering test coverage.
Why it's wrong here
Lowering entry criteria lets defective code enter testing sooner without adding coverage, so the elevated payment-module risk stays unmitigated and defects escape. It tempts when schedule pressure dominates, yet risk-based testing responds to high defect density by increasing, not relaxing, scrutiny of that module.
About these practice questions
Courseiva writes every CTFL-v4 question from scratch — 144 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.