Examkin

Question

Difficulty: MediumConfiguration and Change Management

A network operations team is preparing to implement a major infrastructure modification involving the deployment of new interior routing protocol parameters across core enterprise routers. To ensure compliance with IT governance standards, what is the correct chronological sequence of steps the team must follow throughout the standard change management lifecycle?

  1. 1Draft a formal Request for Change (RFC) defining technical scope, business justification, risk impact analysis, and a detailed backout/rollback procedure.
  2. 2Submit the RFC for formal review and authorization by the Change Advisory Board (CAB).
  3. 3Validate the configuration modification in a lab/sandbox environment and schedule an official maintenance window.
  4. 4Apply the configuration changes to production routers during the maintenance window and execute functional verification tests.
  5. 5Update configuration baseline documentation, archive updated device state, and conduct a post-implementation review (PIR).

Answer

The correct sequence for standard IT change management is: 1) Draft the RFC including risk analysis and rollback plans, 2) Submit the RFC for CAB review and approval, 3) Perform pre-implementation lab validation and schedule the maintenance window, 4) Execute the change during the maintenance window and perform post-change verification, and 5) Update baseline documentation and conduct a post-implementation review.
Standard ITIL and enterprise change management practices require defining scope and rollback procedures in an RFC prior to obtaining formal CAB authorization. Once approved, changes are validated in a sandbox and scheduled during a low-impact maintenance window. Following execution and verification in production, configuration baselines must be updated and a post-implementation review conducted to finalize the change.

Step-by-Step Solution

1
Initiate the change request by drafting the formal RFC.
Defines change scope, potential impact, implementation steps, and mandatory rollback procedures.
Clear documentation of scope and rollback steps is necessary before any review or testing can occur.
2
Submit the RFC to the Change Advisory Board (CAB).
Obtain formal authorization and assessment from business and technical stakeholders.
CAB approval ensures business continuity and prevents uncoordinated or conflicting production changes.
3
Conduct sandbox validation and schedule the maintenance window.
Verifies configuration syntax in lab conditions and minimizes user impact by selecting low-traffic operational windows.
Pre-deployment testing ensures implementation readiness prior to modifying live infrastructure.
4
Deploy configuration changes and execute verification testing.
Applies changes on production equipment during the approved window and confirms service functionality.
Immediate post-change testing confirms whether the change succeeded or if immediate rollback is triggered.
5
Update configuration baselines and complete the Post-Implementation Review (PIR).
Maintains accurate inventory/configuration records and documents lessons learned to close the change ticket.
Documentation and PIR ensure configuration management database (CMDB) accuracy and operational traceability.

Key Concept

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

Topics

Configuration and Change Management

More questions from this topic