If an HTTP vServer using Least Response Time appears to behave like Round Robin, which condition is most likely the cause?

If an HTTP vServer using Least Response Time appears to behave like Round Robin, which condition is most likely the cause?

• A. The services bound to the vServer are using a 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 needs real response-time data from the pool of servers to decide which one is fastest. When a vServer starts, there’s no history yet, so the appliance uses Round Robin by default to distribute the initial requests evenly until it can collect enough latency measurements. Once traffic begins, it records each server’s response times and then starts directing requests to the servers with the lowest latency, moving away from pure Round Robin. The other factors listed don’t cause this initial Round Robin behavior: a monitoring type like PING affects health checks, not the initial load-balancing decision, and the option of not having saved the configuration doesn’t create this startup behavior.

Least Response Time needs real response-time data from the pool of servers to decide which one is fastest. When a vServer starts, there’s no history yet, so the appliance uses Round Robin by default to distribute the initial requests evenly until it can collect enough latency measurements. Once traffic begins, it records each server’s response times and then starts directing requests to the servers with the lowest latency, moving away from pure Round Robin. The other factors listed don’t cause this initial Round Robin behavior: a monitoring type like PING affects health checks, not the initial load-balancing decision, and the option of not having saved the configuration doesn’t create this startup behavior.