CTFL-v4 Fundamentals of Testing Practice Question
Which TWO of the following are examples of static testing?
⚠ Common exam trap
Candidates often select dynamic testing activities like component integration or user acceptance testing because they overlook the core definition of static testing as code or document review without execution.
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 technical review of a requirements document.
Static testing involves examining documents or code without executing the software. It allows for early defect detection, which is significantly cheaper than finding bugs during execution. Common static testing techniques include formal reviews, walkthroughs, and static analysis. These activities help improve the quality of the requirements and the design before the coding phase begins, ultimately reducing the cost and effort of the entire software development lifecycle by preventing errors from being introduced into the codebase.
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 test cases on the system.
Why it's wrong here
Executing test cases is a form of dynamic testing, not static. It requires the software to be running. Static testing is defined by the absence of code execution, focusing instead on documentation, design diagrams, or source code analysis to find errors before the system is actually built or deployed.
- ✓
A technical review of a requirements document.
Why this is correct
A technical review is a form of static testing because it analyzes documentation to find defects in the requirements. This prevents errors from propagating into the design and code. By checking for clarity, consistency, and completeness early, the team avoids building the wrong feature and reduces costly rework down the line.
- ✓
Using automated tools for static code analysis.
Why this is correct
Static analysis tools examine source code for coding standard violations, security vulnerabilities, or unreachable code without actually running the program. This is a classic example of static testing, as it identifies potential bugs at a very early stage of development, allowing developers to correct issues before the code is compiled.
- ✗
Running a performance load test.
Why it's wrong here
Performance load testing is a dynamic activity that measures system behavior under simulated stress. It requires the application to be running in an environment. Since it involves executing the software to gather metrics, it is categorized as dynamic testing, not static testing, and is performed after the system is implemented.
- ✗
Performing user acceptance testing.
Why it's wrong here
User acceptance testing is a dynamic testing phase performed by users to ensure the software is fit for purpose. Because it involves interacting with the running software to validate requirements, it is a form of dynamic testing, which is distinct from static techniques like reviews or static code analysis.
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.