This is because classifying requirements helps to ensure that they are fully understood and traceable by grouping them into categories based on their type, source, priority, or other criteria. Classifying requirements also helps to avoid duplication, ambiguity, and inconsistency among the requirements. Extracting requirements for review (A) is not a valid option, as it implies that the requirements are already documented and ready for approval. Validating requirements © is a good practice, but it does not ensure traceability, which is the ability to link the requirements to the business needs, solution components, and test cases. Meeting regulatory standards (D) is a quality criterion, but it does not ensure that the requirements are fully understood and traceable. References: CCBA Practice Test, CCBA Mock Test