CAPM Practice: Validate requirements through product delivery

Distinguishing defects from requirements gaps determines the right fix: defects are implementation problems corrected by developers; requirements gaps reveal specification failures requiring requirements updates and may indicate a broader specification quality problem.

**Why not B:** Both defects and requirements gaps can be found by QA, BAs, developers, or any team member during validation. The distinction is not about who discovers the issue but about the nature of the problem: implementation error versus specification failure. Different root causes require different resolution approaches.

**Why not C:** Requirements gaps are not always more serious than defects. A critical defect in a security feature could be far more serious than a minor requirements gap in a cosmetic feature. The severity depends on the specific issue's impact on business operations, users, and system integrity.

**Why not D:** Defects and requirements gaps are fundamentally different issues. A defect means the code does not match what was specified, while a requirements gap means the specification itself was flawed. Treating them identically leads to applying the wrong fix, such as debugging code when the real problem is an incomplete specification.