Question

Difficulty: HardPatch Management and Software Maintenance

A network engineering team must mitigate a critical zero-day privilege escalation vulnerability affecting core infrastructure routers. Which of the following represents the correct sequence of administrative and technical steps required to safely implement this software update according to standardized network maintenance procedures?

  1. 1Review the vendor advisory to perform a risk assessment and verify image file hashes.
  2. 2Install and validate the update within a dedicated non-production lab environment.
  3. 3Submit a formal change management ticket to the Change Advisory Board (CAB) with a verified rollback plan.
  4. 4Capture a full baseline backup of system configurations and OS state on the target production routers.
  5. 5Deploy the patch to production devices during the approved maintenance window and verify operational integrity.

Answer

The correct sequence begins with vendor advisory analysis and hash verification, followed by staging/lab testing, securing formal CAB approval with a rollback strategy, taking pre-upgrade configuration baselines, and finally executing the deployment during an authorized maintenance window followed by verification.
The correct process follows standardized network operations governance: initial risk and patch verification precedes staging lab validation, which provides empirical data required for Change Advisory Board (CAB) authorization. Immediately prior to applying the update during the approved maintenance window, administrators take a full baseline backup of target devices to ensure immediate rollback capabilities if the upgrade encounters unexpected faults.

Step-by-Step Solution

1
Analyze vendor advisories and confirm patch integrity.
Establishes necessity, scope, and verifies patch file authenticity via cryptographic hashes.
Prevents deploying corrupted binaries or unnecessary updates.
2
Perform staging lab validation.
Identifies software bugs, performance anomalies, or CLI syntax variations.
Lab verification ensures production stability without risking live network traffic.
3
Request Change Advisory Board (CAB) review and approval.
Schedules maintenance windows and approves backout/rollback procedures.
Enforces operational governance and prevents unauthorized enterprise disruptions.
4
Take pre-deployment configuration and system backups.
Creates a recovery point corresponding to the exact current production state.
Allows rapid restoration if firmware flashing fails or causes unexpected downtime.
5
Execute patch installation in production and perform verification.
Applies security fixes and verifies routing protocols and service availability.
Completes the maintenance cycle within designated out-of-service hours.

Key Concept

Network Patch Management Lifecycle and Change Management Governance
Rate this question