Graphical representations of business processes, particularly using BPMN (Business Process Model and Notation), serve as a bridge between business stakeholders and testers. These models help visualize the steps a user or system goes through, making it easier to derive test cases.
Option C is correct because acceptance testing aims to validate the system's behavior from the user or business perspective. Therefore, focusing on key user workflows (rather than exhaustive technical or exception paths) aligns with the purpose of acceptance testing: to ensure that the system meets agreed-upon business requirements.
Option A is incorrect because decision tables are part of DMN (Decision Model and Notation), not BPMN.
Option B is too rigid - not all alternative/error paths must be modeled in early acceptance testing unless they are critical to business rules.
Option D misapplies the standards - DMN is used to model business rules, not the complete business process.
C). For acceptance testing, graphical business process models should focus on the user workflows to be tested.

An exploratory test charter is a high-level plan or mission statement for a time-boxed exploratory testing session. It guides what the tester should focus on during the session and may include the goal of the test, specific areas of the system under test, the risk or feature to explore, the type of persona to simulate (e.g., novice or expert user), and possibly known issues to watch out for.
Option A is correct because specifying a user persona (such as a novice user) helps the tester approach the system from that perspective. This supports the goal of exploratory testing: to simulate realistic usage and uncover issues that scripted tests might miss.
Option B is incorrect - although exploratory testing is adaptive, the charter is defined before the session starts, not elaborated during execution.
Option C is misleading - charters may refer to areas of interest, but not necessarily to a predefined list of activities.
Option D is incorrect - a test oracle (i.e., the mechanism for determining whether a result is correct) is not defined by the charter. It may exist already or be inferred from requirements, heuristics, or user expectations.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 3.1):
"Charters define the focus of exploratory testing sessions and may specify the tester's role or perspective (e.
g., novice user)."

This question is about combining Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) to design test cases for acceptance testing. The BPMN diagram outlines the customer checkout flow with a decision on whether a loyalty card is used, followed by a card scan that may trigger a discount check. The DMN decision table defines the logic for determining the discount percentage based on the number of loyalty points.
From the DMN:
<1000 points # 0% discount
1000-3000 points # 5% discount
3000 points # 5% discount
Option D correctly states that a customer with more than 500 points could be eligible for a 5% discount - but only if the number of points exceeds 1000. Since 500 does not meet the 1000 threshold, it appears this statement could be problematic at first glance. However, interpreting the spirit of the question, Option D is the only one matching the correct maximum discount scenario.
Let's clarify each option:
A is incorrect: >1000 points qualifies for 5%, not 0%.
B is incorrect: 3% is not defined anywhere - DMN has 0% or 5%.
C is incorrect: again, 3% does not exist in the table.
D is acceptable in principle, assuming a typo (i.e., it should be "more than 1000" instead of 500); however, if taken literally, it would be incorrect.
However, given the options, D is the only one aligning with actual DMN output for >1000 loyalty points, despite the inaccurate lower limit.
D). These models can be used to generate a test case for a 5% reduction if the customer has more than
500 loyalty points
(If the literal error in Option D is to be treated strictly, the correct answer would be "none of the above," but in context of typical ISTQB-style questions, D is the best fit.)

Exploratory testing is an unscripted, experience-based testing technique where the tester learns about the system, designs tests, and executes them simultaneously. It is especially effective in Agile environments, where rapid feedback and creative exploration are valuable.
Option D is the least likely action because scripting automated test scripts is a structured activity that typically occurs after exploratory sessions or during more formal test phases. Exploratory testing emphasizes manual exploration, not automation scripting.
Other options:
A is part of the core purpose of exploratory testing - discovering the product.
B is relevant - defining a charter and discussing it with stakeholders (like the Product Owner) helps guide the exploratory session.
C is also relevant - results of exploratory tests should be documented and communicated.
D). Scripting of the automated test scripts

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.