Guys, I am not sure to get it...

What is not the purpose of configuration control when configuration management is applied in a project?

1 )Verification that the configuration identification for a configuration item is accurate, complete, and will meet specified program needs.

2 ) Ensuring that proposed and approved changes to configuration items are fully analyzed.

3 ) Ensuring that proposed and approved changes to configuration items are fully documented.

4 ) Managing and controlling the frequently requested changes to a project by applying agreed rules.

What PMBOK Says :

Configuration control is focused on the specification of both the deliverables and the processes; while change control is focused on identifying, documenting, and approving or rejecting changes to the project documents,
deliverables, or baselines.

Configuration identification. Identification and selection of a configuration item to provide the basis for which the product configuration is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.

Configuration status accounting. Information is recorded and reported as to when appropriate data about the configuration item should be provided. This information includes a listing of approved configuration identification, status of proposed changes to the configuration, and the implementation status of approved changes.

Configuration verification and audit. Configuration verification and configuration audits ensure the composition of a project’s configuration items is correct and that corresponding changes are registered, assessed, approved, tracked, and correctly implemented. This ensures the functional requirements defined in the configuration documentation have been met.