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

In ATDD (Acceptance Test-Driven Development), business process modeling (e.g., using BPMN) is a powerful way to visualize workflows and system behavior from the user's perspective. Testers can use these models to derive acceptance test cases by covering different business paths, including normal flows, alternate flows, and exception conditions.

Option A is correct because it reflects this practical usage: testers analyze the business process model and create test cases to ensure coverage of the different paths the system might take. This aligns acceptance testing directly with business logic and enhances traceability.

Other options:

B is partially valid but less direct; business analysts help define rules, but test case creation is a tester's role.

C reverses the correct flow; BPMN models are often created first and used to define or validate acceptance criteria, not the other way around.

D is incorrect — requirements/user stories are usually defined through stakeholder collaboration, not auto-generated from BPMN diagrams.

Answer: A. Testers use business process models to write test cases that cover the different paths.

In usability and user experience, system feedback is critical. Users expect clear, timely responses from the system to confirm their actions are received and processed. Lack of feedback (e.g., when clicking a button yields no visual response) leads to confusion, frustration, or repeated actions.

Option B is correct because it highlights a genuine issue from a user’s perspective — inadequate feedback, which affects usability and satisfaction.

Other options:

A focuses on technical infrastructure (architecture, computing power) — a technical or business concern, but less so from a user’s lens.

C is mostly correct but fits the technical or test engineer’s perspective rather than the user’s.

D is inaccurate — selection of performance tools is primarily a technical/test management decision, not business-driven.

Answer: B. From a user perspective, missing feedback from the system when processing a request is a problem.

When stakeholders provide conflicting acceptance criteria, resolving the conflict effectively requires focusing on the underlying business goals rather than getting stuck in technical or solution-level disagreements.

Option D is correct because it aligns with the core role of a business analyst and an acceptance tester: to understand and validate business needs. By exploring the root business objectives, you can help stakeholders reframe the problem and reach a compromise based on what delivers the most value.

Other options:

A may lead to confrontation and unproductive discussion without proper facilitation.

B is risky — prioritizing stakeholders may escalate conflict or appear biased.

C assumes you can objectively resolve the conflict based only on pros and cons, but without understanding the business context, the decision may not meet stakeholder needs.

Answer: D. Instead of discussing conflicting technical solutions, you try to understand the underlying business needs

“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