Scenario: A Citrix Administrator needs to configure persistence on a global server load balancing (GSLB) vServer to which a service Is bound. Service must continue to handle requests from the client…

Question

Options

• APersistence threshold
• BPersistence time-Out
• CRequest threshold
• Dwait time

• A
  10% (3)
• B
  3% (1)
• C
  3% (1)
• D
  83% (25)

Explanation

Wait time (option D) is the parameter configured when manually disabling a GSLB service. It specifies a grace period during which the service continues honoring existing persistent sessions - accepting no new connections - before fully shutting down and closing all open connections. This enables a controlled, graceful drain of the service without abruptly dropping clients.

Why the distractors are wrong:

• A. Persistence threshold - Controls the minimum number of requests before persistence kicks in for a vServer; it has nothing to do with disabling behavior.
• B. Persistence time-out - Defines how long a persistence session remains valid (i.e., how long a client is "stuck" to a server); it governs session lifetime, not service shutdown.
• C. Request threshold - Not a standard GSLB disable parameter; it relates to load conditions, not graceful shutdown logic.

Memory tip: Think of wait time as a "last call" countdown - when you tell the service to close, it waits that configured duration to finish serving loyal (persistent) clients before locking the doors for good. If you associate Wait with Wind-down, you'll never confuse it with persistence timeout, which is about session life, not service death.

No community discussion yet for this question.