CAPM Practice: Validate requirements through product delivery

Operational readiness validates non-functional and operational requirements: can the system be supported, monitored, and maintained? Are disaster recovery requirements met? Is there adequate training? These requirements are often overlooked in functional validation but are critical for production success.

**Why not A:** Testing whether the operations team is ready to manage the system is one aspect of operational readiness, but this choice is too narrow. Operational readiness testing encompasses a broader scope including runbooks, disaster recovery, monitoring, support documentation, and training materials.

**Why not B:** Describing operational readiness testing as a type of user acceptance testing focused on day-to-day operations conflates two distinct testing activities. UAT validates functional requirements from the user perspective, while operational readiness testing validates non-functional and operational requirements for production sustainability.

**Why not D:** Operational readiness testing is directly relevant to BA requirements work because BAs define many of the non-functional and operational requirements being validated. Dismissing it as solely an operations staff concern ignores the BA's responsibility for ensuring these requirements are complete and testable.