Google Associate Cloud EngineerEnsuring successful operation of a cloud solutionEasy
A company is deploying a new web application on Google Cloud that needs to serve users globally with low latency. The application's backend consists of stateless Compute Engine instances. Which load balancing option should be implemented to distribute traffic efficiently across multiple regions and provide a single global IP address?
- AInternal TCP/UDP Load Balancing
- BExternal HTTP(S) Load Balancing
- CNetwork Load Balancing
- DInternal HTTP(S) Load Balancing
Show answer & explanationAnswer & explanation
Correct answer: B. External HTTP(S) Load Balancing
External HTTP(S) Load Balancing is designed for global applications, providing a single global IP address and distributing traffic based on HTTP/HTTPS protocols to backends across multiple regions, ensuring low latency for users worldwide.
Why the other options are wrong
- A. Internal TCP/UDP Load Balancing is for internal services within a VPC network, operating at Layer 4, not for global external HTTP/HTTPS traffic.
- C. Network Load Balancing is a regional, pass-through load balancer operating at Layer 4, not suitable for global HTTP/HTTPS traffic distribution with URL-based routing.
- D. Internal HTTP(S) Load Balancing is for internal services within a VPC network, not for global external access.
External HTTP(S) Load Balancing
A global, Layer 7 load balancer in Google Cloud that distributes HTTP/HTTPS traffic to backends across multiple regions using a single global IP address, optimizing for latency and availability.
- Global reach with a single IP address
- Operates at Layer 7 (HTTP/HTTPS)
- Supports URL-based routing and SSL offloading
Memory trick: Load Balancers are like traffic cops, guiding cars to the best route.