Professional Cloud ArchitectManage and provision solution infrastructureMedium
A company is deploying a multi-region application on Google Cloud and needs to ensure that user traffic is directed to the closest healthy backend instance to minimize latency. They also require protection against DDoS attacks and advanced traffic management capabilities like URL-based routing. Which type of Cloud Load Balancing should they implement?
- ANetwork Load Balancer (TCP/UDP)
- BExternal HTTP(S) Load Balancer
- CInternal TCP/UDP Load Balancer
- DInternal HTTP(S) Load Balancer
Show answer & explanationAnswer & explanation
Correct answer: B. External HTTP(S) Load Balancer
The External HTTP(S) Load Balancer is a global, Layer 7 (HTTP/S) load balancer that offers advanced traffic management features like URL-based routing, SSL termination, and integrates with Cloud Armor for DDoS protection. Its global nature ensures traffic is directed to the closest healthy backend, fulfilling all the specified requirements for a multi-region application.
Why the other options are wrong
- A. Network Load Balancer operates at Layer 4 (TCP/UDP), is not global, and does not provide advanced HTTP/S traffic management or DDoS protection.
- C. Internal TCP/UDP Load Balancer is for internal traffic within a region at Layer 4, not for external global applications with L7 features.
- D. Internal HTTP(S) Load Balancer is for internal traffic within a VPC, not for external internet-facing applications.
External HTTP(S) Load Balancer
Google Cloud's global, Layer 7 load balancer for internet-facing applications, offering advanced traffic management, SSL/TLS offload, and DDoS protection.
- Global reach, directs traffic to closest healthy backend
- Layer 7 (HTTP/S) features: URL-based routing, session affinity
- Integrates with Cloud Armor for DDoS protection
Memory trick: Load Balancer: Traffic cop for your cloud apps.