In the PMBOK Guide, the distinction between Manage Quality and Control Quality is fundamental to understanding how a project manager ensures excellence throughout the project life cycle.
* Manage Quality (Choice A - First Part): This is the process of translating the quality management plan into executable quality activities. It is often referred to as Quality Assurance. Its primary focus is on the processes being used. By ensuring that the team follows organizational policies and defined procedures, the project manager increases the probability that the final product will meet quality standards. It is " preventative " in nature.
* Control Quality (Choice A - Second Part): This process focuses on the deliverables themselves. It involves monitoring and recording the results of executed quality activities to assess performance and ensure the project outputs are complete, correct, and meet customer requirements. It is " detective " in nature, identifying defects in the actual product before it reaches the customer.
* Choice B: This incorrectly swaps the definitions of the two processes.
* Choice C: This is incorrect; while they are related, they have distinct objectives (Process vs. Product) and occur at different points in the workflow.
* Choice D: This is incorrect because Control Quality is a core process within the Project Quality Management knowledge area, not the Stakeholder Management process group.
By balancing both processes, the project manager ensures that the project not only builds the " right thing " (Control Quality) but also builds it the " right way " (Manage Quality).