Google Professional Cloud Network Engineer Question 385
Single answerGoogle Cloud PlatformYou are designing a load balancing solution for a web application running in multiple regions on Google Cloud. Traffic to the application must be distributed globally and directed to the nearest region based on user proximity. Additionally, the solution should support SSL termination and allow session affinity for users. Which load balancer type should you implement to meet these requirements?
- A
HTTP(S) Global External Load Balancer
- B
TCP/UDP Internal Load Balancer
- C
Regional HTTP(S) Load Balancer
- D
Network TCP/UDP External Load Balancer
Show answer and explanation
Correct answer: A
Explanation
The HTTP(S) Global External Load Balancer is the correct choice because it is optimized for distributing HTTP(S) traffic globally across multiple regions. It supports SSL termination, session affinity, and proximity-based routing to direct users to the nearest region. Other load balancer types either lack global reach, SSL termination, or are not suitable for HTTP(S) traffic.
- A. Correct.
The HTTP(S) Global External Load Balancer is designed for global traffic distribution, supports SSL termination, and provides features like proximity-based routing and session affinity. This matches all the requirements in the scenario.
- B. Incorrect.
The TCP/UDP Internal Load Balancer is used for internal traffic within a Virtual Private Cloud (VPC) and does not support global traffic distribution or SSL termination.
- C. Incorrect.
The Regional HTTP(S) Load Balancer is limited to regional traffic distribution and does not support global proximity-based routing, which is a key requirement in this scenario.
- D. Incorrect.
The Network TCP/UDP External Load Balancer is not suitable for HTTP(S) traffic and lacks advanced features like SSL termination and proximity-based routing.