Explanation
According to the BABOK Guide, one of the tasks of the business analyst is to obtain stakeholder approval on requirements. This task involves ensuring that the stakeholders have a shared understanding of the requirements and that they agree on their validity and priority. The business analyst also has to address any concerns, issues, or conflicts that may arise during the approval process. The business analyst has to communicate the requirements clearly and effectively, using appropriate techniques and tools, such as presentations, prototypes, models, or simulations. The business analyst also has to document the approval decisions and track the status of the requirements throughout the project lifecycle. The other options are not relevant to this task. The stakeholders' ability to pay for the solution is not a factor in the approval of the requirements, but rather a factor in the feasibility and viability of the solution. The project manager's input on the solution is not a substitute for the stakeholder approval, but rather a complement to it. The project manager may have a different perspective and interest in the solution than the stakeholders. Getting all the stakeholders to sign off on the requirements is not enough to ensure their understanding and agreement. The business analyst has to verify that the stakeholders have reviewed and comprehended the requirements before obtaining their signatures. References:
BABOK Guide, Version 3, Section 4.5: Obtain Stakeholder Approval on Requirements, page 118-120.
Getting Back to Basics: Delivering Approved Requirements - Modern Analyst, paragraph 2-3.
Requirements approvals - The Functional BA, paragraph 1-2.