Following an unannounced configuration drift incident, a network engineer submits a formal Request for Change (RFC) to deploy a standardized configuration baseline across all datacenter access switches. The RFC details the proposed technical modifications, maintenance window timing, and post-deployment verification procedures. However, the Change Advisory Board (CAB) defers authorization because the proposal fails to specify the exact performance thresholds (such as interface error spikes or packet loss rates) that would mandate immediately reversing the deployment. Which critical component of the RFC requires revision before approval can be granted?
- The rollback plan and its activation triggersAnswer
- BThe disaster recovery full system restoration sequence
- CThe post-implementation review and auditing framework
- DThe initial troubleshooting methodology and hypothesis testing plan
Answer
The rollback plan and its activation triggers
A comprehensive Request for Change (RFC) must include a explicit rollback (backout) plan that specifies both the technical steps to revert to the previous baseline and the measurable abort criteria (such as packet loss or interface error thresholds). Without clear rollback triggers, engineers cannot determine when a deployment has failed and must be aborted to protect production services.
Step-by-Step Solution
Key Concept
Request for Change (RFC) Essential Elements and Rollback Triggers
Estimated Time:1m 30s