A network infrastructure team is preparing a complex change to transition an enterprise data center's core routing infrastructure from a static routing model to an internal BGP (iBGP) topology. The proposed configuration updates have already been tested in a isolated sandbox environment and reviewed by the Change Advisory Board (CAB). Which of the following components must be formally documented within the final Request for Change (RFC) before the maintenance window is approved for execution?
- ADetailed roll-forward procedures allowing engineers to patch device running configurations live during production impact without re-initiating CAB approval
- Specific criteria defining unacceptable performance impact alongside a pre-tested rollback plan and explicit rollback execution triggersAnswer
- CA schedule specifying differential backup execution for core switch operating system images during the middle of the active change window
- DAn explicit modification permit to disable implicit deny statements on all perimeter firewalls to facilitate initial routing convergence testing
Answer
Specific criteria defining unacceptable performance impact alongside a pre-tested rollback plan and explicit rollback execution triggers
A comprehensive Request for Change (RFC) must specify explicit, measurable triggers for failure (such as convergence timeouts or packet loss thresholds) along with a fully documented and tested rollback plan. This ensures that if unforeseen issues occur in production, the team can quickly restore the network to its verified baseline state before the maintenance window expires.
Step-by-Step Solution
Key Concept
Request for Change (RFC) Mandatory Rollback Plan and Execution Triggers