CAPM Practice: Validate requirements through product delivery

A/B testing is a powerful requirements validation tool: when there's uncertainty about which requirements interpretation delivers more value, testing both variants with real users provides objective evidence. The winning variant's requirements are validated by user behavior.

**Why not B:** A/B testing is widely used in product development beyond marketing campaigns. Product teams routinely test feature variants, workflow designs, and interface options to determine which implementation best meets user needs. It is a powerful requirements validation tool for any product decision with measurable outcomes.

**Why not C:** A/B testing does not validate functional requirements against non-functional requirements. It compares two different implementations of the same feature to see which delivers better outcomes for users. The A and B refer to variant versions, not to requirement types.

**Why not D:** A/B testing is not a hiring technique. It is a controlled experiment methodology where different user segments experience different product variants, with measurable outcomes determining which variant better achieves the intended business and user goals.