CV0-002 · Question #480
A production IaaS database server contains PCI data and is a critical business capability. The CAB approved a normal code change release for QA and PROD to occur 30 minutes apart and to last a maximum
The correct answer is C. Submit an emergency CAB approval to change the time to after business hours. Given the delay and the critical nature of the production server and data, the best course of action is to seek an emergency change approval to adjust the deployment schedule to a less impactful time, ensuring proper procedure and minimizing risk.
Question
A production IaaS database server contains PCI data and is a critical business capability. The CAB approved a normal code change release for QA and PROD to occur 30 minutes apart and to last a maximum of one hour. The cloud DBA team is 45 minutes behind schedule, so they miss the start time on QA. As the cloud DBA, which of the following is the BEST course of action to apply the code change?
Options
- ASkip QA and apply the code change to PROD to meet time requirements
- BResubmit another change request for another time for approval
- CSubmit an emergency CAB approval to change the time to after business hours
- DChange the time in the CAB request and apply the code change at a more convenient time
How the community answered
(41 responses)- A29% (12)
- B7% (3)
- C49% (20)
- D15% (6)
Why each option
Given the delay and the critical nature of the production server and data, the best course of action is to seek an emergency change approval to adjust the deployment schedule to a less impactful time, ensuring proper procedure and minimizing risk.
Skipping QA and applying directly to PROD is a highly risky action for a critical system with PCI data and violates standard change management procedures, potentially causing significant outages or data integrity issues.
Resubmitting a normal change request would involve a lengthy approval process, delaying a necessary change without addressing the immediate need or the critical impact of waiting.
Since the team is 45 minutes behind, they've missed the approved window, and the server contains PCI data and is critical. Submitting an emergency CAB approval to move the change to after business hours acknowledges the missed window, maintains compliance with change management, and chooses a less disruptive time for a critical system.
Simply changing the time in the CAB request without explicit approval is a violation of change management policy, especially for a critical system, and could lead to unauthorized changes.
Concept tested: Change Management Procedures - Emergency Changes
Source: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/manage/considerations/change-management
Topics
Community Discussion
No community discussion yet for this question.