Google Associate Cloud EngineerDeploying and implementing a cloud solutionMedium
A company is designing a highly available and scalable web application that will be deployed across multiple regions. They need a global load balancer that can distribute traffic to the nearest healthy backend and also provide SSL offloading. Which Google Cloud load balancing solution should they choose?
- AInternal HTTP(S) Load Balancer
- BNetwork Load Balancer
- CGlobal External HTTP(S) Load Balancer
- DRegional External HTTP(S) Load Balancer
Show answer & explanationAnswer & explanation
Correct answer: C. Global External HTTP(S) Load Balancer
The Global External HTTP(S) Load Balancer is a global, proxy-based Layer 7 load balancer that offers features like SSL offloading and distributes traffic to backends in the nearest healthy region, fulfilling all requirements.
Why the other options are wrong
- A. Internal HTTP(S) Load Balancer is for internal traffic within a VPC, not global external traffic.
- B. Network Load Balancer is a Layer 4 (TCP/UDP) load balancer and does not provide SSL offloading or global distribution to nearest region at the application layer.
- D. Regional External HTTP(S) Load Balancer operates within a single region and cannot distribute traffic across multiple regions globally.
Global External HTTP(S) Load Balancer
A global, proxy-based Layer 7 load balancer that distributes HTTP(S) traffic to backend services across multiple regions, offering features like SSL offloading and content-based routing.
- Provides a single global IP address for your application.
- Directs users to the closest healthy backend.
- Supports SSL/TLS termination at the load balancer.
Memory trick: Global HTTP(S) Load Balancer is the 'global' choice for 'web' traffic.