iSQI CTFL-AcT Exam With Confidence Using Practice Dumps

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.)

This user story is about a logged-in user measuring their blood sugar using a connected glucose meter and seeing the result quickly. The acceptance criterion specifies that the result should be displayed in less than four seconds.

Option B is correct because:

It starts with a valid GIVEN precondition (“I am logged in”).

The WHEN step matches the functionality described in the user story (blood sugar measurement using a connected device).

The THEN step explicitly includes the performance expectation (“less than 4 seconds”), aligning directly with the acceptance criterion.

Other options:

A is incorrect — while it mentions the correct functionality, “I am diabetic” is not a necessary system precondition.

C refers to blood pressure instead of blood sugar — mismatched with the user story.

D introduces additional functionality (alerts for hypo-/hyperglycemia), which is not part of the specified acceptance criteria.

Answer: B. GIVEN I am logged in on the system … THEN I can see the result … in less than 4 second

In situations where a team is demotivated or struggling with vision and direction, it's effective to use visualization workshops that help the team reflect on progress and visualize a path forward.

Option B describes a metaphorical workshop using a staircase to represent the project's journey — this is known as the "Stairway Retrospective" or "Timeline Workshop". It provides a shared mental model, identifies milestones, and encourages discussion around past progress and future steps. It's ideal for reigniting motivation and clarifying direction — which aligns with the issue described in the question.

Other options:

A can spark debate but may not be constructive or motivating in a stagnation scenario.

C may foster team bonding but doesn’t directly address project direction or vision.

D focuses only on future milestones and lacks the reflective component essential when a team feels stuck.