Professional Cloud ArchitectDesign and plan a cloud solution architectureEasy
A global e-commerce company needs to ensure its web application remains highly available and performs optimally for users worldwide. They want to serve content from the closest available region and automatically distribute traffic based on server load and health checks. Which Google Cloud load balancing solution should they implement?
- AGlobal External HTTP(S) Load Balancer
- BRegional External HTTP(S) Load Balancer
- CNetwork Load Balancer
- DInternal HTTP(S) Load Balancer
Show answer & explanationAnswer & explanation
Correct answer: A. Global External HTTP(S) Load Balancer
The Global External HTTP(S) Load Balancer is designed for global traffic distribution, leveraging Google's edge network to direct users to the nearest healthy backend. It provides features like content-based routing, SSL offload, and automatic traffic management for optimal performance and availability across regions.
Why the other options are wrong
- B. Regional External HTTP(S) Load Balancer focuses on traffic within a single region, not for global distribution and serving from the closest available region worldwide.
- C. Network Load Balancer is a Layer 4 (TCP/UDP) load balancer, while the requirement implies Layer 7 (HTTP/S) features for web applications and content routing.
- D. Internal HTTP(S) Load Balancer is for internal traffic within a VPC network, not for external global user traffic.
Global External HTTP(S) Load Balancer
A global, Layer 7 load balancer that distributes HTTP/S traffic to backends across multiple regions, leveraging Google's global network.
- Provides a single anycast IP address globally.
- Directs users to the closest healthy backend.
- Includes features like SSL offload, content-based routing, and Cloud CDN integration.
Memory trick: Load balancers direct traffic, choosing the right one depends on global reach and protocol.