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.

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.
B). Business goals, business needs and requirements describe, at different levels of abstraction, what shall be achieved

Test reports summarize the results of test execution and are often used by stakeholders, including business owners and release managers, to make informed decisions about whether to release a product. If these reports are ambiguous, incomplete, or inaccurate, the decisions based on them could be flawed, leading to reputational damage, customer dissatisfaction, or regulatory issues.
Option A is correct because it highlights the risk of basing critical go/no-go decisions on poor-quality reporting.
Other options:
B describes a problem with test case implementation, not test reporting.
C mentions public perception, which might be influenced by report quality, but it is secondary to the internal decision-making purpose.
D refers to human error during test execution or design, not the purpose of reviewing test reports.
A). If the test reports are unclear or incomplete, the decision to release the product can be based on non-reliable information

Exploratory testing is a dynamic testing technique where learning, test design, execution, and interpretation occur simultaneously. It is especially useful when detailed requirements are unavailable or when testers rely on experience and intuition.
A is correct: Exploratory testing combines exploration, learning about the product, designing and executing tests on the fly, and interpreting the results - all within the same session.
E is also correct: Exploratory testing usually starts with a high-level test charter that defines the mission, objectives, or focus area for the session. It may not define specific test conditions, but it outlines the scope and intent.
Other options:
B: Not accurate - while timeboxing is used, exploratory testing typically relies on charters and experience rather than detailed product risk analysis to prioritize.
C: Incorrect - exploratory testing is not about refining acceptance criteria; that's part of ATDD.
D: Partially true but misleading - good business domain knowledge helps, but understanding the functionality is also important in exploratory testing.

In cross-functional, globally distributed teams, establishing collaboration, communication, and trust is key. A workshop (even virtual) is a proven method for initiating alignment, especially when a new team member joins, and project coordination is weak.
Option A promotes transparency and collective understanding, crucial for building team cohesion.
Option B is too passive and one-directional. Long emails rarely solve coordination problems in Agile or collaborative contexts.
Option C is about tool setup, not team integration or communication - tools are supportive but not substitutes for human connection.
Option D is not efficient; traveling to meet each team member is impractical and doesn't guarantee a shared team vision.
A). You organize a workshop with all team members to establish common understanding and to lay the foundation for fruitful trusting collaboration.