Examkin

Soru

Zorluk: OrtaConfiguration and Change Management

A network engineering team needs to update the primary TACACS+ server IP addresses and authentication keys across all wireless LAN controllers in an enterprise network. To adhere to organizational governance and minimize service disruption, the team must follow the standard change management lifecycle.

Place the following change management steps in the correct chronological order from first to last.

  1. 1Draft and submit a formal Request for Change (RFC) outlining the target scope, risk assessment, and proposed implementation schedule.
  2. 2Present the RFC to the Change Advisory Board (CAB) for impact evaluation and official authorization.
  3. 3Validate the TACACS+ configuration modifications and verify the rollback procedure in a pre-production staging environment.
  4. 4Deploy the TACACS+ configuration updates to production controllers during the scheduled maintenance window.
  5. 5Perform post-implementation testing, conduct a post-implementation review (PIR), and update the central configuration baseline.

Cevap

The correct chronological order begins with drafting and submitting the RFC, followed by obtaining CAB approval, validating the change in a lab environment, executing the deployment during the maintenance window, and concluding with post-implementation verification and documentation updates.
The standard change management lifecycle follows a strict sequential flow: Request initiation (RFC submission), Stakeholder review and approval (CAB approval), Technical validation (sandbox testing and rollback verification), Maintenance execution (production deployment), and Finalization (post-implementation review and baseline documentation update).

Adım Adım Çözüm

1
Initiate the formal change process by drafting and submitting the RFC.
Comprehensive documentation of proposed scope, risks, and rollback steps is created.
All structured changes require formal tracking and initial documentation before review.
2
Submit the RFC to the CAB for review.
Formal authorization and scheduling alignment are secured from key stakeholders.
CAB approval ensures business continuity and prevents uncoordinated network changes.
3
Conduct pre-deployment testing in a lab or staging environment.
Potential syntax errors and rollback failures are identified prior to production exposure.
Testing validates the implementation plan and ensures the rollback procedure is effective.
4
Implement the change on production devices during the designated maintenance window.
The configuration updates are applied to the active network infrastructure.
Performing execution inside approved windows minimizes operational impact to end users.
5
Verify service functionality, perform PIR, and update baseline configuration records.
The change workflow is formally closed and network documentation reflects current state.
Post-implementation review and baseline updates ensure configuration drift is avoided and institutional records remain accurate.

Anahtar Kavram

Standard ITIL/CompTIA Change Management Lifecycle Stages
Bu soruyu puanla

Konular

Configuration and Change Management

Bu konudan daha fazla soru