Conflicting requirements are common in BA work. A strong answer shows that you stay neutral, bring stakeholders back to business goals, and use evidence to guide decisions.
I would first make sure I understand each stakeholder's requirement, the business reason behind it, and the impact if it is not delivered. I would avoid taking sides and instead document the conflict clearly, including assumptions, dependencies, risks, and affected processes.
Then I would facilitate a discussion with the stakeholders to compare the requirements against business objectives, customer impact, compliance needs, cost, timeline, and technical feasibility. If needed, I would use prioritization techniques such as MoSCoW, impact-versus-effort, or value-versus-risk.
If the group still cannot agree, I would escalate with a clear recommendation, supporting analysis, and options for decision-makers. Once a decision is made, I would update the requirements documentation, communicate the rationale, and confirm stakeholder sign-off.
"My role as a BA is to create clarity, not choose sides. I would help stakeholders make an informed decision based on business value, risk, feasibility, and agreed project goals."