Examkin

Question

Difficulty: HardConfiguration and Change Management

An enterprise organization plans to modify the BGP configuration across its global WAN edge routers to convert a full-mesh IBGP topology into a route reflector architecture. During the formal Change Advisory Board (CAB) review, the network lead submits a Request for Change (RFC) containing maintenance window schedules, sandbox testing logs, and step-by-step implementation scripts. However, the CAB refuses approval, noting that the document fails to define measurable criteria for identifying an unsuccessful deployment or explicit instructions for returning the network to a functional baseline if unpredicted routing loops occur. Which of the following elements must be added to the RFC to satisfy the CAB requirement for change authorization?

  1. A detailed rollback plan specifying explicit technical thresholds and triggers for aborting the implementation and restoring previous configuration statesAnswer
  2. B
    An updated maintenance window protocol allowing engineers to establish and test new troubleshooting hypotheses directly on production hardware during execution
  3. C
    A revised system recovery protocol substituting differential configuration file restoration with incremental full-image baseline re-imaging
  4. D
    A post-implementation modification reassigning host default gateways to physical interface IP addresses rather than virtual IP gateway addresses

Answer

A detailed rollback plan specifying explicit technical thresholds and triggers for aborting the implementation and restoring previous configuration states must be added to the RFC.
The correct answer identifies the missing rollback (backout) plan, which must detail the exact sequence of commands to revert configuration changes as well as predefined, measurable metrics (such as routing table instability, latency spikes, or packet loss thresholds) that mandate aborting the deployment.

Step-by-Step Solution

1
Analyze the CAB's objection in the scenario.
Identified that the RFC lacks defined failure conditions, quantitative rollback triggers, and specific steps to revert to the baseline state.
CAB approval requires risk mitigation documentation explaining how and when a change will be backed out if it causes network instability.
2
Evaluate standard Request for Change (RFC) mandatory components for enterprise network changes.
A rollback (backout) plan with explicit trigger metrics is required before high-risk routing topology changes are authorized.
Without predefined threshold triggers (e.g., packet loss exceeding 1%, BGP convergence timeout), maintenance teams may delay backing out, prolonging outages.
3
Select the option that directly addresses the missing RFC requirement.
The requirement for explicit technical thresholds and backout instructions directly matches the CAB's demand.
This provides a clear operational safety net for the maintenance window.

Key Concept

Rollback Plan and Trigger Criteria in Change Management
Estimated Time:2m 0s
Rate this question

Topics

Configuration and Change Management

More questions from this topic