1Z0-1072-25 Question 131
Single answerYour company hosts an e-commerce application in two Oracle Cloud Infrastructure regions: us-phoenix-1 and us-ashburn-1. You want to route 70% of traffic to the Phoenix region and 30% to Ashburn under normal conditions. If the Phoenix region becomes unreachable, you require all traffic to failover automatically to Ashburn. Which Traffic Management Steering Policy configuration best meets these requirements?
- A
Create a single Weighted Steering policy with weights of 70 for Phoenix and 30 for Ashburn, enable health checks for both endpoints, and rely on the policy to remove the unhealthy endpoint from DNS responses.
- B
Create a Failover Steering policy with one primary endpoint in Phoenix and a secondary endpoint in Ashburn, each assigned the desired weights of 70 and 30, respectively.
- C
Use a Geolocation Steering policy to set 70% of traffic from the US to Phoenix and 30% to Ashburn, relying on default DNS routing for failover.
- D
Configure a Latency Steering policy across both regions; when Phoenix is unreachable, DNS automatically fails over to Ashburn through latency rules.
Show answer and explanation
Correct answer: A
Explanation
In Oracle Cloud Infrastructure DNS, Weighted Steering is the appropriate choice for scenarios that require a specific percentage of traffic distribution across multiple endpoints. By enabling health checks on both endpoints, the unhealthy endpoint is automatically excluded from DNS responses, providing an effective failover mechanism. Refer to the Oracle Cloud Infrastructure DNS documentation on Traffic Management Steering Policies for detailed setup steps and best practices (https://docs.oracle.com/en-us/iaas/Content/DNS/Concepts/trafficmanagement.htm).
- A. Correct.
Correct. A Weighted Steering policy with health checks will route traffic proportionally (70/30), and when the Phoenix endpoint is detected as unhealthy, the steering logic excludes it from DNS responses, automatically sending 100% of traffic to Ashburn. This setup satisfies both the weighting requirement and failover behavior.
- B. Incorrect.
Incorrect. A standard Failover Steering policy does not include weight distribution. Failover Steering simply defines a primary and secondary target without splitting traffic by percentage. You cannot assign a distinct weight of 70 and 30 in a single Failover policy.
- C. Incorrect.
Incorrect. Geolocation Steering routes traffic based on the client� origin rather than weights. You cannot split traffic 70/30 using geolocation-based rules alone. Additionally, geolocation does not inherently provide the exact failover behavior needed in this scenario unless further combined with health checks, which still does not allow precise weighting.
- D. Incorrect.
Incorrect. Latency Steering routes clients to the region with the lowest network latency, not a fixed percentage. Although health checks can remove an unhealthy endpoint from consideration, you cannot achieve a strict 70/30 traffic split using latency-based routing.