Soru

Zorluk: OrtaConfiguration and Change Management

A network operations team plans to upgrade the core layer-3 switches in a healthcare system's primary data center. Place the following change management phases in the correct sequence from start to finish.

  1. 1Submit a formal Request for Change (RFC) detailing the scope, business justification, and affected systems.
  2. 2Perform an impact analysis, conduct a risk assessment, and establish a detailed rollback procedure.
  3. 3Present the proposed change to the Change Advisory Board (CAB) for evaluation and formal authorization.
  4. 4Execute the switch firmware and configuration upgrade during an authorized maintenance window.
  5. 5Conduct post-implementation verification testing and update configuration baseline documentation.

Cevap

The correct operational order is: 1) Submit a formal Request for Change (RFC); 2) Perform an impact analysis, risk assessment, and establish a rollback procedure; 3) Present the proposed change to the Change Advisory Board (CAB) for authorization; 4) Execute the upgrade during an authorized maintenance window; 5) Conduct post-implementation verification testing and update configuration baseline documentation.
The standard change management lifecycle begins with RFC submission, followed by risk analysis and rollback planning. The complete proposal is then submitted to the CAB for authorization. Once authorized, implementation takes place within an approved maintenance window, followed by post-implementation validation and baseline documentation updates.

Adım Adım Çözüm

1
Identify the initial request phase
Submitting the RFC initiates the change lifecycle.
Change tracking begins with formal documentation of what is changing and why.
2
Analyze risk and fallback options
Impact analysis, risk scoring, and rollback plans are attached to the RFC.
The approving body requires technical risk metrics and back-out plans to evaluate the change.
3
Seek administrative authorization
The Change Advisory Board (CAB) reviews and approves the change.
Execution cannot proceed without stakeholders and advisory boards granting formal permission.
4
Perform the technical deployment
The upgrade is executed within the scheduled maintenance window.
Changes must be deployed only during approved time frames to prevent unplanned outages.
5
Validate and finalize baseline documentation
Verification testing is completed, and baseline network documentation is updated.
Closing a change requires verifying success and ensuring documentation reflects current state.

Anahtar Kavram

Standard ITIL Change Management Life Cycle
Bu soruyu puanla