Examkin

Question

Difficulty: MediumPatch and Configuration Management

A security administrator must deploy a critical security patch across enterprise production application servers following standard change control and patch management practices. Place the following operational lifecycle steps in the correct sequential order from first to last.

  1. 1Validate the patch in an isolated sandbox environment to test for system instability or application compatibility issues.
  2. 2Submit a formal change request to the Change Advisory Board (CAB) detailing the patch impact, risk analysis, and emergency rollback procedure.
  3. 3Deploy the patch to a pilot/staging fleet to monitor performance and gather telemetry under representative operational workloads.
  4. 4Execute the enterprise-wide patch installation across all remaining production servers during an approved maintenance window.
  5. 5Perform an automated vulnerability compliance scan and update the official configuration baseline.

Answer

The correct operational sequence begins with non-production sandbox testing, followed by submitting a formal change request to the Change Advisory Board, deploying to a pilot/staging fleet, executing the full production deployment during a scheduled maintenance window, and finally auditing compliance to update the configuration baseline.
Structured patch and configuration management follows a strict procedural lifecycle: non-production sandbox testing, formal Change Advisory Board authorization, staged pilot deployment, enterprise production rollout, and final post-installation verification auditing.

Step-by-Step Solution

1
Conduct initial functional and security testing in an isolated sandbox environment.
Identifies software conflicts or system crashes without impacting live operations.
Patches must never be applied to production or submitted for formal change approval without preliminary compatibility validation.
2
Submit a change request to the Change Advisory Board (CAB).
Obtains formal management approval, documents risks, and establishes backout plans.
Enterprise change management governance requires documented authorization before deploying changes to live operational systems.
3
Roll out the patch to a pilot or staging group.
Verifies patch stability under real-world conditions on a small subset of systems.
Staging deployments mitigate enterprise-wide outage risks by detecting unexpected edge-case issues early.
4
Perform full production deployment during an approved maintenance window.
Applies the patch across all target enterprise assets.
Deployment timing must align with authorized maintenance windows to minimize disruption to business operations.
5
Conduct automated compliance auditing and update configuration baselines.
Confirms successful patch application and establishes a new hardened system baseline.
Post-patch verification ensures no systems were missed and updates security records to prevent false drift alerts.

Key Concept

Standard Patch Management Lifecycle and Change Governance
Rate this question

Topics

Patch and Configuration Management

More questions from this topic