Examkin

Question

Difficulty: MediumConfiguration and Change Management

A network operations team is preparing to modify BGP path selection attributes across enterprise border routers to optimize traffic flow. Place the steps of the standard change management process in the correct order from initial proposal to final completion.

  1. 1Submit a detailed Request for Change (RFC) document detailing the proposed BGP modifications, potential business impact, and a clear rollback plan.
  2. 2Present the RFC to the Change Advisory Board (CAB) for formal review, risk assessment, and deployment authorization.
  3. 3Validate and test the BGP route policy updates in an isolated lab environment to ensure configuration syntax and expected traffic steering behavior.
  4. 4Apply the BGP configuration changes to the production border routers during an authorized maintenance window.
  5. 5Perform post-implementation verification testing and update the official enterprise network configuration baseline documentation.

Answer

The correct operational order for change management is: 1) Submit a detailed Request for Change (RFC) document detailing the proposed BGP modifications, potential business impact, and a clear rollback plan -> 2) Present the RFC to the Change Advisory Board (CAB) for formal review, risk assessment, and deployment authorization -> 3) Validate and test the BGP route policy updates in an isolated lab environment to ensure configuration syntax and expected traffic steering behavior -> 4) Apply the BGP configuration changes to the production border routers during an authorized maintenance window -> 5) Perform post-implementation verification testing and update the official enterprise network configuration baseline documentation.
A structured change management process follows a strict sequence: defining the scope and rollback plan in an RFC, securing stakeholder approval from the CAB, staging and testing in a lab, applying changes during an authorized maintenance window, and concluding with verification and documentation baseline updates.

Step-by-Step Solution

1
Identify the initial phase of the change management lifecycle.
Creating and submitting the Request for Change (RFC) with complete documentation (scope, risk analysis, rollback plan) occurs first.
Changes cannot be evaluated or scheduled without a formally documented proposal.
2
Determine the governing authorization step.
Presenting the RFC to the Change Advisory Board (CAB) for approval occurs second.
Stakeholders and management must authorize the change and approve the scheduled timeline before implementation activities proceed.
3
Identify pre-deployment validation procedures.
Testing and staging the configuration in a lab/sandbox environment occurs third.
Technical validation confirms command syntax and behavior before touching production systems.
4
Identify the execution phase.
Deploying changes to production network devices during the scheduled maintenance window occurs fourth.
Implementation must occur within approved outage/maintenance windows to protect service availability.
5
Identify the final wrap-up activities.
Performing post-implementation verification and updating configuration baselines occurs fifth.
Confirming functional status and recording the new state into documentation prevents configuration drift and closes out the change.

Key Concept

Structured Change Management Lifecycle
Estimated Time:1m 30s
Rate this question

Topics

Configuration and Change Management

More questions from this topic