You have an application that receives SSL-encrypted TCP traffic on port 443. Clients for this application are located all over the world. You want to minimize latency for the clients. Which load balancing option should you use?
You have an application that receives SSL-encrypted TCP traffic on port 443. Clients for this application are located all over the world. You want to minimize latency for the clients. Which load balancing option should you use?
To minimize latency for clients located all over the world and receiving SSL-encrypted TCP traffic on port 443, the optimal choice is the HTTPS Load Balancer. The HTTPS Load Balancer is a global solution specifically designed to handle secure SSL/TLS traffic and provides features such as HTTP/2 and connection multiplexing, which significantly reduce latency. It is capable of terminating SSL/TLS connections, enhancing its ability to efficiently manage encrypted traffic and distribute it to backend instances based on IP address or request content.
SSL Proxy Load Balancing support for the following ports: 25, 43, 110, 143, 195, 443, 465, 587, 700, 993, 995, 1883, 3389, 5222, 5432, 5671, 5672, 5900, 5901, 6379, 8085, 8099, 9092, 9200, and 9300. When you use Google- managed SSL certificates with SSL Proxy Load Balancing, the frontend port for traffic must be 443 to enable the Google-managed SSL certificates to be provisioned and renewed.
C is correct
Go for C. We are taking exam so read the question smart. For HTTPS traffic use HTTPS load balancer. For non-HTTP traffic, use SSL Proxy Load Balancer. (https://cloud.google.com/load-balancing/docs/ssl). Network Load Balancer (Extenral TCP/UDP network load balancer) for regional pass through traffic (https://cloud.google.com/load-balancing/docs/network). Here it mentioned SSL-encrypted TCP traffic all over the world, go for SSL proxy load balancer. Read the keyword "SSL-encrypted TCP" and "all over the world". Keep it simple, don't over complicated yourself
A. HTTPS Load Balancer The HTTPS Load Balancer is the best option for minimizing latency for clients located all over the world. HTTPS Load Balancer provides a global solution for load balancing secure (SSL/TLS) traffic, including the ability to distribute traffic to backend instances based on IP address, based on request content, or both. It is designed to handle encrypted traffic and can terminate SSL/TLS connections, making it the optimal choice for an application that receives SSL-encrypted TCP traffic on port 443. Additionally, HTTPS Load Balancer has built-in features to minimize latency, such as support for HTTP/2 and connection multiplexing, which can reduce the number of connections and round trips required to complete a request.
C. SSL Proxy Load Balancer would be the best option for minimizing latency for the clients, as it terminates SSL traffic and forwards unencrypted traffic directly to the backend instances. This reduces the amount of processing and latency associated with SSL encryption/decryption. Additionally, because the clients are located all over the world, using a global SSL Proxy Load Balancer can distribute traffic to the closest backend instances for the clients, further reducing latency.
This is a tricky question. First point to consider is the port. TCP 443 port is used for HTTPS traffic. Second : SSL Proxy LB is intended for non-HTTPs traffic and for HTTPs traffic, it should be global HTTPs LB. Answer is A : HTTPS Load Balancer.
Answer is A From this Link: https://cloud.google.com/load-balancing/docs/ssl it states this: External SSL proxy load balancers are intended for non-HTTP(S) traffic. For HTTP(S) traffic, we recommend that you use an external HTTP(S) load balancer. 443 is HTTPS traffic for those saying 443 isn't https https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=443
C. SSL Proxy Load Balancer The SSL Proxy Load Balancer is designed specifically for SSL-encrypted traffic and provides SSL termination, minimizing latency for clients worldwide by handling SSL connections efficiently. This load balancer is suitable for applications that receive SSL-encrypted TCP traffic on port 443, making it a good choice for the scenario.
C is the correct Answer, SSL proxy load balancer with Traffic Type - TCP with SSL offload, for global IPv4, IPv6, external ports for load balancing - 25,43,110,143,195,443,465,587,700,993,995,1883,5222
Correct answer: (A) Global https load balancer https://cloud.google.com/load-balancing/docs/choosing-load-balancer
The question does not mention the layer 7 protocol (HTTP/S), only that is TCP (layer 4). This is way it should be C
HTTPs uses both SSL encryption and TCP layer as well. 443 port is HTTPs default port, which suggests A.
443 is default port for SSL/TLS communication. I can be HTTPs or it can be somethink else.
A: Although both HTTPS and SSL Proxy load balancers can both be used for global external load balancing, for HTTP(S) traffic, Google recommends that you use HTTP(S) Load Balancing. https://cloud.google.com/load-balancing/docs/ssl
To add further clarity, Google documentation says: "External SSL Proxy Load Balancing is intended for non-HTTP(S) traffic. For HTTP(S) traffic, we recommend that you use HTTP(S) Load Balancing." Port 443 (mentioned in the question) is for HTTPS https://cloud.google.com/load-balancing/docs/ssl
You are assuming that this is HTTPS traffic. But from question we know that it is SSL-encrypted TCP , so we can't use HTTPS load balancer. Moreover we will be missing HTTP data for URL map
C is the right answer , read it carefully TCP traffic
It's not about TCP Traffic. It's about minimizing latency, so in order to achieve that we need to use SSL termination which is a feature of the SSL Proxy LB.
I think i'm wrong cuz HTTPS use TCP and SSL, because HTTPS is HTTP over TLS/SSL(now) so the ans in my pov is A
Correct answer is C. External proxy load balancer supports global and regional scope. While external passthrough network load balancer supports regional scope.
SSL Proxy Load Balancer
The answer is C. "SSL encrypted TCP" traffic is not exactly SSL traffic. SSL encrypted TCP traffic is usually used for non HTTP application. Port 443 is supported by SSL proxy load balancer so this isn't what will differentiate the two for us. The main part here is "SSL encrypted TCP" traffic.
443 is HTTTPs
I remember compliance question was in "Associate Cloud Engineer Certification Learning Path". And I answered SSL Proxy Load Balancer but it was incorrect. Correct answer is A.