Question

Difficulty: MediumConfiguration and Change Management

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?

  1. Specific rollback triggers and criteriaAnswer
  2. B
    Change Advisory Board (CAB) emergency authorization
  3. C
    Differential configuration backup verification
  4. D
    Post-implementation review (PIR) schedule

Answer

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.

Step-by-Step Solution

1
Analyze the incident details provided in the scenario
Identify that the deployment team continued troubleshooting unforeseen failures past reasonable thresholds because explicit quantitative or temporal boundaries for aborting the change were absent.
Engineers need objective criteria to make unbiased decisions during maintenance windows when changes fail.
2
Evaluate the components of a comprehensive Request for Change (RFC)
Determine that rollback plans must contain both the technical procedure for reversion and explicit rollback triggers (e.g., maximum allowable downtime, specific performance degradation limits, or clock-time cutoffs).
Without pre-defined rollback triggers, teams frequently over-commit to troubleshooting during active maintenance, leading to extended service outages.

Key Concept

Rollback Triggers and Reversion Criteria in Change Management
Rate this question