Question

Difficulty: MediumChange Management Processes

A cloud administrator is preparing to migrate an enterprise on-premises file server to a cloud-based storage infrastructure. To ensure minimal disruption to business operations and adhere to organizational policy, the administrator must follow formal change management procedures. In what sequence should the administrator execute the following steps of the change management workflow?

  1. 1Document the purpose, scope, and technical details of the cloud migration proposal.
  2. 2Perform a formal risk assessment to evaluate business impact and potential service downtime.
  3. 3Develop the step-by-step implementation plan alongside a detailed rollback strategy.
  4. 4Submit the completed change request package to the Change Advisory Board (CAB) for approval.
  5. 5Perform the migration during the maintenance window, conduct post-implementation testing, and update documentation.

Answer

The correct sequence begins with defining the purpose and scope, followed by conducting a risk assessment, creating implementation and rollback plans, obtaining CAB approval, and finally executing the change with post-implementation testing and documentation.
Standard CompTIA A+ change management workflow requires establishing scope/purpose first, evaluating risk second, building implementation/rollback plans third, securing CAB authorization fourth, and completing execution, post-testing, and documentation fifth.

Step-by-Step Solution

1
Define purpose and scope of the proposed change.
Establishes clear boundaries and technical requirements for the migration.
A documented scope is necessary to understand what is being changed and why.
2
Conduct a risk analysis.
Identifies risk levels, potential disruptions, and affected business units.
Evaluating risk helps determine the necessary safety precautions and rollback requirements.
3
Formulate implementation procedures and a rollback plan.
Produces the technical instructions and backout steps if deployment fails.
Change management guidelines require a complete rollback plan before seeking management approval.
4
Request authorization from the Change Advisory Board (CAB).
Obtains formal business and technical approval to proceed.
The CAB must review all risk analyses and backout strategies to approve the scheduled maintenance window.
5
Execute the change, test functionality, and update documentation.
Completes the migration, verifies normal operation, and updates system records.
Deployment occurs only after approval; post-testing ensures operational stability and complete configuration management tracking.

Key Concept

CompTIA Change Management Lifecycle
Rate this question