Google Associate Cloud EngineerPlanning and configuring a cloud solutionMedium
A global company needs to deploy a new web application that serves users across multiple continents. The application requires a single, global IP address for entry and must dynamically route user requests to the closest healthy backend instance to minimize latency. Which load balancing option should be implemented?
- ANetwork Load Balancing (external passthrough)
- BInternal HTTP(S) Load Balancing
- CExternal HTTP(S) Load Balancing (global)
- DRegional External HTTP(S) 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 uses Google's global network to direct user requests to the closest healthy backend, optimizing for latency and providing global availability for web applications.
Why the other options are wrong
- A. Network Load Balancing (external passthrough) operates at Layer 4, supporting TCP/UDP traffic, but does not provide HTTP(S) features, global routing based on proximity, or a single global IP for web applications.
- B. Internal HTTP(S) Load Balancing is for internal services within a VPC network, not for external internet-facing applications.
- D. Regional External HTTP(S) Load Balancing provides a regional IP address and routes traffic within a single region, not globally.
External HTTP(S) Load Balancing (Global)
A global, Layer 7 (HTTP/HTTPS) load balancer that provides a single IP address and routes user traffic to the closest healthy backend instance across multiple regions.
- Global IP address
- Routes based on user proximity
- Supports HTTP/HTTPS traffic
Memory trick: GLOBAL (Global IP, Low Latency, Application Layer, Backend Health)