Examkin

Question

Difficulty: Very hardPatch Management and Software Maintenance

An enterprise organization needs to mitigate a newly disclosed critical vulnerability affecting the operating system of its core infrastructure network devices. To ensure business continuity and adhere to standardized patch management governance, place the following operational steps in the correct chronological order from first to last.

  1. 1Verify the digital cryptographic hash of the patch binary and execute deployment testing within an isolated lab environment.
  2. 2Submit a formal Request for Change (RFC) including lab test results, risk analysis, and a detailed rollback plan to the Change Advisory Board (CAB).
  3. 3Perform a complete system state and configuration backup and document operational performance baselines on target production devices.
  4. 4Apply the software update to target production network hardware during the authorized maintenance window.
  5. 5Execute post-installation functional verification tests and audit system logs to validate stable network operation and baseline adherence.

Answer

The correct sequence for enterprise patch management is: 1) Verify hash integrity and test in a staging lab environment, 2) Submit an RFC with rollback plans and test results for CAB approval, 3) Capture full configuration backups and operational baselines on target devices, 4) Apply the patch to production devices during the maintenance window, and 5) Conduct post-installation verification testing and log auditing.
Proper operational maintenance follows a rigorous lifecycle: sandbox testing and binary integrity verification must occur first to generate test evidence. Next, an RFC accompanied by test results and rollback steps is submitted for change control approval. Once approved, engineers capture pre-deployment device backups and baseline metrics immediately before applying the patch within the scheduled maintenance window. Finally, post-deployment testing and audit log reviews ensure system health before closing the change ticket.

Step-by-Step Solution

1
Verify and test the patch in isolation.
Patch integrity is confirmed via cryptographic hashes and functional behavior is validated in staging without impacting production.
Deploying unverified code directly to production risks network-wide outages.
2
Obtain change management authorization.
The Change Advisory Board reviews staging data, risk factors, and rollback procedures to approve the change schedule.
Enterprise governance mandates formal approval and verified rollback strategies prior to system alterations.
3
Establish safety baselines and backups.
Current running configurations and performance baselines are archived immediately before patch execution.
If an anomaly occurs during installation, technical teams must be able to restore the device to its exact pre-patch state.
4
Execute patch installation in production.
The software update is applied during the designated low-impact maintenance window.
Limiting implementation to approved maintenance windows minimizes user impact.
5
Perform post-patch audit and validation.
Control plane and data plane metrics are confirmed to match or exceed pre-patch baselines, and event logs show no abnormal errors.
Functional validation confirms that the update successfully remediated the issue without introducing unintended secondary errors.

Key Concept

Structured Patch Management Lifecycle and Change Management Procedures
Estimated Time:3m 0s
Rate this question

Topics

Patch Management and Software Maintenance

More questions from this topic