An internal service exposes HTTP and TFTP to on-prem clients, and you need client stickiness across both services when load balancing across instances. Which session affinity do you choose?

Client IP affinity ensures that requests from the same client IP address are consistently routed to the same backend instance. This is crucial for maintaining session state across both HTTP and TFTP services when client stickiness is required. Since both services originate from the same client IP, this method effectively binds them to a single backend. "None" would distribute requests randomly, breaking stickiness. "Client IP and protocol" or "Client IP, port and protocol" are unnecessarily granular. While they would work, they introduce more complexity than needed for this scenario. The problem statement specifies stickiness across both services from the same client, making Client IP the most straightforward and efficient solution.