A database administrator is preparing a change request to update the database schema and apply a critical security patch to a primary Enterprise Resource Planning (ERP) server. The submitted proposal outlines the business justification, the exact scope of the modification, a comprehensive risk assessment, and detailed post-implementation testing procedures. Which of the following critical elements must be included in the change request before presenting it to the Change Advisory Board (CAB) for authorization?
- A documented rollback plan detailing the exact procedures to revert the database to its prior stable state if the patch causes unexpected failureAnswer
- BAn agreement granting the administrator pre-approved authorization to bypass CAB review during emergency maintenance windows
- CWritten sign-off showing end users tested and validated the patch directly inside the production environment prior to request submission
- DA request deferring post-implementation validation until the next scheduled quarterly release cycle
Answer
A documented rollback plan detailing the exact procedures to revert the database to its prior stable state if the patch causes unexpected failure
Before presenting a change proposal to the Change Advisory Board, the initiator must include a detailed, documented rollback plan. This ensures that if the database schema upgrade or security patch degrades system performance or causes an outage, technicians can quickly revert the ERP database to its original functional state without extended downtime.
Step-by-Step Solution
Key Concept
Required documentation elements of a formal change request (purpose, scope, risk analysis, plan for change, rollback plan, end-user notification, CAB approval, post-implementation testing).
Estimated Time:1m 30s