CTFL_Syll_4.0 Exam Dumps : ISTQB Certified Tester Foundation Level (CTFL) v4.0

Comprehensive and Detailed Explanation From Exact Extract:

This is a classic application of theDecision Table Testingtechnique.

We are combining two conditions:

Purchase Volume, which has3 equivalence classes:

1 to 100 units → 0%

101 to 1000 units → 5%

More than 1000 units → 10%

Customer Type, which has2 categories:

Frequent Customer = YES → 5% extra

Frequent Customer = NO → 0%

This gives:

3 (bulk discount levels) × 2 (frequent customer options) = 6 unique decision rules

Each combination of these input conditions defines a separate test scenario with its own outcome.

“Decision table testing is used to identify the different combinations of inputs and their associated outputs. Each unique combination of input values defines a rule.”

(ISTQB CTFL Syllabus v4.0, Section 4.2.3 – Decision Table Testing, Page 40)

Thus,Option D (6 decision rules)is the correct answer.

The statement that the shift-left approach can only be implemented with test automation is false. The shift-left approach emphasizes early testing activities in the software development lifecycle to detect and address defects as soon as possible. While test automation can support shift-left practices, it is not the only method. The shift-left approach can also involve practices such as static analysis, early requirement reviews, and integrating security vulnerability assessments early in the development process.

This answer is correct because product risks are risks that affect the quality of the software product, such as defects, failures, or non-compliance with requirements or standards. Project risks are risks that affect the project’s schedule, budget, resources, or scope, such as delays, cost overruns, skill gaps, or scope changes. In this case, [I] and [IV] are product risks, as they relate to the accessibility and security of the software product, which are quality attributes. [II] and [III] are project risks, as they relate to the delivery time and the test automation skills of the test team, which are project factors. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.1.1.1