A network security administrator must apply a critical security patch to an enterprise perimeter firewall cluster to remediate a disclosed remote code execution vulnerability. Place the following patch management lifecycle steps in the correct chronological order from first step to last step.
- 1Verify downloaded patch file integrity using cryptographic checksums and review vendor release notes for software dependencies.
- 2Deploy and evaluate the patch within an isolated staging environment that mirrors the active firewall configuration.
- 3Submit a formal change management ticket detailing the scope, maintenance window, lab test results, and rollback plan.
- 4Perform a complete system baseline configuration and state backup of the active production firewall.
- 5Install the patch during the authorized maintenance window and perform post-implementation verification testing.
Cevap
The proper chronological patch management sequence is: (1) Verify file integrity and release notes, (2) Test the patch in an isolated lab staging environment, (3) Submit a formal change request ticket with rollback plan, (4) Perform a baseline backup of the production system, and (5) Install the patch during the maintenance window and validate operational status.
Standard network engineering best practices require a sequential lifecycle: initial verification of patch integrity, staging/testing in a non-production environment, formal change request authorization with documented rollback procedures, pre-deployment system backup, and post-installation verification testing.
Adım Adım Çözüm
Anahtar Kavram
Structured Network Patch Management Lifecycle and Change Management Control