CTFL-v4 Test Analysis and Design Practice Question
Which THREE of the following are benefits of using decision tables in test design?
⚠ Common exam trap
Candidates often assume decision tables are only for code coverage, missing that their primary value is in clarifying business logic and finding requirement gaps.
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
✓
They explicitly force the definition of business rules.
Decision tables are powerful tools for managing complexity. They force the explicit definition of business rules, ensuring that all logical combinations are accounted for. By providing a clear, tabular view of conditions and actions, they enable testers to identify gaps in requirements, simplify complex logic into testable scenarios, and ensure high-quality documentation. This structured approach significantly reduces ambiguity and helps prevent defects that arise from misunderstood business logic in the implementation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
They explicitly force the definition of business rules.
Why this is correct
Decision tables require the tester to map inputs to outputs, which forces a clear definition of the underlying business logic. This process often reveals ambiguities or missing requirements in the initial documentation, leading to a much more robust understanding of the expected system behavior before testing begins.
- ✗
They are the primary tool for measuring code coverage metrics.
Why it's wrong here
Decision tables are a black-box test design technique for functional validation, not for measuring internal code coverage. Metrics like branch or statement coverage are derived from white-box analysis, which examines the source code structure rather than the business logic defined in a decision table.
- ✓
They help identify missing or contradictory requirements.
Why this is correct
Constructing a decision table requires considering all possible combinations of conditions. If a combination leads to an undefined state, the tester immediately identifies a missing requirement. If two combinations lead to conflicting outputs, a contradiction is exposed, allowing for resolution before development or testing proceeds further.
- ✗
They guarantee that every line of source code is executed.
Why it's wrong here
No black-box technique can guarantee complete code execution. Decision tables focus on functional requirements, not the internal pathways of the code. Achieving full code coverage requires structural (white-box) analysis, whereas decision tables ensure logical coverage of the business rules defined in the system specification.
- ✓
They simplify the representation of complex logical dependencies.
Why this is correct
Complex logical systems often suffer from 'combinatorial explosion,' making them hard to document using text. Decision tables condense these dependencies into a readable grid, making it significantly easier to design and maintain test cases that cover all necessary logical outcomes without becoming overwhelmed by the complexity.
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.