Google Professional Cloud Network Engineer Question 387
Single answerGoogle Cloud PlatformYou are designing a global application hosted on Google Cloud that requires low-latency access for users in multiple geographic regions. The application must distribute traffic across multiple backend services, support HTTPS, and provide a static IP for the front end. Which load balancing option should you choose?
- A
HTTP(S) Load Balancer with global backend services
- B
Internal TCP/UDP Load Balancer
- C
Network Load Balancer
- D
Regional External HTTP(S) Load Balancer
Show answer and explanation
Correct answer: A
Explanation
The HTTP(S) Load Balancer with global backend services is the best option for a global application that requires HTTPS, low-latency access across multiple regions, and a static IP. It operates at Layer 7, supports global traffic distribution, and meets the application's requirements. Other options either lack HTTPS support, do not provide global distribution, or are designed for internal traffic.
- A. Correct.
Correct. HTTP(S) Load Balancer with global backend services is the appropriate choice for a global application that requires HTTPS, low-latency access, traffic distribution across multiple regions, and a static IP.
- B. Incorrect.
Incorrect. Internal TCP/UDP Load Balancer is used for internal traffic within a VPC and does not support global traffic distribution or HTTPS.
- C. Incorrect.
Incorrect. Network Load Balancer is used for high-performance, low-latency traffic at Layer 4, but it does not support HTTPS or global traffic distribution.
- D. Incorrect.
Incorrect. Regional External HTTP(S) Load Balancer only provides traffic distribution within a single region and does not meet the global traffic distribution requirement.