Question

Difficulty: MediumPatch Management and Software Maintenance

A network administrator needs to apply a critical vendor security update to the organization's core infrastructure routers. In what order should the administrator execute the patch management lifecycle steps from first to last?

  1. 1Acquire the patch package and verify its cryptographic hash against the vendor's published checksum.
  2. 2Deploy and test the software patch in an isolated sandbox lab environment.
  3. 3Perform a complete baseline configuration backup of target devices and submit a change management request.
  4. 4Install the update across production routers during an authorized maintenance window using a staggered rollout.
  5. 5Conduct post-installation system audits and monitor telemetry metrics to confirm ongoing stability.

Answer

The correct sequence for the patch management lifecycle is: 1) Verify the cryptographic hash of the patch file, 2) Test the patch in an isolated sandbox lab, 3) Perform a baseline backup and obtain change management approval, 4) Install the patch across production devices during an approved maintenance window, and 5) Conduct post-installation system audits and performance monitoring.
A structured patch management lifecycle prioritizes risk reduction by verifying package integrity and testing in a lab staging environment first. After validating stability, administrators secure device baseline backups and obtain change management authorization. The patch is then deployed during an approved maintenance window, followed by post-implementation verification to ensure system integrity.

Step-by-Step Solution

1
Verify patch file integrity
Confirmed authentic update package file
Ensures corrupted or altered binary files are never staged or executed.
2
Lab staging and non-production testing
Validated patch stability in isolation
Exposes unexpected software behavior or service defects before impacting active production networks.
3
Configuration baseline backup and change approval
Authorized change ticket with a rollback baseline
Establishes administrative compliance and secures a recovery point if installation fails.
4
Production deployment during maintenance window
Patch applied using a phased rollout strategy
Restricts operational impact to scheduled downtime and limits blast radius.
5
Post-patch verification and telemetry monitoring
Verified operational compliance and remediated security posture
Ensures services are functioning as intended without performance degradation.

Key Concept

Standard Patch Management Lifecycle
Rate this question