Google Associate Cloud Engineer

Get started today

Ultimate access to all questions.

Explanation:

The SSL Proxy Load Balancer is the correct choice for minimizing latency for global users by offloading SSL close to them and routing traffic through Google's network. It specifically supports SSL-encrypted TCP traffic on port 443, among others.

HTTPS Load Balancer (A) is designed for HTTP/HTTPS traffic, not SSL-encrypted TCP traffic.
Network Load Balancer (B) operates at the Transport Layer but isn't optimized for SSL traffic.
Internal TCP/UDP Load Balancer (C) is for internal VPC traffic, not external SSL traffic.

For more details, refer to Google Cloud Load Balancing documentation.

Explanation:

HTTPS Load Balancer (A) is designed for HTTP/HTTPS traffic, not SSL-encrypted TCP traffic.
Network Load Balancer (B) operates at the Transport Layer but isn't optimized for SSL traffic.
Internal TCP/UDP Load Balancer (C) is for internal VPC traffic, not external SSL traffic.

For more details, refer to Google Cloud Load Balancing documentation.

Comments (0)

No comments yet.

As a software engineer at a startup, you've developed an image search API service used globally. The service handles SSL-encrypted TCP traffic on port 443. Which load balancing option would best minimize latency for your clients?

Real Exam

Network Load Balancer

17.0%

Internal TCP/UDP Load Balancer

15.1%

HTTPS Load Balancer

20.8%

SSL Proxy Load Balancer

47.2%