Comprehensive Detailed Explanation (Approx. 200 words):
Building a new team with members from diverse backgrounds requires activities that foster shared values, identity, and trust. Designing a team emblem with values, goals, and a motto is a well-known team-building technique often used in Agile kick-offs. It engages creativity, sparks discussion about shared purpose, and reinforces a collective team identity.
Option A is correct because it supports both vision and team spirit - crucial for newly formed teams.
Other options:
B focuses on individual backgrounds but may not build a collective vision.
C risks highlighting negative views about the organization and may not foster trust at the early stage.
D uses a "staircase" metaphor but incorrectly locates the team at the top of the stairs - potentially signaling an endpoint rather than a beginning, making it inappropriate for a new team.
A). You invite the team members and ask them to design their own emblem...

The medical scanner must be able to examine at least 50 patients per day. This requirement directly impacts hospital operations and service efficiency. If the scanner fails to meet performance requirements, such as processing speed or availability, it will affect the hospital's ability to deliver services to patients - impacting schedules, patient flow, and ultimately the business goals of the hospital.
Option C is correct because it reflects the consequences of performance shortfalls from a business outcome perspective: failure to meet this requirement may result in financial loss, compliance issues, or customer dissatisfaction.
Other options:
A (User perspective) is involved, but the impact here is primarily operational/business.
B (Functional perspective) refers to whether the scanner has the correct features, not performance.
D (Technical perspective) is also relevant, but the business impact (e.g., service delivery) takes precedence in this case.

The best Gherkin-style acceptance tests are business-oriented, behavior-driven, and avoid unnecessary technical or UI details. They describe actions in a way stakeholders can understand, focusing on system behavior rather than implementation mechanics.
Option A follows Gherkin conventions:
GIVEN clearly describes the system state (account balances).
WHEN describes a user action (transferring funds).
THEN describes a verifiable outcome (account balances updated correctly).
Option B includes unnecessary UI actions like clicking buttons or field names, which are implementation- specific and violate the abstraction level expected of acceptance tests.
Option C uses appropriate structure but introduces incorrect balances in the THEN step (possibly a typo;
$4500 on X is wrong if funds were transferred from Y to X).
Option D uses improper syntax - WHEN is misused as another GIVEN, and THEN describes a computation rather than a system behavior.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 2.2.2):
"Acceptance criteria in BDD are best captured through Gherkin scenarios that are understandable by business stakeholders and focus on expected outcomes, not implementation details."

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.
D). Instead of discussing conflicting technical solutions, you try to understand the underlying business needs