CTFL-v4 Testing Throughout the SDLC Practice Question
What is the primary objective of static testing in the software development lifecycle?
⚠ Common exam trap
Candidates often confuse static testing with 'manual testing'. They assume static testing is just manual execution, ignoring the crucial aspect that code is not executed at all.
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 find defects in the software before it is executed.
The main goal of static testing is defect prevention. By identifying issues in documentation, requirements, and design early, it prevents these errors from being translated into software defects. This is highly efficient, as it is much cheaper to fix a requirement error on paper than a bug in the code, contributing significantly to overall project quality and cost-effectiveness.
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 identify performance issues that might impact system scalability.
Why it's wrong here
Performance issues are evaluated through dynamic testing, such as load or stress testing, where the code is actually running. Static testing, by definition, does not involve executing software, so it cannot be used to measure runtime performance characteristics or identify bottlenecks in system scalability or resource utilization.
- ✓
To find defects in the software before it is executed.
Why this is correct
Static testing aims to find defects in work products other than the executable code, such as requirements documents, design specifications, or test plans. Finding these defects early prevents them from propagating into the implementation phase, which is a fundamental and proactive aspect of the testing process.
- ✗
To verify that the software meets all functional requirements through execution.
Why it's wrong here
Verifying that the software meets functional requirements through execution is the definition of dynamic testing. Static testing is concerned with analyzing documents and code without execution. Therefore, this option incorrectly identifies the primary method and objective of static testing, which is primarily focused on prevention and early verification.
- ✗
To generate test data for future automated testing sessions.
Why it's wrong here
While static testing can help define the requirements for test data, it is not the primary objective of the process itself. The generation of test data is a separate preparation task within the test design process, not the purpose of static testing, which focuses on evaluating work products for defects.
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.