CTFL-v4 Fundamentals of Testing Practice Question
What is the primary benefit of performing 'confirmation testing' after a defect has been fixed?
⚠ Common exam trap
Candidates often confuse confirmation testing with regression testing, incorrectly believing it is meant to check the whole system rather than specifically verifying the fix for a known defect.
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
✓
To ensure the specific defect is resolved as expected.
Confirmation testing is essential to verify that the fix actually resolved the reported failure and that no further issues were introduced by the fix itself. This ensures the defect is truly closed and the system behaves as expected. Without this step, teams risk assuming a fix works when it may have been incomplete or unsuccessful, leading to wasted time and increased frustration when the same issue is discovered again in production.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To find new, unrelated defects in the system.
Why it's wrong here
Finding new, unrelated defects is the role of regression testing or general feature testing. While confirmation testing might reveal an issue, its specific and primary goal is to verify the efficacy of a fix for a previously identified and reported defect, not general defect discovery.
- ✓
To ensure the specific defect is resolved as expected.
Why this is correct
The sole purpose of confirmation testing is to verify that the original failure reported by the test is no longer occurring. This gives the team confidence that the fix implemented by the developer successfully addresses the identified problem and meets the expected behavior specified in the requirements.
- ✗
To estimate the time required for future test cycles.
Why it's wrong here
Confirmation testing does not provide metrics relevant to estimating future test cycles. It is a targeted activity for defect verification. Estimation is usually handled during the test planning phase by analyzing historical data and the complexity of the features, not by simply performing a verification pass.
- ✗
To test the system's performance under heavy load.
Why it's wrong here
Performance testing is a specific type of non-functional testing designed to check system response times and scalability. Confirmation testing is a functional verification process. Confusing these two types of testing leads to improper resource planning and a failure to address the specific objectives of each test type.
Visual reference
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.