CTFL-v4 Test Analysis and Design Practice Question
When applying decision table testing, what should you do if the number of combinations is extremely high?
⚠ Common exam trap
Candidates assume they must test every single permutation even if it leads to redundant results, failing to apply simplification techniques that maintain coverage while reducing the overall test suite size.
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
✓
Simplify the table by merging equivalent rules.
When the number of combinations in a decision table becomes unmanageable, testers should use techniques to simplify the table. This involves identifying redundant conditions or grouping inputs that lead to the same result. Simplification ensures the test suite remains feasible while still covering all essential logic. This balance is crucial for maintaining testing efficiency without sacrificing the thoroughness required to find defects in complex logical processes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Test only the most common combinations.
Why it's wrong here
Testing only common combinations is a high-risk strategy that likely leaves critical, rare-path defects unfound. A better approach is to simplify the table by consolidating rules or removing redundant conditions, rather than arbitrarily excluding large portions of the logical space that the business requirements define as part of the functionality.
- ✓
Simplify the table by merging equivalent rules.
Why this is correct
Simplification is the correct approach to manage complexity. By identifying rules that yield the same outcome and merging them, you keep the test suite size manageable without losing logical coverage. This keeps the testing process rigorous and efficient, ensuring that all unique paths are tested while eliminating unnecessary redundancy.
- ✗
Abandon decision tables and switch to random testing.
Why it's wrong here
Switching to random testing is an ineffective way to handle complex logic. Random testing lacks the structure and repeatability required to verify specific business rules. If a decision table is too large, the correct solution is to refine the design or simplify the model, not to discard structured testing altogether.
- ✗
Only test the boundary conditions.
Why it's wrong here
Boundary value analysis is a different technique with a different purpose. While it is useful, it does not replace the logical coverage provided by a decision table. Relying solely on boundaries when complex business logic is involved will miss defects related to internal rule interactions, leading to an incomplete test design.
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 →
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.