A network administrator prepares a Request for Change (RFC) to perform a major firmware upgrade on the primary core switches of a enterprise network. The submitted RFC includes the technical rationale, a comprehensive risk impact analysis, results from pre-deployment sandbox testing, and a designated maintenance window schedule. During the Change Advisory Board (CAB) review, the committee defers approval due to an omitted required section. Which of the following critical elements was missing from the submitted RFC?
- A formal rollback plan defining specific trigger thresholds and step-by-step procedures to revert to the previous stable state if validation failsAnswer
- BA documented diagnostic hypothesis log detailing potential lower-layer failure causes prior to change execution
- CA full differential backup restoration strategy covering all client workstations connected to the switch stack
- DAn explicit permit-all Access Control List entry appended to the bottom of all active switch interfaces
Answer
A formal rollback plan defining specific trigger thresholds and step-by-step procedures to revert to the previous stable state if validation fails
In standardized configuration and change management workflows, every Request for Change (RFC) must contain an explicit rollback plan prior to Change Advisory Board (CAB) approval. This ensures engineers can quickly and safely revert the network device to its baseline configuration if post-implementation testing fails.
Step-by-Step Solution
Key Concept
Standard Request for Change (RFC) Mandatory Components and Rollback Planning
Estimated Time:1m 15s