iSQI CTFL-AcT Practice Test Questions Answers

In acceptance testing, testers execute test cases that are directly derived from user stories or requirements via their acceptance criteria. During execution, testers compare the actual outcome of the system with the expected result described in the acceptance criteria. If there's a mismatch (a deviation), it is documented as a defect or discrepancy.

This process is essential for validating that the system meets business needs. The tester’s role includes reporting clear, objective findings—not fixing the defect or deciding its severity (which might involve developers or business analysts).

Option A is incorrect: Business analysts may support testing, but execution is primarily a tester’s responsibility.

Option C is not fully correct: While developers may fix defects, assignment and triage follow a formal workflow and do not happen automatically.

Option D is incorrect: Business analysts don’t repeat test executions; this is the tester’s responsibility.

Beta testing is a form of external user acceptance testing where real users test the product in their environment before the official release. It helps identify issues that may not have been caught in internal testing and gather user feedback on functionality, usability, and performance in real-world conditions.

Option C is correct — the core goal of beta testing is to obtain user feedback in their actual usage context, providing insight into how the system performs outside of controlled environments.

Other options:

A: Test charters are used in exploratory testing, not typically in beta testing.

B: Incorrect — beta testing is not tied to the timing of user story development in Agile.

D: Incorrect — beta testing is performed by end users, not by internal team members like developers or business analysts.

Answer: C. Beta testing aims to obtain feedback from users in their context of use

Decision Model and Notation (DMN) is a standardized approach used to model decision logic, often represented in decision tables that evaluate inputs and determine outputs. In this scenario, the entitlements granted to a candidate are based on the total score from two exams, where:

Each exam can be graded as either 0 or 1.

The combined score can be 0, 1, or 2.

The entitlements depend on the combined result:

0 → No entitlements

1 → Partial entitlements

2 → Full entitlements

Among the given diagrams:

Option A simply lists test cases but lacks explicit logic modeling.

Option B shows a mapping from total score to entitlements but doesn't model how the total is derived from the two exams.

Option C redundantly splits outputs into multiple Boolean fields and doesn't reflect how the decision is made from exam inputs.

Option D is the correct representation.

Option D uses:

e1 and e2 as inputs for Exam #1 and Exam #2.

Result as the sum of e1 + e2.

A final Output mapped based on the Result:

0 → No

1 → Partial

2 → Full

This structure accurately follows the DMN standard by expressing inputs, a derived result, and the corresponding decision output, making Option D the correct and most complete decision model.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 2.3):

“Decision tables are commonly used to express business rules that determine outputs based on combinations of inputs. DMN formalizes this structure to support automated reasoning.”

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.

Beta testing is a type of acceptance testing performed by end users in a real-world or production-like environment. It is especially relevant for cloud-based and SaaS platforms where widespread feedback is required before release.

Option B is correct because SaaS platforms often release features to a subset of users (beta users) to test the software under actual operating conditions, get feedback, and fix any defects that were not found during internal testing. This allows vendors to validate functionality, performance, and usability in diverse environments.

Other options:

A: Beta testing is not limited to Commercial Off-the-Shelf (COTS) software.

C: Incorrect — beta testing is a form of acceptance testing, not a separate unrelated technique.

D: Incorrect — beta testing and acceptance testing overlap, but they are not synonyms; the terminology does not change based on the development approach (Agile or not).

Answer: B. Beta testing is often used for acceptance testing of Software as a Service (SaaS) platforms