CTFL-v4 Static Testing Practice Question
A software company is adopting static testing to reduce defect leakage. Which of the following scenarios best demonstrates the primary benefit of static testing over dynamic testing?
⚠ Common exam trap
Candidates often focus on the 'speed' of static testing rather than the 'cost-effectiveness' of catching defects before they are implemented into code.
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
✓
A peer review of a technical specification document reveals an ambiguity that would lead to incorrect business logic.
Static testing finds defects early in the software development lifecycle, significantly reducing the cost of remediation compared to dynamic testing. By reviewing documentation, code, or requirements before execution, teams prevent defects from propagating into later phases. This approach improves overall software quality by addressing root causes in artifacts rather than just identifying symptoms in the running system, which is crucial for early risk mitigation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The testing team executes a test script to identify a logic error in the billing module.
Why it's wrong here
Executing test scripts is a form of dynamic testing, which occurs after the code is built. While this identifies the logic error, it does not represent the unique advantage of static testing, which is the ability to find defects without executing the code in a runtime environment.
- ✗
Developers perform unit tests to verify that the API endpoints handle null inputs correctly.
Why it's wrong here
Unit testing is a dynamic testing technique that requires code execution to verify behavior. Although beneficial for identifying defects, it does not demonstrate the static testing advantage of identifying issues in requirements or designs before any code is ever written or compiled for execution.
- ✓
A peer review of a technical specification document reveals an ambiguity that would lead to incorrect business logic.
Why this is correct
This scenario highlights the core benefit of static testing: identifying defects early in the development lifecycle before code is written. By catching the ambiguity in the design phase, the team avoids the high cost of rework that would occur if the defect were discovered during dynamic testing.
- ✗
A performance tool monitors system latency to ensure compliance with non-functional requirements.
Why it's wrong here
Performance monitoring is a dynamic technique that relies on system execution under load. This is useful for validating the system's runtime characteristics but does not provide the preventive benefits of static testing, which focuses on reviewing project artifacts prior to the existence of an executable system.
About these practice questions
This CTFL-v4 question is part of Courseiva's 144-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.