CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Solution validation confirms that the built solution correctly implements the requirements and delivers the intended business value. BAs typically facilitate user acceptance testing and sprint reviews to validate delivered functionality.

**Why not A:** Risk analysis involves identifying, assessing, and prioritizing potential threats and opportunities that could affect the project. While BAs contribute to risk identification during requirements analysis, risk analysis does not involve reviewing delivered functionality against requirements — that is a post-delivery confirmation activity.

**Why not B:** Stakeholder identification is an early-project activity focused on discovering and documenting all individuals and groups with an interest in the project. It establishes who should be engaged for requirements elicitation and communication planning, and is not related to reviewing delivered functionality against requirements.

**Why not C:** Requirements elicitation is the process of discovering, extracting, and documenting stakeholder needs — it occurs before solution development. Reviewing delivered functionality against those documented requirements is a later activity called solution validation, which confirms that the development team correctly implemented what was specified.