CTFL-v4 Test Analysis and Design Practice Question
During Test Design, you notice that a specific function has very high cyclomatic complexity. Which black-box technique is most appropriate to help ensure sufficient coverage?
⚠ Common exam trap
Candidates often assume that high cyclomatic complexity requires only white-box testing, ignoring that black-box techniques like decision tables are essential for validating the intended business logic.
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
✓
Decision table testing
When dealing with high cyclomatic complexity, white-box techniques like branch testing are often used, but black-box techniques like decision table testing are equally important to ensure the business logic represented by that complexity is correctly implemented. By using a decision table, you can systematically break down the logical paths, ensuring all combinations are covered, which helps manage the risks associated with complex, branching code that is difficult to test thoroughly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Decision table testing
Why this is correct
Decision table testing is excellent for managing high complexity. It maps all combinations of inputs and conditions, ensuring that every logical path is identified and tested. This is essential for complex functions where traditional ad-hoc testing would likely leave large sections of the logic unexercised and unverified.
- ✗
Error guessing
Why it's wrong here
Error guessing is an ad-hoc, experience-based technique. It lacks the systematic approach required to cover high cyclomatic complexity. Relying on intuition when the underlying logic is complex is a poor strategy, as it often overlooks many of the possible logical paths that a structured technique would catch.
- ✗
Exploratory testing
Why it's wrong here
Exploratory testing is useful for uncovering unknown issues, but it is not a primary technique for ensuring comprehensive coverage of complex logical branches. Because it is highly dependent on the tester's current focus, it is insufficient as a standalone method for dealing with high cyclomatic complexity in critical modules.
- ✗
User story mapping
Why it's wrong here
User story mapping is a planning and requirements activity, not a test design technique. It helps organize features but does not provide a framework for testing the logical branches created by high cyclomatic complexity within the code. It is entirely unsuitable for verifying the correctness of functional logic.
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.