iSQI Updated CTFL-AcT Exam Questions and Answers by jeremiah

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.

The relationship between business goals, business needs, and requirements is hierarchical and reflects increasing levels of specificity:

Business Goals: High-level strategic objectives.

Business Needs: Problems or opportunities that must be addressed to achieve those goals.

Requirements: Specific capabilities or conditions the system must satisfy to meet the needs.

Option B is correct because it accurately describes how these elements relate at different abstraction levels in the requirements hierarchy. This relationship is fundamental to business analysis and accepted by standards like BABOK and ISTQB.

Other options:

A is reversed — business goals usually precede and drive the elicitation of requirements.

C and D misrepresent the sequence — product requirements are derived from business goals and needs, not the other way around.

Answer: B. Business goals, business needs and requirements describe, at different levels of abstraction, what shall be achieved

An acceptance test summary report is a high-level document produced at the end of acceptance testing. It provides stakeholders (especially business owners and decision-makers) with essential information to determine whether the system meets the acceptance criteria and whether it is ready for release.

Option A is correct because understanding the residual risk — based on test results, open defects, and coverage — is critical for release decisions. The summary report includes test execution status, significant findings, defect summaries, and an overall risk assessment.

Other options:

B (technical details on defect fixes) belong more in defect or technical reports, not in the acceptance summary.

C (test strategy/design methods) are part of the test plan, not the summary report.

D (test procedure info) is operational detail, not suited for a high-level summary report.

Answer: A. Information to evaluate the level of risk for product release.