1Z0-1072-25 Question 132
Single answerYou manage an e-commerce application deployed in two OCI regions: one in the US (us-ashburn-1) and another in Europe (eu-frankfurt-1). You want to send 60% of traffic to the US region and 40% of traffic to the European region under normal circumstances. However, if the US region becomes unreachable, you want all traffic to automatically flow to the EU region until the US is healthy again. Which Traffic Management Steering Policy configuration meets these requirements?
- A
Use a Weighted Round Robin steering policy with endpoint health checks enabled for both regions.
- B
Use a Weighted Round Robin steering policy without health checks configured.
- C
Use a Failover steering policy with us-ashburn-1 set as the primary and eu-frankfurt-1 as the secondary.
- D
Use a GeoLocation steering policy that directs US-based users to us-ashburn-1 and EU-based users to eu-frankfurt-1.
Show answer and explanation
Correct answer: A
Explanation
Weighted Round Robin with health checks is the recommended solution for mixing traffic distribution ratios (60/40) under normal conditions and automatically failing over when a region becomes unhealthy. By configuring health checks on both endpoints, the steering policy can detect outages and reroute traffic to the healthy region. Refer to the Oracle Cloud Infrastructure DNS documentation on Traffic Management Steering Policies (https://docs.oracle.com/en-us/iaas/Content/DNS/Reference/trafficmanagement.htm) for best practices and configuration details.
- A. Correct.
Correct. Weighted Round Robin with health checks allows you to assign percentages of traffic to each endpoint (60% to US, 40% to EU), and if one endpoint becomes unhealthy, traffic can automatically reroute to the other. Health checks are essential for detecting and responding to endpoint unavailability.
- B. Incorrect.
Incorrect. While a Weighted Round Robin policy can distribute traffic according to assigned weights, it cannot automatically fail over to the second region if the first region becomes unavailable without health checks. Without health checks, the policy has no way of knowing when a region is down.
- C. Incorrect.
Incorrect. A Failover steering policy can switch all traffic to the secondary region if the primary region is down, but it does not support distributing traffic in a 60/40 ratio during normal operation. Failover steering only supports active/standby behavior.
- D. Incorrect.
Incorrect. A GeoLocation steering policy routes requests based on the geographic origin of the client, not based on custom weights or failover logic. It does not permit sending 60% of global traffic to one region and 40% to another.