Examkin

Question

Difficulty: MediumChange Management Processes

An IT infrastructure coordinator is organizing change request documentation to upgrade the central enterprise resource planning (ERP) application server over an upcoming weekend. Which of the following elements MUST be included in the change request before submitting it to the Change Advisory Board (CAB) for review? (Select TWO.)

  1. A detailed scope of change outlining the exact software, hardware, and network services affected by the upgrade.Answer
  2. A documented rollback plan specifying procedures for restoring the server to its previous working state if the upgrade encounters critical issues.Answer
  3. C
    Written approval from CAB leadership allowing the coordinator to bypass post-implementation testing in order to shorten the maintenance window.
  4. D
    Validation results gathered from deploying the patch directly onto the live production server prior to submitting the request.

Answer

The correct elements that must be included in the change request are the detailed scope of change outlining affected systems and services, and a documented rollback plan specifying procedures for restoring the server if the upgrade fails.
Proper change management standards mandate that a formal request submitted to the Change Advisory Board includes a detailed scope of change (to identify all impacted systems and configurations) and a documented rollback plan (to provide an actionable recovery path if the change fails).

Step-by-Step Solution

1
Identify the mandatory documentation components required during the pre-change phase of formal change management.
Formal change proposals require defining the scope of change, risk/impact analysis, schedule, plan for change, end-user notification, and a documented rollback plan.
The Change Advisory Board (CAB) evaluates risk and business impact based on comprehensive documentation before approving implementation.
2
Evaluate each provided option against standard CompTIA change management workflow rules.
The scope of change and the rollback plan are necessary pre-implementation requirements. Pre-deploying changes to production or skipping post-implementation testing breaches proper change controls.
Changes must never be executed on production systems prior to CAB approval, and post-implementation verification must always be conducted post-deployment.

Key Concept

Change Management Processes and Documentation Requirements
Rate this question

Topics

Change Management Processes

More questions from this topic