Scenario: A Citrix Administrator has configured an HTTP load-balancing virtual server with least response time as the load-balancing algorithm. The administrator notices that requests to the virtual…

Question

Options

• AThe virtual server is in startup round robin mode.
• BLeast response time CANNOT be used as a load-balancing algorithm on an HTTP virtual server.
• CThe services that are bound to the HTTP virtual server are using the PING monitor.
• DThe Citrix ADC configuration has NOT been saved yet.

• A
  77% (27)
• B
  6% (2)
• C
  11% (4)
• D
  6% (2)

Explanation

Option A is correct because Citrix ADC enters Startup Round Robin mode when services are newly brought online and there is insufficient response time data for the Least Response Time algorithm to function properly - since that algorithm needs real measured data to compare services, the ADC temporarily falls back to round robin until enough samples are collected.

Option B is wrong because Least Response Time is a fully supported load-balancing method for HTTP virtual servers on Citrix ADC; there is no protocol restriction preventing its use.

Option C is wrong because the monitor type (PING, HTTP, TCP, etc.) determines how the ADC checks service health, not which load-balancing algorithm is applied - a PING monitor has no influence on the LB method.

Option D is wrong because unsaved configuration still runs correctly in memory; the ADC operates on its running config, so not saving to disk doesn't change runtime behavior until a reboot.

Memory tip: Think of it as a "cold start" problem - Least Response Time is data-driven, so with no response time history yet, the ADC can't rank services and temporarily uses round robin as a neutral fallback. No data = round robin.

No community discussion yet for this question.