Google Professional Cloud Network Engineer Question 25
Single answerGoogle Cloud PlatformYou are designing a global e-commerce application hosted in Google Cloud that must handle high volumes of traffic with low latency. The application has users across multiple continents and requires SSL termination. Additionally, you want to route requests to the nearest backend based on the user's geographic location. Which Google Cloud load balancer should you choose?
- A
HTTP(S) Load Balancer
- B
TCP/UDP Load Balancer
- C
Internal Load Balancer
- D
Network Load Balancer
Show answer and explanation
Correct answer: A
Explanation
The HTTP(S) Load Balancer is the best choice for this scenario as it is designed for managing global, external HTTP(S) traffic. It provides SSL termination, geographic-based routing, and the ability to route traffic to the nearest backend for low latency. It also supports features like cross-region failover and advanced request routing, making it ideal for high-traffic, global applications like e-commerce platforms.
- A. Correct.
The HTTP(S) Load Balancer is the correct choice for global load balancing with SSL termination and the ability to route requests based on geographic location. It supports advanced features like URL-based routing and cross-region backend balancing, making it ideal for global applications.
- B. Incorrect.
The TCP/UDP Load Balancer is designed for non-HTTP traffic and does not support SSL termination or geographic routing. It is not suitable for this use case.
- C. Incorrect.
The Internal Load Balancer is used for internal, private IP-based traffic within a VPC and does not support global or external traffic, making it unsuitable for a public-facing global application.
- D. Incorrect.
The Network Load Balancer is used for high-performance Layer 4 traffic and does not support features like SSL termination or geographic-based routing, which are required in this scenario.