An HTTP load-balancing virtual server is configured with Least Response Time as the load-balancing algorithm, but requests appear to be using Round Robin. What could cause this behavior?

• A. The services that are bound to the HTTP virtual server are using the PING monitor.
• B. The virtual server is in startup round robin mode.
• C. Least Response Time CANNOT be used as a load-balancing algorithm on an HTTP virtual server.
• D. The NetScaler configuration has NOT been saved yet.

Answer: (B)

Least Response Time relies on live response-time measurements from health probes to pick the best back-end server. When a HTTP virtual server is configured to use Least Response Time, the appliance first needs data from the bound servers to rank them. If there isn’t enough data yet—such as right after creation or a recent change—it enters startup round robin mode and distributes requests evenly using Round Robin until it has enough samples to compute meaningful response times. Once enough measurements exist, it switches to Least Response Time and future requests go to the server with the lowest observed response time. That’s why you might see Round Robin behavior even though the configured method is Least Response Time.