CTFL-v4 Testing Throughout the SDLC Practice Question
Which of the following activities best demonstrates the ISTQB principle of 'Testing provides early feedback'?
⚠ Common exam trap
Candidates often confuse 'early feedback' with 'early execution' of automated tests, failing to realize that static testing (reviews) is the most effective way to provide feedback before any code exists.
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
✓
Reviewing user stories and acceptance criteria during the sprint planning session.
Early feedback is the core of shift-left testing. By performing static testing on documents like requirements or design specifications, testers identify defects before a single line of code is written. This is more efficient and cost-effective than finding defects during dynamic testing, as it prevents the cost of rework and ensures that quality is built into the product from the very start of development.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Executing automated regression tests at the end of each daily build.
Why it's wrong here
Regression testing is a form of dynamic testing that happens after code is produced. While it provides feedback, it is not considered 'early' because it occurs after implementation has already started or completed for that specific feature, missing the opportunity to prevent defects at the design stage.
- ✓
Reviewing user stories and acceptance criteria during the sprint planning session.
Why this is correct
Reviewing requirements during planning is a classic example of static testing. It provides immediate feedback to the product team, allowing them to clarify requirements, identify missing test conditions, and ensure the criteria are measurable. This activity prevents defects from being injected into the development process later on.
- ✗
Conducting a performance test on the integrated system before the final release.
Why it's wrong here
Performance testing at the end of the SDLC is late-stage testing. While important for validating the system, it does not provide 'early' feedback. Problems found at this stage are significantly more expensive and time-consuming to fix because they often require deep architectural changes or complex code refactoring.
- ✗
Reporting defects found during the User Acceptance Testing (UAT) phase.
Why it's wrong here
UAT occurs at the very end of the SDLC. Defects discovered at this stage are the most expensive to resolve because they require changes to finished software. Providing feedback this late does not adhere to the principle of early testing or minimizing the cost of quality.
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.