During a post-incident audit following a scheduled core network maintenance event, auditors noted that engineers spent several hours attempting to resolve unexpected packet loss on a newly updated WAN interface rather than reverting to the previous baseline configuration. Although the maintenance window eventually expired without restoring stable service, the deployment team had not breached any formal protocols because no specific metrics were defined to dictate when troubleshooting should cease and restoration must begin. Which specific element of the Request for Change (RFC) documentation was missing or improperly constructed?
- Specific rollback triggers and criteriaCevap
- BChange Advisory Board (CAB) emergency authorization
- CDifferential configuration backup verification
- DPost-implementation review (PIR) schedule
Cevap
Specific rollback triggers and criteria
A comprehensive Request for Change (RFC) must include detailed rollback triggers in addition to the step-by-step restoration procedure. Rollback triggers establish objective metrics (such as SLA threshold breaches, elapsed maintenance time, or unresolvable error rates) that mandate when implementation must be abandoned to safeguard business continuity.
Adım Adım Çözüm
Anahtar Kavram
Rollback Triggers and Reversion Criteria in Change Management