You create multiple Compute Engine virtual machine instances to be used at TFTP servers.
Which type of load balancer should you use?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
If you create multiple Compute Engine virtual machine instances to be used as TFTP servers, you would need to use a TCP proxy load balancer.
Here's why:
HTTP(S) load balancer: This type of load balancer is used for HTTP or HTTPS traffic. TFTP is not an HTTP-based protocol, so this option is not appropriate.
SSL proxy load balancer: This type of load balancer is used for SSL/TLS encrypted traffic. TFTP is not an SSL/TLS-based protocol, so this option is not appropriate.
TCP proxy load balancer: This type of load balancer is used for TCP traffic that needs to be proxied, such as TFTP. A TCP proxy load balancer can terminate the client-side connection, and establish a new connection to the server-side instance. This allows the load balancer to act as a middleman between the client and server, optimizing the traffic flow and improving the overall reliability and availability of the TFTP service.
Network load balancer: This type of load balancer is used for network traffic that needs to be distributed across multiple instances. However, it operates at the network layer (Layer 4) and does not support proxying or manipulating the traffic in any way. Since TFTP requires proxying, a network load balancer is not appropriate for this use case.
In summary, if you create multiple Compute Engine virtual machine instances to be used as TFTP servers, you should use a TCP proxy load balancer.