Google Associate Cloud EngineerEnsuring successful operation of a cloud solutionHard
A company is designing a highly available architecture for a critical application. The application's backend services are deployed on Compute Engine instances across multiple zones within a single region. To distribute incoming traffic and ensure resilience against zone failures, they need a global load balancer that can direct traffic to the closest healthy instance. Which Google Cloud load balancing option should they choose?
- ANetwork Load Balancing
- BExternal HTTP(S) Load Balancing
- CInternal TCP/UDP Load Balancing
- DSSL Proxy Load Balancing
Show answer & explanationAnswer & explanation
Correct answer: B. External HTTP(S) Load Balancing
External HTTP(S) Load Balancing is a global, proxy-based load balancer that provides intelligent routing, global availability, and advanced traffic management features (like URL maps and SSL termination) for HTTP(S) traffic, making it ideal for highly available web applications across multiple zones.
Why the other options are wrong
- A. Network Load Balancing is a regional, pass-through load balancer primarily for non-HTTP(S) traffic, and it doesn't offer the global distribution or advanced features required for resilient web applications.
- C. Internal TCP/UDP Load Balancing is for internal traffic within a VPC network and cannot handle external internet traffic or provide global distribution.
- D. SSL Proxy Load Balancing is a global load balancer for non-HTTP(S) SSL traffic, but it doesn't provide the HTTP(S)-specific features like URL maps that are often needed for web applications.
External HTTP(S) Load Balancing
A global, proxy-based load balancer for HTTP and HTTPS traffic, offering advanced traffic management and resilience across multiple regions and zones.
- Global load balancer
- Proxy-based for HTTP(S) traffic
- Supports multiple regions/zones, intelligent routing
Memory trick: HTTP(S) external is the global gateway for your web apps.