Google Associate Cloud EngineerPlanning and configuring a cloud solutionMedium
A company is designing a highly available application that requires a regional IP address to be exposed to the internet. They want to ensure that traffic is distributed across multiple instances within that region and can failover automatically if an instance becomes unhealthy. Which Google Cloud load balancing option should they choose?
- AExternal TCP/UDP Proxy Load Balancing
- BExternal HTTP(S) Load Balancing (Global)
- CInternal TCP/UDP Load Balancing
- DRegional External HTTP(S) Load Balancing
Show answer & explanationAnswer & explanation
Correct answer: D. Regional External HTTP(S) Load Balancing
Regional External HTTP(S) Load Balancing provides a regional IP address and distributes HTTP(S) traffic to backend services within the same region. It supports health checks and automatic failover, ensuring high availability for applications exposed to the internet regionally.
Why the other options are wrong
- A. External TCP/UDP Proxy Load Balancing can provide a global IP and proxy TCP/UDP traffic, but the requirement is specifically for HTTP(S) and a regional IP address.
- B. External HTTP(S) Load Balancing (Global) provides a global IP address and distributes traffic across multiple regions, which is not desired for a regional IP requirement.
- C. Internal TCP/UDP Load Balancing is used for load balancing traffic *within* a VPC network, not for exposing applications to the internet.
Regional External HTTP(S) Load Balancing
A Google Cloud load balancing service that distributes HTTP(S) traffic to backend services within a specific region, providing a regional external IP address.
- Regional external IP address.
- Distributes HTTP(S) traffic.
- Supports health checks and automatic failover.
Memory trick: Regional HTTP(S) Load Balancing keeps regional apps balanced and healthy.