Free Google Associate Cloud Engineer Actual Exam Questions - Question 7 Discussion
application are located all over the world. You want to minimize latency for the clients. Which load
balancing option should you use?
A, since HTTPS Load Balancer also offers global distribution and SSL offload, reducing latency.
B. The key here is minimizing latency for a global client base while handling SSL-encrypted TCP traffic on port 443. Since the traffic must stay encrypted all the way to the backend, using a Network Load Balancer makes sense because it operates at the transport layer and forwards TCP connections without decrypting them. This avoids the extra processing delay caused by SSL termination at the load balancer, unlike options A or C, which would decrypt and re-encrypt traffic. Also, internal load balancer (D) doesn’t fit since it’s meant for internal traffic, not global internet clients.
B, because it handles raw TCP traffic with minimal processing, so less delay globally.
Option B makes sense since it passes encrypted traffic straight through without decrypting, so it avoids extra processing and keeps latency low worldwide.
B imo, Network Load Balancer works at the connection level and can forward encrypted traffic without terminating SSL, which means less overhead and lower latency globally.
It’s B because Network Load Balancer handles raw TCP traffic and is designed for high performance and low latency, especially since it’s a global app with SSL encrypted traffic on port 443.
Maybe A is better since HTTPS Load Balancer works globally and does SSL termination, which could reduce latency by offloading SSL from backends. It also supports global backend distribution unlike B or D.
C. SSL Proxy Load Balancer works at the TCP level but can handle SSL traffic globally and offers SSL offloading, which reduces the load on backend instances and can improve latency. Unlike the Network Load Balancer, it has a global anycast IP which helps route clients to the nearest instance. Option A (HTTPS Load Balancer) terminates HTTPS and expects HTTP traffic, so if the app is handling raw SSL over TCP, it might not fit. D is clearly internal only, so that’s out too.
Network Load Balancer (B) is definitely out if we want global coverage since it only works regionally. Internal TCP/UDP Load Balancer (D) is for internal traffic, so that’s not matching the use case. HTTPS Load Balancer (A) terminates SSL at the load balancer and works globally, but if the question says SSL-encrypted TCP traffic, that might mean SSL isn’t terminated at the LB. That leaves SSL Proxy Load Balancer (C), which also supports global scaling and does SSL proxying without terminating HTTPS. Could that be better for keeping encryption end-to-end while still reducing latency worldwide?
Makes sense to pick B since Network Load Balancer handles TCP traffic directly and is optimized for high performance and low latency. It can also scale well globally, which fits the need for clients all over the world connecting on port 443 with SSL. Options like HTTPS Load Balancer (A) terminate SSL and operate at Layer 7, which adds overhead and might increase latency compared to a Layer 4 balancer. So, B feels like the right call here.
B