Courseiva
Testing Throughout the SDLC →mediumMultiple Choice

CTFL-v4 Testing Throughout the SDLC Practice Question

Which of the following describes the 'Testing' activity in the context of the V-model?

⚠ Common exam trap

Candidates often think V-model testing happens only after coding is complete, ignoring the fact that the V-model maps testing activities to every development phase, including requirements.

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

✓

Testing activities correspond to specific development phases, starting at the requirements level.

The V-model emphasizes the relationship between each development phase and a corresponding testing phase. In this model, testing is not just a final stage; it is a parallel activity that starts with planning and design. This ensures that every development requirement has a corresponding verification method, providing a structured approach to quality assurance throughout the entire SDLC.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Testing is a distinct phase that occurs only after the final system integration.

    Why it's wrong here

    In the V-model, testing occurs throughout the SDLC. Each phase—from requirements to coding—has a corresponding testing level (e.g., acceptance testing for requirements, system testing for architecture, and component testing for code). Limiting testing to the final integration phase is a misunderstanding of the V-model's structure.

  • ✓

    Testing activities correspond to specific development phases, starting at the requirements level.

    Why this is correct

    The V-model explicitly maps each development phase to a testing level. Requirements analysis is verified by acceptance testing, design by system testing, and so on. This alignment ensures that testing starts early, is traceable to requirements, and provides a clear mechanism for verifying the system at every level.

  • ✗

    Testing is used solely for defect detection at the very end of the development process.

    Why it's wrong here

    The V-model is designed to prevent defects by incorporating testing early. By planning and designing tests alongside the development phases, teams can verify specifications early. Focusing only on defect detection at the end ignores the prevention benefits of the V-model, which is the primary purpose of the structure.

  • ✗

    Testing consists only of the execution of automated scripts against the finished code.

    Why it's wrong here

    The V-model includes static testing activities like reviews of documents and specifications. Limiting testing to automated script execution against code is incomplete, as it ignores the critical role of static analysis in ensuring that requirements and design are sound before the expensive coding process even begins.

About these practice questions

One of 144 original CTFL-v4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.