Google Professional Cloud Network Engineer Question 388
Single answerGoogle Cloud PlatformYour company has deployed a web application on Google Cloud using Compute Engine instances in multiple regions. You want to configure load balancing to ensure high availability, reduce latency for users globally, and provide SSL termination. Which load balancer should you configure to meet these requirements?
- A
HTTP(S) Load Balancer
- B
Internal TCP/UDP Load Balancer
- C
Network Load Balancer
- D
TCP Proxy Load Balancer
Show answer and explanation
Correct answer: A
Explanation
The HTTP(S) Load Balancer is specifically designed for global load balancing of HTTP(S) traffic. It supports a single IP address for users globally, reduces latency through edge caching, and provides SSL termination, which meets all the requirements outlined in the scenario. Other load balancers either lack global capabilities, are designed for different protocols, or do not support SSL termination.
- A. Correct.
HTTP(S) Load Balancer is the correct choice for global load balancing, SSL termination, and handling HTTP/HTTPS traffic. It provides features like content-based routing and support for a single IP address for users worldwide.
- B. Incorrect.
Internal TCP/UDP Load Balancer is designed for internal traffic within a region and does not support global load balancing or SSL termination, making it unsuitable for this scenario.
- C. Incorrect.
Network Load Balancer is used for external load balancing of non-HTTP(S) traffic and operates at the transport layer. It does not provide SSL termination or global load balancing.
- D. Incorrect.
TCP Proxy Load Balancer is used for global load balancing of non-HTTP(S) TCP traffic, such as SSL-protected traffic. However, it does not support content-based routing or handling HTTP(S) traffic directly.