CTFL-v4 Managing the Test Activities Practice Question
Which of the following actions is a typical 'corrective action' taken by a test manager during Test Control?
⚠ Common exam trap
Candidates often choose 're-running all tests' or 'reporting the status to the client.' While these are activities, they are not 'corrective actions' designed to fix a specific project delay.
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
✓
Reallocating team members from low-priority tasks to address critical delays.
Corrective actions aim to bring the project back in line with the test plan. If a test phase is delayed, the manager must act decisively. Reallocating resources, extending the schedule, or narrowing the test scope are all standard management responses. These actions ensure that the team focuses on high-value tasks, maintaining project control even when unforeseen challenges threaten the original delivery plan.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Permanently deleting the original test plan to start over.
Why it's wrong here
Deleting a test plan is not a corrective action; it is a failure of project management. A plan should be updated or revised, not destroyed. Starting over causes massive delays and loss of historical data, which is contrary to the ISTQB goal of maintaining traceability and effective process documentation.
- ✓
Reallocating team members from low-priority tasks to address critical delays.
Why this is correct
Reallocating resources is a standard corrective action. By shifting staff from less urgent areas to address bottlenecks, the test manager optimizes the use of available capacity to meet the most pressing project needs. This keeps the project moving toward completion while managing the most critical risks effectively.
- ✗
Increasing the number of meetings to discuss project history.
Why it's wrong here
Increasing meeting frequency often decreases productivity and consumes valuable time that could be spent on testing. This is not a corrective action for project delays; it is a common management mistake that adds overhead without resolving the underlying technical or schedule issues causing the testing project to fall behind.
- ✗
Ignoring the defects until the end of the project.
Why it's wrong here
Ignoring defects is a highly dangerous practice that leads to late-stage discovery of critical failures. Corrective action requires addressing the root causes of issues promptly. Postponing defect resolution until the end of the project makes them significantly more expensive to fix and threatens the quality of the final software product.
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.