Question 640
A TCP application has regional Standard public Azure Load Balancers in West Europe and East US. The client network permits only one unchanged IP address, and the company requires Azure to direct traffic to a healthy regional deployment across regions without DNS-based failover. Which Azure solution meets those constraints?
Explanation
Correct Answer
Azure Global Load Balancer is the cross-region tier of Azure Standard Load Balancer. Its Global-tier Standard public IP is a static anycast frontend advertised in participating regions, with regional public load balancers used as backends. It routes clients toward an eligible healthy regional deployment while retaining one advertised public IP address. This directly meets the TCP/Layer 4 and no-DNS-switchover requirements, subject to supported regions and service limitations.
Incorrect Answers
Regional-tier public IP resources are associated with a single Azure region and do not automatically advertise an anycast frontend across multiple regions. A regional load balancer can handle local high availability, but if its region is unavailable it cannot by itself shift new connections to the service deployed in East US. The scenario requires a cross-region endpoint with one static IP.
Private addresses are not internet-routable public frontend endpoints. Even if connectivity is provided through a private VPN or ExpressRoute network, separate VM private addresses do not provide the single public anycast IP requested by the client. This design does not implement automatic cross-region health-based routing through the Azure public load-balancing service.
DNS-based routing can expose multiple address values or depend on TTLs and recursive resolver caching during failover. Clients cannot be guaranteed to observe one unchanging public IP when the authoritative record changes to a different regional endpoint. A Global Load Balancer uses one Global-tier static public frontend and selects its healthy regional public load balancers without requiring the client to switch DNS destinations.