An enterprise network infrastructure team needs to apply a vendor-recommended operating system update across core routing hardware to address a zero-day vulnerability. In which order should the engineer execute the patch management and maintenance lifecycle steps from first to last?
- 1Validate patch functionality and stability inside an isolated lab environment.
- 2Submit a formal change request to the Change Advisory Board (CAB) detailing risk assessments and rollback plans.
- 3Deploy the update to a pilot staging group of non-critical edge devices during an approved window.
- 4Perform enterprise-wide production deployment and conduct post-implementation verification audits.
Answer
The proper sequence for network patch management requires isolating and testing the update in a lab, obtaining Change Advisory Board approval with an established rollback strategy, executing a pilot deployment in a staging environment, and finally completing the full production rollout accompanied by post-implementation health checks.
Structured network maintenance follows a linear lifecycle to minimize outage risks: testing the patch in an isolated lab environment comes first to discover defect anomalies; securing formal Change Advisory Board (CAB) approval with documented rollback steps comes second; deploying to a pilot staging environment during a scheduled maintenance window comes third; and completing full production rollout alongside post-deployment auditing comes last.
Step-by-Step Solution
Key Concept
Network Patch Management Lifecycle and Change Management Governance