Soru

Zorluk: ZorPatch Management and Software Maintenance

An enterprise network operations team must urgently remediate a newly published zero-day vulnerability affecting the routing protocol daemon across core Layer 3 switches. Which of the following procedures should the engineering team execute during the emergency maintenance window to preserve high availability and maintain change management compliance? (Select TWO.)

  1. Stagger the patch installation across redundant switch pairs, updating the secondary node first while verifying control-plane stability before patching the primary node.Cevap
  2. Export a full running-configuration file and verify an existing rollback system image copy in flash storage immediately prior to applying the software patch.Cevap
  3. C
    Apply the software patch simultaneously to both active and standby core nodes to complete the maintenance window as quickly as possible.
  4. D
    Skip functional post-patch verification testing to fast-track the emergency change advisory board documentation approval.

Cevap

The engineering team must stagger the patch installation across redundant switch pairs—updating the secondary node first—and export running configurations alongside validating fallback system image copies in flash storage prior to patch execution.
Staggering software updates across redundant high-availability switch pairs preserves uninterrupted traffic flow while allowing the secondary device to be tested post-patch. Additionally, saving the current running configuration and confirming a valid rollback image in local storage ensures that the core switch can be restored quickly if the patch causes instability.

Adım Adım Çözüm

1
Perform Pre-Patch Preparation and Backups
System configurations and baseline images are saved and verified for fast recovery.
Before executing software updates on critical infrastructure, administrators must secure current running configurations and confirm flash memory contains a functional rollback image.
2
Execute Staggered Redundant Deployment
High availability is maintained as active traffic is handled by the unpatched primary node while the secondary node updates.
Upgrading high-availability pairs sequentially prevents network-wide outages caused by unexpected patch failure or crash loops.
3
Perform Post-Patch Verification and Change Documentation
The update is validated, and change management records are updated post-maintenance.
Verifying control-plane stability and routing protocol convergence ensures full operational capability before completing change tickets.

Anahtar Kavram

High-Availability Staggered Patching and Rollback Verification
Bu soruyu puanla