1Z0-1072-25 Question 116
Single answerYou have deployed a multi-region web application in Oracle Cloud Infrastructure (OCI) and want automated failover when the primary region becomes unavailable. You created a DNS zone, configured a Traffic Management Steering Policy in 'Failover' mode, and defined two endpoints�one for each region. However, testing shows that traffic never switches to the secondary region when the primary endpoint is down. Which additional configuration is required for failover to function correctly?
- A
A. Set the steering policy to Geolocation-based routing for both endpoints
- B
B. Enable and configure a health check for each endpoint in the Traffic Management policy
- C
C. Create a separate DNS zone for each endpoint and alias them in the primary zone
- D
D. Configure Weighted Round Robin with a higher weight for the primary endpoint
Show answer and explanation
Correct answer: B
Explanation
To implement failover using OCI Traffic Management, each endpoint must have a health check associated with it. The steering policy uses health check results to determine if the primary endpoint is healthy. When it fails, the policy automatically shifts traffic to the secondary endpoint. See Oracle� OCI documentation on Traffic Management Steering Policies for details on enabling health checks and configuring failover routing.
- A. Incorrect.
A. Geolocation routing directs users based on geographic location, not endpoint health, so it would not ensure failover when the primary region fails.
- B. Correct.
B. This is correct. OCI Traffic Management requires health checks to continuously monitor endpoint availability. Once the primary endpoint is detected as unhealthy, traffic is redirected to the secondary endpoint.
- C. Incorrect.
C. This is unnecessary for failover. Having multiple DNS zones is more complex and does not address monitoring endpoint health or automatic switch-over.
- D. Incorrect.
D. Weighted Round Robin distributes traffic according to assigned weights, but it does not handle automated failover without health checks detecting an unresponsive endpoint.