CAPM Practice: Validate requirements through product delivery

Compliance-grade validation requires documented evidence: requirements ID, test case, tester, date, environment, result, and sign-off. This audit trail demonstrates to regulators, auditors, or customers that all requirements were systematically validated before delivery.

**Why not B:** Verbal acceptance is insufficient for audit and compliance purposes. Regulated environments require documented evidence of systematic validation — who validated what, when, how, and with what result — to demonstrate compliance to auditors, regulators, or customers.

**Why not C:** Documenting only failed results creates an incomplete audit trail. Auditors and compliance reviewers need evidence that all requirements were validated, including those that passed. Without documenting successful validations, there is no proof that systematic validation occurred.

**Why not D:** Validation documentation is a shared responsibility, and BAs play a key role in it. While QA manages test execution documentation, BAs are responsible for ensuring that validation results are linked to requirements and that the overall validation trail demonstrates coverage of all business requirements.