Examkin

Question

Difficulty: MediumChange Management Processes

A VoIP administrator is preparing a formal change request to migrate the enterprise on-premises Private Branch Exchange (PBX) to a cloud-based Session Initiation Protocol (SIP) trunking platform. To ensure minimal interruption to business operations and adhere to standard corporate governance, the change must follow the established change management lifecycle. In what chronological order should the administrator perform these key change management steps?

  1. 1Define the purpose and scope of the PBX migration.
  2. 2Conduct a risk analysis to evaluate potential call routing disruptions and downtime.
  3. 3Formulate a detailed rollback plan to restore the legacy PBX if the migration fails.
  4. 4Submit the completed change proposal to the Change Advisory Board (CAB) for formal authorization.
  5. 5Perform post-implementation testing and document final completion in the ticketing system.

Answer

The proper chronological order for the change management process is: 1. Define the purpose and scope of the PBX migration, 2. Conduct a risk analysis to evaluate potential call routing disruptions and downtime, 3. Formulate a detailed rollback plan to restore the legacy PBX if the migration fails, 4. Submit the completed change proposal to the Change Advisory Board (CAB) for formal authorization, and 5. Perform post-implementation testing and document final completion in the ticketing system.
The standard CompTIA change management lifecycle follows a structured sequence: starting with defining the purpose and scope of the change, followed by assessing the risks associated with the modification. Once risks are understood, the technician builds the plan for change along with a comprehensive rollback strategy. This documentation is submitted to the Change Advisory Board (CAB) for review and approval. After approval and deployment, the final step involves post-implementation testing and complete documentation update.

Step-by-Step Solution

1
Identify the initial scope and purpose definition phase.
Establishes what system is changing and why the change is required.
You cannot assess risk or build plans without knowing the precise scope.
2
Perform risk assessment on the defined scope.
Identifies potential failure points, affected users, and severity of potential downtime.
Risk evaluation directly informs mitigation strategies and fallback requirements.
3
Draft the plan for change and associated rollback procedures.
Creates step-by-step installation instructions and an explicit contingency backout strategy.
CAB approval requires a completed technical plan and verified rollback procedure before submission.
4
Submit documentation to the Change Advisory Board (CAB).
Obtains formal authorization and schedules the change window.
Unauthorized changes present extreme operational risk; CAB review ensures organizational alignment before deployment.
5
Execute deployment, perform post-implementation verification, and log documentation.
Confirms the change succeeded and updates configuration management databases (CMDB) and tickets.
The change management process is incomplete until testing verifies success and documentation is updated.

Key Concept

Standard Change Management Process Lifecycle
Rate this question

Topics

Change Management Processes

More questions from this topic