1Z0-1072-25 Question 39
Select 2Your company has received a notification from Oracle about an upcoming infrastructure maintenance event that will require a reboot of compute instances in your production region. You run a business-critical application on these instances, and you want to minimize potential downtime. Which two approaches are recommended to prepare for this maintenance event? (Choose two.)
- A
Configure a custom maintenance window to control when your compute instances will be rebooted.
- B
Manually patch the underlying hypervisor before the event to match the planned maintenance schedule.
- C
Distribute your compute instances across multiple Availability Domains and perform rolling reboots during the maintenance window.
- D
Ignore the maintenance notification because the maintenance will be entirely transparent with no impact on your instances.
- E
Stop all your compute instances well in advance so they are powered off when the maintenance begins.
Show answer and explanation
Correct answers: A, C
Explanation
Oracle Cloud Infrastructure maintenance events can require compute instance reboots. By setting a custom maintenance window, you can control timing and coordinate any necessary restarts. Using high-availability designs�such as spreading instances across multiple Availability Domains�lets you perform rolling reboots without taking your entire application offline. Refer to Oracle� official documentation on Maintenance and Availability (https://docs.oracle.com/en-us/iaas/Content/General/Reference/maintenance.htm) for best practices on minimizing downtime and ensuring service continuity during scheduled events.
- A. Correct.
Configuring a custom maintenance window is a recommended best practice. It allows you to choose a specific time that causes minimal disruption to your workloads, ensuring you have control over when reboots happen.
- B. Incorrect.
Manually patching the hypervisor is not possible for OCI tenants. Oracle manages the underlying infrastructure, so this option is incorrect and is a common misconception about how maintenance events are handled.
- C. Correct.
Distributing instances across multiple Availability Domains helps ensure high availability. Performing rolling reboots allows you to keep part of your application online while you update or reboot the other parts, thereby reducing downtime.
- D. Incorrect.
Ignoring the notification is risky because most infrastructure maintenance events involve reboots or other temporary service interruptions. You need to plan your application� availability around these notifications.
- E. Incorrect.
Stopping all instances is not recommended, as it could extend your downtime unnecessarily. Instead, planning a rolling restart or using high availability designs is more effective.