A company is designing a highly available and globally distributed web application that needs to serve content from multiple regions with low latency. The application frontend is deployed on Compute Engine instances across several regions, and static assets are stored in Cloud Storage buckets. Which Google Cloud load balancing solution should be implemented to distribute traffic and minimize latency for users worldwide?
- ARegional External HTTP(S) Load Balancer
- BInternal HTTP(S) Load Balancer
- CGlobal External HTTP(S) Load Balancer
- DNetwork Load Balancer
Show answer & explanationAnswer & explanation
Correct answer: C. Global External HTTP(S) Load Balancer
The Global External HTTP(S) Load Balancer is designed for global applications, distributing traffic to backend services in multiple regions. It uses a single global IP address and Google's global network to direct users to the nearest healthy backend, ensuring low latency and high availability for both Compute Engine instances and Cloud Storage (via Cloud CDN integration).
Why the other options are wrong
- A. Regional External HTTP(S) Load Balancer serves traffic within a single region, not globally.
- B. Internal HTTP(S) Load Balancer is for traffic within a VPC network, not for external global users.
- D. Network Load Balancer is a pass-through load balancer for TCP/UDP traffic, not designed for HTTP(S) and global content distribution with low latency.
Global External HTTP(S) Load Balancer
A global, highly scalable load balancer for HTTP(S) traffic, distributing requests to backends across multiple regions to ensure high availability and low latency.
- Single global IP address for entry point.
- Leverages Google's global network for optimal routing.
- Supports backend services across multiple regions and integrates with Cloud CDN.
Memory trick: For 'Global' reach, 'External' access, and 'HTTP(S)' apps, you need the 'Global External HTTP(S) Load Balancer' to balance the load across the world.