Question

Difficulty: HardChange Management Processes

A database administrator is preparing to deploy a major version upgrade and schema modification to an organization's central transactional database system. To align with formal CompTIA change management processes, in which chronological order should the administrator execute the following steps?

  1. 1Document the purpose, business rationale, and technical scope of the proposed database change.
  2. 2Perform a risk assessment and construct a detailed backout plan for database restoration.
  3. 3Submit the change request to the Change Advisory Board (CAB) for formal evaluation and authorization.
  4. 4Broadcast maintenance window notifications to impacted business stakeholders and end users.
  5. 5Execute the database upgrade within the maintenance window and complete post-implementation testing.

Answer

The correct chronological sequence for standard change management processes is: 1) Document the purpose, business rationale, and technical scope; 2) Perform a risk assessment and construct a detailed backout plan; 3) Submit the change request to the Change Advisory Board (CAB) for formal evaluation and authorization; 4) Broadcast maintenance window notifications to impacted business stakeholders and end users; 5) Execute the database upgrade within the maintenance window and complete post-implementation testing.
The standard CompTIA change management workflow begins by defining the purpose and scope of the change. Next, potential risks are evaluated and a detailed backout plan is drafted. The completed proposal is then submitted to the Change Advisory Board (CAB) for formal review and authorization. Once CAB approval is obtained, maintenance window notifications are issued to end users and business leaders. Finally, the technician executes the upgrade during the maintenance window and performs post-implementation testing to confirm success.

Step-by-Step Solution

1
Identify the initial scope definition step.
Documenting the purpose and scope forms the baseline requirement for any change request.
A change request cannot begin without defining what is changing and why.
2
Identify the risk and contingency planning phase.
Conducting risk analysis and drafting a backout plan follows scope definition.
Understanding potential business impacts and fallback procedures is necessary to complete the change proposal.
3
Identify the formal authorization stage.
Submitting the change request package to the Change Advisory Board (CAB) follows documentation.
CAB approval grants official approval and schedules the authorized deployment window.
4
Identify stakeholder communication timing.
Sending end-user notifications takes place after securing CAB approval.
Users should only be informed of maintenance windows once authorized by governance.
5
Identify execution and post-change validation.
Executing the upgrade and conducting post-implementation testing occurs during the approved window.
Implementation and functional verification are the concluding steps of the operational change.

Key Concept

Change Management Lifecycle Phases
Rate this question