Five Azure VMs (Windows Server 2016) host websites and are fronted by Azure load balancer LB1. To make sure a visitor always reaches the same backend server across requests, what should you configure?

Setting session persistence to "Client IP and protocol" ensures that all requests from a specific client IP address are directed to the same backend VM. This is crucial for applications that maintain session state on the server, preventing users from losing their session data if subsequent requests are routed to a different server. Creating a health probe monitors the health of backend instances but doesn't guarantee session stickiness. Enabling Floating IP (Direct Server Return) is used for specific scenarios like high-performance applications where the backend server responds directly to the client, but it doesn't inherently provide session persistence. Changing the load-balancer protocol to UDP is irrelevant as HTTP/HTTPS (TCP) is typically used for websites, and UDP doesn't offer session persistence in this context.