A security administrator must deploy a critical system patch and an updated security hardening baseline across a fleet of enterprise application servers. To minimize operational risk and maintain security compliance, the administrator must follow a structured configuration and patch management workflow. In what order should the administrator execute these operational steps from first to last?
- 1Validate the patch and modified configuration baseline within an isolated staging environment to verify system functionality.
- 2Submit a formal change request to the Change Advisory Board (CAB) including test metrics, risk impact analysis, and a rollback plan.
- 3Execute a controlled deployment of the patch and baseline to a designated canary group of production servers while monitoring system health.
- 4Push the automated configuration management policy and patch payload across the remaining enterprise production fleet.
- 5Run an automated compliance scan to verify patch application and record the new state snapshot as the official configuration baseline.
Answer
The correct operational sequence begins with non-production staging validation, followed by Change Advisory Board approval, a phased canary deployment, full production fleet distribution, and final post-deployment compliance scanning to establish the new baseline snapshot.
The standard patch and configuration management lifecycle follows a strict sequence: validate in non-production staging, obtain Change Advisory Board authorization with a rollback plan, execute a limited canary deployment, deploy to the entire production fleet using configuration orchestration, and finally perform an automated compliance scan to record the new baseline snapshot.
Step-by-Step Solution
Key Concept
Patch and Configuration Management Workflow