What could cause an HTTP vServer configured with Least Response Time to appear to use Round Robin?

• A. The services bound to the HTTP vServer use a PING monitor.
• B. The vServer is in startup round robin mode.
• C. Least Response Time cannot be used on an HTTP vServer.
• D. The ADC configuration has NOT been saved yet.

Answer: (B)

Least Response Time relies on real-time latency data from monitors to pick the fastest available server. If the vServer is in startup round robin mode, there isn’t yet enough monitoring data to compute reliable response times, so the system temporarily distributes requests evenly across bound services using Round Robin. Once monitors are active and enough latency data is collected, the policy switches to Least Response Time, and future requests go to the server with the lowest response time. This startup behavior is what makes it appear as though Round Robin is being used even though the vServer is configured for Least Response Time.