iSQI CTFL-AcT Dumps Questions Answers

Let’s analyze the DMN table shown in the image:

Rule 1: If weight ≤15, size ≤50, and distance ≤10 → use Normal bicycle

Rule 2: If weight is between 15 and 60 kg, size ≤150, and distance ≤25 → use Electric cargo bike

Rule 3: Otherwise → use Electric van

Now consider the options:

A: Incorrect — parcel size is not the only determining factor for using electric vans; it's about weight, size, and distance combined.

B: Incorrect — normal bicycles are used only when weight ≤15 kg, size ≤50 cm, and distance ≤10 km — so not just “short trips.”

C: Incorrect — electric cargo bikes are explicitly used for short trips (≤25 km), per Rule 2.

D: Correct — based on the rules, any weight above 15 kg (and up to 60 kg) results in the use of electric cargo bikes. So if weight >50 kg (but ≤60), cargo bike is still used under the conditions of Rule 2.

Therefore, the most consistent interpretation of the decision model is:

Answer: D. When the weight of the parcel exceeds 50kg then the electric cargo bike is necessarily used

UX task analysis focuses on understanding how users perform their tasks in real-world contexts. It captures not only the sequence of actions but also the surrounding environment — including physical conditions (light, noise), devices used, interruptions, and constraints. These external or environmental conditions become vital inputs to UX design decisions, helping teams adapt interfaces and workflows to user realities.

Option C is correct because it emphasizes this key aspect of UX task analysis: capturing external conditions that influence usability and system interaction.

Other options:

A focuses on user profiling, not task analysis.

B refers to business process modeling, which is more strategic and less user-context specific.

D refers to benchmarking or inspiration analysis — useful for design ideation but not task analysis.

Answer: C. External conditions are considered as input for subsequent design steps.

In Gherkin syntax (Given-When-Then), the purpose is to describe system behavior in a way that’s understandable to all stakeholders. Test steps should focus on user intentions and observable results — not UI implementation details — to ensure maintainability and abstraction.

Line 3 ("click 'Buy Tickets' button") refers explicitly to a UI element, which should generally be avoided in acceptance tests. Instead, it could say "I request to buy tickets."

Line 7 ("I should provide my personal data") is describing an action the user must take, not an outcome or result. In a Gherkin “Then” step, we expect an observable system response, not further user interaction.

Option C identifies both of these review concerns correctly.

Other options:

A includes an incorrect comment about line 4 ("quantity should not be set") — setting a value is acceptable.

B is false — the test case has reviewable issues.

D might be valid in a different context (e.g., boundary tests), but that’s not a flaw in the existing scenario.

Answer: C. Line 3 refers to an element of the user interface, which is to be avoided and line 7 is an action and not a result