1Z0-1072-25 Question 115
Single answerYou have a global e-commerce application hosted in multiple Oracle Cloud Infrastructure regions (US West, US East, Europe, and Asia). You want to configure your DNS so that customers are directed to the region with the lowest latency. Which Oracle Cloud Infrastructure DNS Traffic Management Steering Policy should you set up to ensure users reach the closest endpoint based on network performance?
- A
Weighted Steering Policy
- B
Geolocation Steering Policy
- C
Performance Steering Policy
- D
Failover Steering Policy
Show answer and explanation
Correct answer: C
Explanation
In Oracle Cloud Infrastructure DNS Traffic Management, the Performance Steering Policy is specifically designed to evaluate network performance, such as latency, and direct clients to the optimal endpoint. This helps ensure the best possible user experience by automatically routing requests to the region with the lowest measured latency. Oracle's documentation for DNS Traffic Management (available in the OCI documentation) provides further detail on how to configure and optimize this policy for multi-region deployments.
- A. Incorrect.
Weighted Steering Policy allows you to distribute traffic based on specific weights assigned to each endpoint rather than latency or connection performance. It's useful when you want to allocate a certain percentage of traffic to particular endpoints, but it won't automatically route users to the lowest-latency region.
- B. Incorrect.
Geolocation Steering Policy routes users based on their geographic location. This can help comply with data residency requirements or direct traffic by user region, but it does not actively measure or optimize for latency.
- C. Correct.
Performance Steering Policy is the correct choice for automatically directing users to the closest endpoint based on real-time network performance metrics. This policy measures latency across endpoints and sends users to the region with the lowest latency.
- D. Incorrect.
Failover Steering Policy is designed for high availability by designating a primary endpoint and one or more secondary endpoints. Traffic only goes to the secondary endpoints if the primary fails, so it's not used for latency-based routing.