A business analyst (BA) facilitated elicitation activities with subject matter experts and end users using observation, workshops, and interviews. After comparing the results, how should the BA resolv

Limiting conflict resolution to a few key stakeholders excludes subject matter experts and end users whose input created the variation, risking an incomplete or biased resolution.

Setting up additional collaborative activities allows all relevant stakeholders to examine conflicting information together and reach consensus through structured dialogue. This aligns with BABOK guidance that elicitation and confirmation are iterative processes used to resolve discrepancies. Collaborative resolution ensures no valid perspective is dismissed and that the final requirements reflect an agreed-upon understanding.

Removing requirements that cause differences discards potentially valid business needs without first understanding whether they reflect legitimate requirements.

Weighting observation as inherently more reliable is a subjective bias - no single elicitation technique is universally superior, as each captures different aspects of requirements.