Examkin

Question

Difficulty: MediumChange Management Processes

A database administrator is planning to upgrade the database engine of an enterprise Human Resources (HR) application. To comply with formal organizational change management procedures, place the following change management phases in the correct chronological order from first step to last step.

  1. 1Document the purpose and scope of the change and perform a comprehensive risk assessment.
  2. 2Develop the detailed implementation plan, backout (rollback) strategy, and sandbox testing results.
  3. 3Submit the change request to the Change Advisory Board (CAB) for review and formal authorization.
  4. 4Notify impacted end users and department stakeholders regarding the upcoming maintenance window.
  5. 5Execute post-implementation testing and document the completion of the change in the ticketing system.

Answer

The correct chronological order of change management phases is: 1) Document purpose/scope and perform risk assessment, 2) Develop implementation, rollback, and testing plans, 3) Submit to the Change Advisory Board (CAB) for formal approval, 4) Notify impacted stakeholders of the maintenance window, and 5) Execute post-implementation testing and complete documentation.
Proper CompTIA change management follows a structured lifecycle: establishing purpose and performing risk assessment -> formulating implementation, rollback, and testing plans -> submitting to the Change Advisory Board (CAB) for approval -> notifying stakeholders of the approved maintenance window -> performing post-implementation testing and completing documentation.

Step-by-Step Solution

1
Define the change requirements
Identify the purpose, scope, and potential risk factors associated with upgrading the database engine.
Every change request begins with defining what needs to change and evaluating potential business and technical impacts.
2
Formulate technical plans
Create implementation procedures, a rollback strategy, and document sandbox testing outcomes.
Formal change management requires fully formed technical and backout plans prior to seeking authorization.
3
Seek formal authorization
Present the comprehensive change proposal to the Change Advisory Board (CAB) for approval.
The CAB evaluates business impact, scheduling conflicts, and risk mitigation before granting authorization.
4
Communicate with affected parties
Issue notifications to stakeholders about planned service disruptions and maintenance schedules.
End users and business leaders must be informed in advance so they can prepare for operational impact.
5
Validate and finalize
Perform verification testing post-change and document final status in the ticketing workflow.
Testing ensures the system is fully operational and lessons learned or completion metrics are logged.

Key Concept

CompTIA Change Management Lifecycle Order
Rate this question

Topics

Change Management Processes

More questions from this topic