Choose the Right Load Balancer for Minimizing Latency

C.

In this scenario, the application receives SSL-encrypted TCP traffic on port 443 and has clients located all over the world. The goal is to minimize latency for the clients. To achieve this goal, a load balancing option should be used.

Option A: HTTPS Load Balancer An HTTPS Load Balancer is typically used for HTTP/HTTPS traffic, which is not the case in this scenario. Moreover, since SSL-encrypted TCP traffic is already being received, there is no need for an HTTPS Load Balancer.

Option B: Network Load Balancer A Network Load Balancer can handle TCP, UDP, and TLS traffic, which makes it a good option for SSL-encrypted TCP traffic. It offers low latency and high throughput by distributing traffic across multiple targets. This option is a good choice to minimize latency for clients located all over the world.

Option C: SSL Proxy Load Balancer An SSL Proxy Load Balancer is used for SSL-encrypted traffic, but it terminates the SSL connection and creates a new SSL connection to the backend instances. This can increase latency and is not a good option if the goal is to minimize latency for clients.

Option D: Internal TCP/UDP Load Balancer. Add a firewall rule allowing ingress traffic from 0.0.0.0/0 on the target instances. An Internal TCP/UDP Load Balancer is used for traffic within a VPC network, which is not applicable to this scenario since the clients are located all over the world. Adding a firewall rule allowing ingress traffic from 0.0.0.0/0 on the target instances is not a good security practice as it opens up the instances to traffic from anywhere on the internet.

Therefore, the best load balancing option for this scenario is B. Network Load Balancer, as it can handle SSL-encrypted TCP traffic and offers low latency and high throughput by distributing traffic across multiple targets.