AZ-700 Question 177
Select 2Your company hosts a globally distributed web application with endpoints in East US, West Europe, and Southeast Asia. You want to automatically direct users to the endpoint that provides the lowest latency. If any endpoint becomes unavailable, traffic should fail over to the next best-performing endpoint without manual intervention. Which two configurations should you include in your Azure Traffic Manager profile to meet these requirements?
- A
Use the 'Performance' routing method within the Azure Traffic Manager profile
- B
Enable health checks with the 'HTTPS' probe on each endpoint
- C
Use the 'Priority' routing method, making the East US endpoint primary
- D
Use 'Weighted' routing and assign higher weights to lower-latency endpoints
- E
Implement geo-fencing rules for each continent to direct requests to the closest endpoint
Show answer and explanation
Correct answers: A, B
Explanation
To achieve optimal latency-based routing with automatic failover, use Azure Traffic Manager with the Performance routing method and configure endpoint monitoring (health checks). The Performance method directs traffic to the endpoint that provides the lowest latency, while health checks ensure that if an endpoint fails, traffic is rerouted to the next best endpoint. For more information, refer to the Microsoft documentation on Azure Traffic Manager routing methods and endpoint monitoring: https://docs.microsoft.com/azure/traffic-manager/traffic-manager-monitoring.
- A. Correct.
Correct. The 'Performance' routing method ensures that traffic is directed to the closest Azure region based on network latency. This meets the requirement to route users to the lowest-latency endpoint.
- B. Correct.
Correct. Enabling health checks (endpoint monitoring) with HTTPS probes ensures that Azure Traffic Manager detects a failed endpoint. When an endpoint is down, it automatically reroutes traffic to the next available best-performing endpoint.
- C. Incorrect.
Incorrect. The 'Priority' routing method uses a simple ordered list of endpoints, always sending traffic to the highest-priority endpoint. This does not ensure low latency for all users since traffic is not distributed based on network performance.
- D. Incorrect.
Incorrect. 'Weighted' routing allows you to distribute traffic in specific proportions to each endpoint, but does not guarantee routing based on lowest latency. It is typically used for gradual migrations, testing, or traffic splitting.
- E. Incorrect.
Incorrect. Geo-fencing (Geographic routing) targets users based on their geographic location rather than latency. While it can direct users to geographically close endpoints, it does not dynamically re-route based on the actual real-time performance or automatically fail over if an endpoint becomes unavailable.