Contoso Retail has two Azure regions (EastUS and WestEurope). They must publish a single public IP that provides global client connectivity and forwards traffic to regionally deployed backend pools (VM Scale Sets) while keeping backend health and NAT rules regional. You plan to use Azure Load Balancer. Which configuration meets this requirement with minimal changes to the existing regional backend setups?

A Global (cross-region) Public Load Balancer (Global tier) is designed for this exact scenario. It provides a single public IP address that can distribute traffic across backend pools in multiple Azure regions. This allows Contoso Retail to maintain their existing regional backend health probes and NAT rules, as the global load balancer simply references these regional resources. The other options introduce additional layers of complexity or do not directly support global traffic distribution with regional backend management. Standard Load Balancers are regional and cannot directly span regions. Application Gateway and Front Door are Layer 7 solutions, whereas the requirement implies a Layer 4 load balancing solution and emphasizes minimal changes to existing regional backend setups, which a Global Load Balancer directly addresses.