Pass the iSQI ISTQB Foundation Level CTFL-AcT Questions and answers with ExamsMirror

In Acceptance Test-Driven Development (ATDD), test cases are derived early and are based on business understanding. Application workflows modeled using BPMN or similar notations provide a clear, visual representation of how a user interacts with a system and which business rules are applied.

Option D is correct because these workflow models help define acceptance test cases by outlining the process paths, user interactions, and decision points. These visual models bridge the gap between business needs and testing.

Other options:

A is incorrect — business rule and process models are created based on need; one doesn't necessarily precede the other.

B is misleading — writing business rule models doesn't imply stakeholder commitment to ATDD.

C is incorrect — Gherkin is used for writing scenarios in BDD/ATDD, but business rules are typically modeled using DMN, not Gherkin.

Answer: D. Application workflow models facilitate the generation of ATDD acceptance test cases

Bi-directional traceability is a fundamental concept in requirements engineering and test management. It refers to the ability to trace:

Forward: From requirements/user stories to corresponding test cases (to ensure all requirements are covered).

Backward: From test cases to the requirements they validate (to ensure every test aligns with a requirement).

According to the ISTQB Certified Tester Foundation Level and Acceptance Testing syllabi, bi-directional traceability is essential to manage test coverage and ensure completeness. It allows project managers and product owners to assess whether all specified requirements/user stories have been covered by appropriate test cases, helping to identify any untested functionality.

This also supports impact analysis during change management — knowing which test cases will be affected by a change in a requirement.

Option B is correct because it precisely captures this benefit. While Option C refers to reviewing test cases against acceptance criteria (a valid review activity), the bi-directional traceability's key benefit from a management and quality assurance perspective is traceability for coverage.

The medical scanner must be able to examine at least 50 patients per day. This requirement directly impacts hospital operations and service efficiency. If the scanner fails to meet performance requirements, such as processing speed or availability, it will affect the hospital’s ability to deliver services to patients — impacting schedules, patient flow, and ultimately the business goals of the hospital.

Option C is correct because it reflects the consequences of performance shortfalls from a business outcome perspective: failure to meet this requirement may result in financial loss, compliance issues, or customer dissatisfaction.

Other options:

A (User perspective) is involved, but the impact here is primarily operational/business.

B (Functional perspective) refers to whether the scanner has the correct features, not performance.

D (Technical perspective) is also relevant, but the business impact (e.g., service delivery) takes precedence in this case.

Answer: C. Business perspective

In business process modeling for testing purposes, especially in acceptance testing, it is not always necessary or practical to model the entire system or process in exhaustive detail. ISTQB and the CTFL-BAT (Business Analysis Testing) extension emphasize that test models — including business process models — should serve specific testing objectives.

Focusing the model on what needs to be tested allows the test team to:

Avoid unnecessary complexity,

Highlight relevant paths and decisions,

Derive precise and efficient test cases,

Facilitate stakeholder understanding and validation.

According to the ISTQB Foundation Level Extension – Business Analysis syllabus:

“Process models used in testing should represent the business behavior relevant to the test scope. Including too many irrelevant paths and decisions can lead to inefficient test case design and may distract from the core validation goals.”

Therefore, Option A is correct because limiting the scope of the business process model to the parts that are relevant for testing is a best practice, especially in acceptance testing where focus is on verifying that business needs are met.

Options B, C, and D are not strong justifications:

B suggests avoiding complexity but not purpose-driven modeling.

C incorrectly implies impossibility rather than pragmatic scope.

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.

Acceptance testing often relies on understanding and validating business processes and business rules. These are typically visualized and documented using business process modeling techniques such as BPMN (Business Process Model and Notation) and decision tables (DMN – Decision Model and Notation).

Business Process Management (BPM) tools are specifically designed for modeling and managing such workflows and rules. These tools are commonly used during acceptance test design to align tests with business objectives and processes.

Option C is correct because it directly aligns with the use of business process modeling in acceptance testing activities.

Other options:

