An administrator needs to load balance connections to the application server with the lowest number of. Which load balancing method meets these requirements?

Least Sessions tracks established sessions rather than active TCP connections, which is a different metric and does not directly measure the raw connection count on each server.

Ratio Least Connections (member) combines a configured ratio weight with connection count, so selection is influenced by the ratio value rather than purely by the lowest connection count.

Least Connections (member) counts connections only for a specific pool member (IP and port pair), not for the entire node, so a server hosting multiple services could still be overloaded while one member appears to have few connections.

Least Connections (node) directs new connections to the physical server node that has the fewest total active connections across all pools and services. Because it counts connections at the node level rather than per pool member, it gives the most accurate picture of overall server load. This is the correct choice when the goal is to route to the server with the absolute lowest connection count.