1Z0-1072-25 Question 130
Select 2You manage a global application hosted in three OCI regions: Ashburn (US East), Phoenix (US West), and Frankfurt (Europe). You need to split incoming requests from North American users evenly between Ashburn and Phoenix. European users should primarily be directed to Frankfurt, but if that endpoint fails a backup in Ashburn should handle the traffic automatically. Which TWO configurations should you include when setting up your Traffic Management Steering Policy?
- A
A single Geolocation rule for all global regions, sending all traffic to the nearest endpoint based on location
- B
A Geolocation rule specifically configured for Europe, routing traffic to Frankfurt with Ashburn set as the fallback if Frankfurt fails
- C
Two separate Latency rules per endpoint, assigning each region the closest healthy endpoint
- D
A Weighted Round Robin rule for North American traffic, assigning equal weights (e.g., 50 each) to Ashburn and Phoenix
Show answer and explanation
Correct answers: B, D
Explanation
To meet the outlined requirements, you must configure a Geolocation rule to handle European traffic with failover built in (Frankfurt primary, Ashburn backup) and a Weighted Round Robin rule for North American traffic (50/50 between Ashburn and Phoenix). This approach satisfies the need for region-specific routing and proper failover behavior. Refer to Oracle Cloud Infrastructure documentation on Traffic Management Steering Policies for details on creating and combining Geolocation and Weighted rules.
- A. Incorrect.
Option 1 is incorrect because a single Geolocation rule for all global regions does not allow you to fine-tune the backup scenario for Frankfurt or to split North American traffic evenly. You need more granular rules.
- B. Correct.
Option 2 is correct because you need a Geolocation rule specifically targeting European users to direct them to Frankfurt and set up Ashburn as a fallback for failover. This ensures continuity if Frankfurt goes offline.
- C. Incorrect.
Option 3 is incorrect because Latency Steering rules direct users to the endpoint with the lowest latency, not necessarily splitting traffic evenly or respecting a fallback scenario based on the region failing. Latency does not fulfill the requirement to split North American traffic or provide a Europe → Ashburn failover.
- D. Correct.
Option 4 is correct because Weighted Round Robin steering for North America allows you to distribute traffic evenly between Ashburn and Phoenix. This meets the requirement of splitting load equally between these two endpoints.