1Z0-1067-25 Question 82
Single answerYour company hosts a publicly accessible web application in the Phoenix region with a standby instance in the Ashburn region. You need to implement an automated failover strategy such that, if the primary site in Phoenix becomes unavailable, traffic seamlessly redirects to the standby site in Ashburn with minimal downtime. Which approach best accomplishes this requirement on Oracle Cloud Infrastructure?
- A
Deploy a regional Load Balancer in Phoenix with both Phoenix and Ashburn instances configured as backend servers for automatic failover.
- B
Configure an OCI Traffic Management Steering policy with health checks in DNS to direct traffic to Ashburn if Phoenix becomes unhealthy.
- C
Write a custom script using instance principals on the Phoenix instance to detect a failure and manually update the DNS record to point to Ashburn.
- D
Maintain a manual process where the operations team updates the domain� A record from Phoenix to Ashburn upon detecting an outage.
Show answer and explanation
Correct answer: B
Explanation
OCI Traffic Management Steering Policies allow you to configure automated failover solutions between regions. By applying DNS-based health checks that monitor the health of your primary application endpoint, traffic is routed to the standby endpoint if the primary becomes unreachable. For more details, refer to the Oracle Cloud Infrastructure Traffic Management documentation on using 'Failover' policies with health checks.
- A. Incorrect.
Option 1: A regional Load Balancer is restricted to a single region and cannot automatically fail over to a different region if the entire primary region becomes unavailable. Hence, this would not provide true cross-region failover.
- B. Correct.
Option 2: Using an OCI Traffic Management Steering policy with health checks in DNS is the recommended approach for automated cross-region failover. The health checks detect unavailability in the primary region and seamlessly direct traffic to the standby region.
- C. Incorrect.
Option 3: While a custom script could update DNS, it relies on the source instance (which could be unavailable) and manual coding. This introduces complexity and potential single points of failure rather than providing a robust, automated failover mechanism.
- D. Incorrect.
Option 4: Manually updating DNS records is time-consuming, prone to human error, and does not meet the requirement for minimal downtime or a seamless failover process.