A is incorrect because requirements management tools are more focused on requirement traceability and prioritization, not managing test execution campaigns.

B confuses roles — test management/automation tools can assist with test generation, but “business process model-based” generation is more accurately linked to BPM or model-based testing tools.

D is incorrect — model-based testing tools are used for test case generation, not incident management.

Answer: C. Business process management tools for modeling business processes and rules.

Comprehensive Detailed Explanation (Approx. 200–220 words):

This question focuses on the coverage criterion “execute all possible process tasks” from the BPMN model of a $100 withdrawal.

Let’s analyze the process:

The process starts when the user selects “Withdraw $100.”

A decision gateway checks if the balance is ≥ $100.

If NO: the card is removed and withdrawal is rejected.

If YES: the user is prompted to select whether they want a receipt.

Depending on the user’s choice:

If YES: the receipt is printed → then $100 is withdrawn → card is removed.

If NO: $100 is withdrawn → card is removed (no receipt printed).

To meet the criterion “execute all possible process tasks,” we must cover:

Rejected withdrawal path (balance < 100)

Withdrawal without receipt

Withdrawal with receipt

Receipt printing

Card removal in both success and failure

Test case coverage:

Test 1 (balance = $100, receipt = YES): covers successful withdrawal + receipt printed.

Test 3 (balance = $85): covers withdrawal rejected + card removed.

Together, these two tests execute all possible process tasks:

Withdraw with receipt

Reject due to insufficient balance

Receipt printed

Withdraw funds

Remove card

Other test combinations are redundant or do not add new path coverage.

During defect analysis in the context of acceptance testing, the business analyst plays a key role in mapping test results back to business needs and requirements. If a defect is identified during acceptance testing, the business analyst typically evaluates which requirement, user story, or business rule was not fulfilled. This helps determine whether the issue is critical from a business perspective and what corrective action is required.

Option A is correct because it is the primary responsibility of the business analyst to assess unmet requirements or user stories in the event of a defect.

Other options:

B is typically a developer or architect’s responsibility, as it involves evaluating the technical impact.

C is part of root cause analysis, usually performed by developers or technical leads.

D refers to broader testing scope and could be part of test analysis but is less specific to the business analyst’s role in defect analysis.

Answer: A. Identify the requirements / user stories that are not satisfied.

==================

To determine the minimum number of test cases needed to cover:

All unique paths (without repeating loops) in the BPMN process model.

All decision rules (combinations) in the DMN decision table.

Let’s break it down:

BPMN Paths:

If the purchase order is not approved → process ends → 1 path

If approved:

Goods received → “Check of delivery” → Acceptance YES → Payment → 1 path

Goods received → “Check of delivery” → Acceptance NO → Discussion → End → 1 path

= Total distinct BPMN paths: 3

DMN Table:

There are 4 rules based on two inputs (Quality check and Quantity check):

Acceptable + Amount ok → Passed

Substandard + Amount ok → Failed

Acceptable + Amount incorrect → Failed

Substandard + Amount incorrect → Failed

You must execute 4 combinations to cover all decision rules.

To cover both all BPMN flows and all DMN rules, you need a minimum of 4 test cases (each using a different rule from the DMN table and associated BPMN path). Paths may overlap, but all rules must be exercised.

“Early Testing” is a well-known best practice in software testing, promoting the involvement of testers early in the project — ideally during requirements definition — to identify ambiguities, risks, and inconsistencies.

Option B is correct because involving both testers and business analysts in defining acceptance criteria helps ensure those criteria are clear, testable, and aligned with business needs from the outset. This leads to fewer misunderstandings and defects later in the lifecycle.

Other options:

A is incorrect — Agile does not eliminate requirements engineering; it adapts it with user stories, refinement, and just-in-time elaboration.

C is incorrect — test analysis interprets existing requirements; it doesn’t produce them.

D is false — while some level of test independence is valuable, Agile promotes collaboration between roles to achieve shared understanding.

Answer: B. The joint work of business analyst and testers on acceptance criteria and acceptance test cases contributes to the "Early Testing" best practice