Examkin

Question

Difficulty: MediumConfiguration and Change Management

An enterprise network team prepares to update the operating system across central distribution switches to patch a critical security flaw. The lead engineer submits a formal Request for Change (RFC) to the Change Advisory Board (CAB). After evaluating the submission, the CAB rejects the RFC. Which of the following omissions in the RFC is the most likely reason for the board's rejection?

  1. The RFC did not contain a validated rollback procedure and specific performance metrics for triggering a change reversion.Answer
  2. B
    The RFC omitted a plan to conduct initial software deployment directly on live production switches during business hours.
  3. C
    The RFC scheduled the update window during maximum network utilization to guarantee high staff availability.
  4. D
    The RFC failed to include replacement commands for physical interface cabling during the switch operating system patch.

Answer

The RFC did not contain a validated rollback procedure and specific performance metrics for triggering a change reversion.
The correct answer highlights the necessity of a fully documented rollback plan and clear abort triggers within an RFC. A primary responsibility of the Change Advisory Board is risk management; any RFC lacking a clear, tested backout strategy for reverting to a functional baseline upon failure will be rejected.

Step-by-Step Solution

1
Analyze the core requirements of a Change Advisory Board (CAB) review for a Request for Change (RFC).
Identify that CAB approval requires comprehensive risk mitigation, including impact analysis, maintenance window scheduling, testing validation, and backout strategies.
CAB governance focuses on ensuring system stability and minimizing unmitigated operational risk.
2
Evaluate the missing element that presents the greatest risk during a core distribution switch upgrade.
The absence of a defined rollback plan leaves the network without a recovery strategy if the software update causes unforeseen instability or outage.
Without clear backout steps and trigger metrics, recovery from a failed change would be unstructured and prolonged.

Key Concept

Request for Change (RFC) Requirements and Rollback Planning
Rate this question

Topics

Configuration and Change Management

More questions from this topic