Google Associate Cloud EngineerEnsuring successful operation of a cloud solutionMedium
A company is hosting a critical web application on Google Cloud that needs to be accessible from multiple geographic regions with minimal latency. They require a single, global IP address for the application and the ability to distribute traffic efficiently to the nearest healthy backend instance. Which load balancing option should be implemented?
- AInternal HTTP(S) Load Balancing
- BExternal HTTP(S) Load Balancing
- CInternal TCP/UDP Load Balancing
- DNetwork TCP/UDP Load Balancing
Show answer & explanationAnswer & explanation
Correct answer: B. External HTTP(S) Load Balancing
External HTTP(S) Load Balancing provides a single global IP address, distributes traffic to backends based on proximity and health, and supports HTTP(S) traffic, making it ideal for a globally accessible web application with low latency requirements.
Why the other options are wrong
- A. Internal HTTP(S) Load Balancing is for load balancing traffic within a VPC network, not for external global access.
- C. Internal TCP/UDP Load Balancing is for internal TCP/UDP traffic within a region, not global external web traffic.
- D. Network TCP/UDP Load Balancing is an external, regional load balancer for TCP/UDP traffic, not global and not optimized for HTTP(S) web applications.
External HTTP(S) Load Balancing
A global, external load balancer on Google Cloud that distributes HTTP(S) traffic to backend instances across multiple regions using a single IP address.
- Provides a single global IP address.
- Offers advanced traffic management features (e.g., URL maps, health checks).
- Optimized for web applications that need global reach and low latency.
Memory trick: External HTTP is Global Web.