A network operations team needs to remediate a high-severity vulnerability disclosed in the operating system of the organization's core network switches. Place the standard patch management lifecycle steps in the correct chronological order from first to last.
- 1Perform vulnerability scanning and audit device inventory to identify all vulnerable core switch models and firmware versions.
- 2Apply the software patch to non-production switches in an isolated lab environment to test stability and verify software checksums.
- 3Submit a formal change request detailing deployment impact, maintenance window schedules, and a tested rollback plan to the Change Advisory Board.
- 4Deploy the firmware update across production core switches during the approved maintenance window using a staggered rollout strategy.
- 5Verify network connectivity, review switch log files, and archive the updated post-patch baseline configuration.
Cevap
The correct chronological sequence for the patch management lifecycle is: 1) Identify vulnerable assets and scan inventory, 2) Test the patch in an isolated lab environment, 3) Submit a change request with a rollback plan to the Change Advisory Board, 4) Deploy the firmware update during the approved maintenance window, and 5) Verify post-patch operation and update baseline documentation.
The correct sequence follows industry-standard patch management governance: discovering vulnerable inventory, validating patches in sandbox environments, gaining Change Advisory Board authorization with rollback strategies, executing the update during scheduled maintenance, and completing post-deployment auditing and baselining.
Adım Adım Çözüm
Anahtar Kavram
Standard Network Patch Management Lifecycle