What is a primary goal of performing change-control prior to deployment?

What is a primary goal of performing change-control prior to deployment?

• A. Slow down deployment without benefit.
• B. Replace change-control with ad-hoc updates.
• C. Skip approvals if vendor provides a patch.
• D. Ensure only approved changes are deployed, reducing risk of unauthorized or faulty updates.

Answer: (D)

Change-control before deployment is about managing changes to production in a controlled way. It ensures that changes are reviewed, tested, authorized, implemented with a rollback plan, and logged, so only approved updates go live. This reduces the risk of unauthorized or faulty updates disrupting services or creating security gaps, which is why the best option is that only approved changes are deployed, reducing risk. The other options describe behaviors that defeat governance or introduce risk: unnecessary delays without benefit, ad-hoc updates, or skipping approvals on patches.

Change-control before deployment is about managing changes to production in a controlled way. It ensures that changes are reviewed, tested, authorized, implemented with a rollback plan, and logged, so only approved updates go live. This reduces the risk of unauthorized or faulty updates disrupting services or creating security gaps, which is why the best option is that only approved changes are deployed, reducing risk. The other options describe behaviors that defeat governance or introduce risk: unnecessary delays without benefit, ad-hoc updates, or skipping approvals on patches.