Examkin

Question

Difficulty: Very hardChange Management Processes

An enterprise systems administrator must perform a critical migration of an organizational database to a high-availability cloud architecture. To comply with standard CompTIA change management protocols, place the following administrative steps in the correct chronological order from first to last.

  1. 1Identify and document the purpose and scope of the proposed infrastructure change.
  2. 2Perform a comprehensive risk analysis to evaluate business impact and security implications.
  3. 3Develop the detailed implementation plan, rollback strategy, and sandbox testing protocol.
  4. 4Submit the compiled change documentation package to the Change Advisory Board (CAB) for review and authorization.
  5. 5Send end-user notifications outlining the approved maintenance window and expected operational impact.
  6. 6Execute post-implementation verification testing and finalize post-change documentation.

Answer

The correct chronological order for the change management lifecycle is: 1) Identify and document purpose and scope, 2) Perform risk analysis, 3) Develop implementation plan, rollback strategy, and testing protocol, 4) Submit package to the Change Advisory Board (CAB) for approval, 5) Send end-user notifications, and 6) Execute post-implementation verification testing and complete documentation.
The formal ITIL/CompTIA change management workflow requires that scope definition occurs first, followed by risk analysis, technical planning (including rollback and pre-testing), CAB review and approval, end-user communication, and finally post-implementation verification testing accompanied by ticket closure documentation.

Step-by-Step Solution

1
Define purpose and scope
Establishes clear boundaries and target systems affected by the change.
Operational scope must be clearly articulated first to understand potential downstream dependencies.
2
Conduct risk assessment
Identifies potential failure points, downtime risks, and business impacts.
Understanding risks directly dictates the safety measures and rollback procedures needed.
3
Formulate deployment plan, rollback plan, and sandbox testing
Produces step-by-step instructions for installation, recovery, and pre-deployment verification.
Complete implementation and fallback instructions must be fully prepared prior to seeking administrative board approval.
4
Obtain Change Advisory Board (CAB) authorization
Secures formal management authorization to proceed with the planned modification.
The CAB evaluates the risk assessment, timing, and rollback strategy to authorize the change request.
5
Issue end-user and stakeholder notifications
Alerts affected users to scheduled service interruptions.
Notifications must occur prior to maintenance, but only after formal approval guarantees the schedule.
6
Perform post-implementation testing and complete final documentation
Verifies full functionality post-change and logs the outcome in the ticketing system.
Post-implementation testing confirms system stability and completes compliance recordkeeping.

Key Concept

CompTIA A+ Core 2 Change Management Process Lifecycle
Rate this question

Topics

Change Management Processes

More questions from this topic