Examkin

Question

Difficulty: MediumConfiguration and Change Management

A network operations team is preparing to modify BGP routing parameters across WAN edge routers to connect a secondary internet service provider. Before executing this scheduled modification, the lead network engineer must submit a formal Request for Change (RFC) to the Change Advisory Board (CAB). Which TWO of the following elements must be explicitly detailed within the RFC to ensure proper change management governance?

  1. A step-by-step rollback procedure with defined trigger conditions for reverting the changes if unexpected performance degradation occursAnswer
  2. A comprehensive risk and impact analysis detailing potential downtime and affected business servicesAnswer
  3. C
    Final post-implementation verification sign-offs from business stakeholders conducted prior to change submission
  4. D
    An automated script that permanently bypasses baseline configuration audits during maintenance windows

Answer

The correct elements that must be included in the Request for Change (RFC) are a step-by-step rollback procedure with defined trigger conditions, and a comprehensive risk and impact analysis detailing potential service disruptions.
A formal Request for Change (RFC) submitted to a Change Advisory Board (CAB) must contain a detailed risk and impact analysis to gauge potential service disruption, alongside a clear rollback plan with concrete triggers to safely undo changes if implementation fails during the maintenance window.

Step-by-Step Solution

1
Identify the core requirements of an enterprise Request for Change (RFC) document prior to CAB review.
Recognize that RFC documentation must justify the change, evaluate risk, specify the implementation steps, and detail emergency recovery procedures.
CAB approval relies on knowing the business impact, scheduling scope, and risk mitigation strategies.
2
Evaluate the necessity of a rollback plan with specific trigger criteria.
Confirm that a defined rollback plan allows engineers to abort and revert the change safely if issues arise during execution.
Without predefined trigger conditions, teams risk extending downtime beyond approved maintenance windows trying to troubleshoot ad-hoc errors.
3
Evaluate the risk assessment component.
Confirm that risk and impact analysis is required to determine maintenance window scheduling and business unit notifications.
Higher-risk changes targeting core WAN edge infrastructure require greater scrutiny and broader stakeholder awareness.

Key Concept

Request for Change (RFC) Components and Risk Management
Rate this question

Topics

Configuration and Change Management

More questions from this topic