To maintain client persistence on a GSLB vServer after manual disable of a service, which parameter controls the time to wait before stopping new requests?

To maintain client persistence on a GSLB vServer after manual disable of a service, which parameter controls the time to wait before stopping new requests?

• A. Persistence threshold
• B. Persistence time-Out
• C. Wait time
• D. Request threshold

Answer: (B)

The concept here is how long a GSLB vServer should honor a client’s persistence mapping after a service is disabled. The persistence time-out sets the grace period during which new requests can still be directed to the previously used service, so existing sessions stay sticky even after you disable a backend. This timer keeps routing until it expires, then new requests are no longer sent to that disabled service and can be redirected to other healthy ones. Other options refer to different thresholds or generic wait notions that don’t control this grace period for persistence.

The concept here is how long a GSLB vServer should honor a client’s persistence mapping after a service is disabled. The persistence time-out sets the grace period during which new requests can still be directed to the previously used service, so existing sessions stay sticky even after you disable a backend. This timer keeps routing until it expires, then new requests are no longer sent to that disabled service and can be redirected to other healthy ones. Other options refer to different thresholds or generic wait notions that don’t control this grace period for persistence.