CTFL-AcT Exam Dumps : ISTQB Certified Tester - Acceptance Testing (CT-AcT)

ISO/IEC 25010 defines two key quality models:

Product Quality Model (e.g., Usability, Security, Portability)

Quality in Use Model — which includes characteristics of the user’s experience when interacting with the product in a real-world context.

The four main characteristics of the Quality in Use model are:

Effectiveness

Efficiency

Satisfaction

Freedom from risk

Option A — Efficiency is one of the key Quality in Use characteristics, as it refers to the resources used to achieve goals with accuracy and completeness.

Other options:

B (Usability), C (Compatibility), and D (Portability) are characteristics of the Product Quality Model, not of Quality in Use.

Therefore, the correct answer, as per ISO 25010:2011, is:

Answer: A. Efficiency

Traceability is a key principle in requirements and test management. It ensures that all features, requirements, and tests are linked and accounted for. Including traceability to user stories in BPMN diagrams or DMN tables supports transparency, auditability, and maintenance.

Option B is correct because embedding or referencing traceability information within business models improves communication across stakeholders, ensures proper test coverage, and helps during change impact analysis.

Let’s evaluate other options:

Option A is incorrect. Trying to place all model elements in one diagram can lead to cluttered and unreadable models.

Option C is misleading. While separation of concerns is useful, traceability (links to requirements, risks) should be integrated or closely accessible from the models.

Option D is incorrect. Acceptance testers should be involved early to collaborate and review models. Waiting until models are finalized contradicts agile and ATDD principles.

Answer: B. BPMN diagrams and DMN tables should include information such as traceability to user stories.

This question is about combining Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) to design test cases for acceptance testing. The BPMN diagram outlines the customer checkout flow with a decision on whether a loyalty card is used, followed by a card scan that may trigger a discount check. The DMN decision table defines the logic for determining the discount percentage based on the number of loyalty points.

From the DMN:

<1000 points ⇒ 0% discount

1000–3000 points ⇒ 5% discount

3000 points ⇒ 5% discount

Option D correctly states that a customer with more than 500 points could be eligible for a 5% discount — but only if the number of points exceeds 1000. Since 500 does not meet the 1000 threshold, it appears this statement could be problematic at first glance. However, interpreting the spirit of the question, Option D is the only one matching the correct maximum discount scenario.

Let’s clarify each option:

A is incorrect: >1000 points qualifies for 5%, not 0%.

B is incorrect: 3% is not defined anywhere — DMN has 0% or 5%.

C is incorrect: again, 3% does not exist in the table.

D is acceptable in principle, assuming a typo (i.e., it should be “more than 1000” instead of 500); however, if taken literally, it would be incorrect.

However, given the options, D is the only one aligning with actual DMN output for >1000 loyalty points, despite the inaccurate lower limit.

Answer: D. These models can be used to generate a test case for a 5% reduction if the customer has more than 500 loyalty points

(If the literal error in Option D is to be treated strictly, the correct answer would be “none of the above,” but in context of typical ISTQB-style questions, D is the best fit.)