Google Professional Cloud Network Engineer Question 23
Single answerGoogle Cloud PlatformYour team is deploying a web application on Google Cloud that serves a global audience. The application requires low-latency access for users worldwide, supports HTTPS traffic, and needs to handle millions of requests per second. Which load balancer should you choose to meet these requirements?
- A
HTTP(S) Load Balancer
- B
Internal HTTP(S) Load Balancer
- C
TCP/UDP Load Balancer
- D
Network Load Balancer
Show answer and explanation
Correct answer: A
Explanation
The HTTP(S) Load Balancer is the correct choice because it is specifically designed to handle global traffic for web applications, supports HTTPS, and provides low-latency access using Google's global network. Other load balancers either lack HTTPS support or are designed for internal traffic or non-HTTP(S) use cases.
- A. Correct.
The HTTP(S) Load Balancer is a global, fully-distributed load balancer that is ideal for serving web applications to a global audience. It supports HTTPS traffic, can handle millions of requests per second, and provides low-latency access by using the Google Cloud global network.
- B. Incorrect.
The Internal HTTP(S) Load Balancer is designed for internal traffic within a VPC, not for serving global audiences or handling external HTTPS traffic.
- C. Incorrect.
The TCP/UDP Load Balancer is suitable for non-HTTP(S) traffic and does not provide the advanced features required for web applications, such as HTTPS support or global distribution.
- D. Incorrect.
The Network Load Balancer operates at the transport layer and is used for high-performance, low-latency TCP and UDP traffic, but it does not support HTTPS or web-specific features.