When managing a globally distributed application that delivers both static and dynamic HTTP/HTTPS content, which Google Cloud Load Balancer configuration is most effective for ensuring high availability and low latency, particularly when a single IP address is needed for global routing?
- Global HTTP(S) Load Balancer
- Regional TCP Proxy Load Balancer
- Global SSL Proxy Load Balancer
- Regional External HTTP(S) Load Balancer
- Regional Internal HTTP(S) Load Balancer
Explanation:
The Global HTTP(S) Load Balancer is the optimal choice for this scenario. It provides a single anycast IP, enabling global routing of traffic to the nearest data center, which is crucial for low latency and high availability. This type of load balancer is specially designed to handle both static and dynamic HTTP/HTTPS content efficiently, distributing traffic across multiple regions worldwide. The Global HTTP(S) Load Balancer’s intelligent routing ensures optimal performance by responding to users from the nearest location. The other options, such as Regional Load Balancers or SSL Proxy Load Balancers, either do not support the required HTTP/HTTPS protocols or are not configured for global distribution, thus failing to meet the requirements for a globally distributed application.