Google Associate Cloud EngineerDeploying and implementing a cloud solutionMedium
A company is deploying a new web application that needs to serve users globally with low latency. The application's backend is hosted across multiple regions on Google Cloud. You need a load balancing solution that provides global load balancing, DDoS protection, and SSL termination at the edge. Which Google Cloud load balancer should you choose?
- AGlobal External HTTP(S) Load Balancer
- BInternal HTTP(S) Load Balancer
- CNetwork Load Balancer
- DRegional External HTTP(S) Load Balancer
Show answer & explanationAnswer & explanation
Correct answer: A. Global External HTTP(S) Load Balancer
The Global External HTTP(S) Load Balancer offers global load balancing, DDoS protection (via Cloud Armor integration), and SSL termination at Google's edge network, optimizing performance for globally distributed users.
Why the other options are wrong
- B. Internal HTTP(S) Load Balancer is for internal traffic within a VPC, not for external global users.
- C. Network Load Balancer is a Layer 4 load balancer, not suitable for HTTP(S) traffic, global distribution, or SSL termination at the edge.
- D. Regional External HTTP(S) Load Balancer operates within a single region, not suitable for serving users globally with low latency across multiple regions.
Global External HTTP(S) Load Balancer
A global, proxy-based Layer 7 load balancer that distributes HTTP(S) traffic to backends in multiple regions.
- Offers global availability and low latency via Google's edge network.
- Provides DDoS protection through Cloud Armor integration.
- Supports SSL/TLS termination at the load balancer.
Memory trick: Global for world, Regional for zone, Internal for inside.