AZ-700 Question 163
Select 2You manage a global web application with deployments in two Azure regions: East US and West Europe. Each region hosts multiple virtual machines behind a Standard Azure Load Balancer. You want users to connect to the geographically closest region for minimal latency, but if one region becomes unavailable, traffic from that region should automatically fail over to the other. You decide to use Azure Traffic Manager for global traffic distribution. Which two configuration steps should you take to achieve these requirements?
- A
Configure Traffic Manager using the Performance routing method so users are directed to the nearest endpoint by latency, with failover if one region is down.
- B
Configure Traffic Manager using the Weighted routing method, assigning equal weights to both regions to balance traffic evenly.
- C
Create endpoints in Traffic Manager that reference each region� Standard Load Balancer public IP or FQDN, allowing Traffic Manager to perform health checks and route traffic appropriately.
- D
Configure a single Standard Load Balancer to span across both regions, ensuring direct multi-region distribution without Traffic Manager.
- E
Enable DNS-based round-robin for each Load Balancer in Azure DNS Zones, so user requests are distributed between East US and West Europe automatically.
Show answer and explanation
Correct answers: A, C
Explanation
In a multi-region setup, Azure standard load balancers operate within each region to balance traffic among VMs in that region. For global routing, Azure Traffic Manager is used on top of these load balancers to route users to the closest healthy service endpoint. By configuring the Performance routing method and specifying each region� load balancer as an endpoint, the solution ensures minimal latency under normal conditions and automatic failover if a region becomes unavailable. For more details, refer to Microsoft� documentation on Azure Traffic Manager routing methods and regional load balancers (https://learn.microsoft.com/azure/traffic-manager/traffic-manager-routing-methods and https://learn.microsoft.com/azure/load-balancer/load-balancer-overview).
- A. Correct.
Correct. The Performance routing method examines network latency to determine the 'closest' region for each user. If any endpoint becomes unhealthy, Traffic Manager fails over to an available endpoint, meeting both low-latency and high-availability requirements.
- B. Incorrect.
Incorrect. Weighted routing distributes traffic based on assigned weights rather than proximity. This will not ensure minimal latency for users or automatically direct them to the closest region.
- C. Correct.
Correct. Pointing Traffic Manager to each region� Standard Load Balancer public IP or FQDN allows Traffic Manager to send health probes and route traffic to the available region, ensuring fault tolerance.
- D. Incorrect.
Incorrect. A single Standard Load Balancer cannot span across multiple regions in this manner. Azure Load Balancer is a regional service; global distribution requires a separate global load balancing solution (Traffic Manager in this scenario).
- E. Incorrect.
Incorrect. DNS-based round-robin does not ensure users connect to the nearest region or guarantee failover if one region is unhealthy. Traffic Manager� health monitoring and proximity-based routing are necessary for those capabilities.