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

Requirements validation confirms that the documented requirements correctly capture what stakeholders need and that the proposed solution would actually deliver business value. It's distinct from verification (checking if the solution meets requirements).

**Why not A:** Version control is a configuration management and development operations concern, not a BA validation activity. While proper version control is important for project hygiene, the BA's validation focus is on confirming that delivered functionality aligns with documented requirements and stakeholder expectations, not on repository management practices.

**Why not B:** Requiring project manager approval before sharing deliverables is an administrative gate, not a validation activity. BA validation involves confirming that a solution or requirement artifact meets its intended purpose and acceptance criteria. Routing approvals through a PM is a governance step that does not constitute validation of correctness.

**Why not D:** Verifying that code meets coding standards is a development team responsibility, typically handled through code reviews and automated linting tools. BA validation focuses on whether the solution satisfies business requirements and delivers expected value, not on the technical quality or style of the underlying code implementation.