A network administrator is preparing a formal Request for Change (RFC) to deploy updated security policies across several branch office routers. Before presenting the request to the Change Advisory Board (CAB) for formal review, which of the following elements must be included in the RFC documentation?
- A detailed rollback plan defining specific criteria and steps to restore the previous stable configuration if the deployment failsAnswer
- BAn authorization step to test the configuration change on live production routers during peak operational hours prior to CAB review
- CA restoration requirement specifying that network state recovery must rely on restoring the last differential configuration backup
- DA requirement to convert network management agents to SNMPv1 to allow unencrypted tracking of configuration updates
Answer
A detailed rollback plan defining specific criteria and steps to restore the previous stable configuration if the deployment fails
In standardized IT change management, a Request for Change (RFC) submitted to the Change Advisory Board (CAB) must include a comprehensive rollback plan. This ensures that if the change causes unexpected network failure or performance degradation, administrators can rapidly revert the environment to its previous known-good baseline using pre-defined triggers and explicit CLI procedures.
Step-by-Step Solution
Key Concept
Request for Change (RFC) Documentation and Rollback Procedures
Estimated Time:1m 30s