AZ-305 Practice Question 79: Cross Region Load Balancer TCP Failover
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 8 · question 9 of 10
A gaming company runs a custom TCP based matchmaking service on Standard Load Balancers deployed in three Azure regions. Players must connect to the closest healthy region automatically, and if a region's regional load balancer becomes unavailable, traffic must fail over to the next closest healthy region within seconds, all under a single anycast public IP address. The protocol is not HTTP or HTTPS, so a Layer 7 web based routing service cannot inspect it. Which solution should the architect recommend?
Show answer and explanation
Answer:
The cross-region, or global tier, Standard Load Balancer operates at Layer 4 and distributes traffic across regional Standard Load Balancers behind a single global anycast public IP. It routes each connection to the closest healthy region and probes regional load balancer health every few seconds, shifting traffic automatically to the next closest healthy region if one becomes unavailable, which fits a non-HTTP TCP protocol.
Azure Front Door and Application Gateway are Layer 7 services that route based on HTTP or HTTPS semantics such as host headers and URL paths, so they cannot inspect or route a custom TCP matchmaking protocol. Traffic Manager works at the DNS layer, resolving a hostname to a regional endpoint IP address based on performance or other routing methods, but failover depends on DNS propagation and client-side DNS caching, which is far slower than the automatic data-plane failover that a cross-region load balancer provides.
Reference: Global load balancer overview