Google Associate Cloud EngineerPlanning and configuring a cloud solutionHard
A global e-commerce company wants to deploy a highly available and low-latency web application across multiple geographic regions. They need a single external IP address for their application and automated traffic distribution to the nearest healthy backend. Which Google Cloud load balancing option should they choose?
- AInternal HTTP(S) Load Balancing
- BNetwork Load Balancing (external, TCP/UDP)
- CExternal HTTP(S) Load Balancing (Global)
- DSSL Proxy Load Balancing
Show answer & explanationAnswer & explanation
Correct answer: C. External HTTP(S) Load Balancing (Global)
External HTTP(S) Load Balancing (Global) provides a single global IP address and distributes HTTP/S traffic across multiple regions to the closest healthy backend, ensuring high availability and low latency for global web applications. It's a Layer 7 load balancer specifically designed for web traffic.
Why the other options are wrong
- A. Internal HTTP(S) Load Balancing is for traffic within a VPC network, not for external global applications.
- B. Network Load Balancing (external) operates at Layer 4 (TCP/UDP) and is regional, not global, nor does it provide the advanced HTTP(S) features needed for a web application.
- D. SSL Proxy Load Balancing handles SSL/TLS termination globally but is for non-HTTP(S) traffic; External HTTP(S) Load Balancing is for web applications.
External HTTP(S) Load Balancing (Global)
A global, Layer 7 (HTTP/S) load balancer on Google Cloud that provides a single external IP address, distributing traffic to backend services across multiple regions based on proximity and health checks. It's ideal for global web applications requiring high availability and low latency.
- Layer 7 (HTTP/S) load balancing
- Global scope with a single IP address
- Distributes traffic to nearest healthy backend
- Supports SSL termination
- Ideal for global web applications and APIs
Memory trick: Load Balancers: Direct your 'traffic' with the right 'traffic cop'!