1Y0-A21 · Question #101
An administrator monitoring a NetScaler implementation configures a max client in the environment. Which information from the Dashboard will clearly indicate to the administrator that a service is…
The correct answer is D. Current requests in the surge queue. See the full explanation below for the reasoning.
Question
An administrator monitoring a NetScaler implementation configures a max client in the environment. Which information from the Dashboard will clearly indicate to the administrator that a service is definitely NOT able to handle the workload as configured? Citrix 1Y0-A21 Exam
Options
- ACurrent request rate
- BCurrent server connections
- CCurrent load on the service
- DCurrent requests in the surge queue
How the community answered
(53 responses)- A6% (3)
- B13% (7)
- C2% (1)
- D79% (42)
Community Discussion
8
Toby R.May 7, 2026D is your answer. When max client is configured, NetScaler limits how many concurrent connections a service can accept, and once that ceiling is hit, new requests get held in the surge queue instead of being forwarded. A non-zero and growing surge queue count on the Dashboard is the hard proof that the service cannot keep up, because requests are literally being queued rather than served. The other metrics like current load or server connections might be elevated, but they do not directly tell you the service is failing to absorb demand the way a populated surge queue does.
Giselle K.May 11, 2026Surge queue is the smoking gun, not load percentage, which only reflects capacity thresholds, D.
Mateus R.May 4, 2026I almost picked C, but surge queue filling up means the service literally ran out of room.
Toby R.May 6, 2026Yeah, and the key detail they love to test is that once the surge queue is full, new connection requests get dropped entirely, not queued further or redirected.
Ingrid P.May 10, 2026I kept looking at C, "Current load on the service," thinking that was the smoking gun since load is the most direct capacity signal, but then I remembered that load just tells you how busy the service is, not whether requests are actually piling up waiting to get in. D, the surge queue count, is the only metric that proves the service cannot keep up, because requests only land in the surge queue when max client connections are exhausted and new requests have nowhere to go.
Mateus R.May 12, 2026Right, think of load like the temperature gauge on your car engine, it tells you things are hot, but the surge queue is the steam coming out of the radiator, that is the hard proof the system has crossed from busy into actually overwhelmed.
Yusuf A.May 1, 2026I am going with A, current request rate, and here is why it makes sense to me. My senior showed me that the request rate tells you in real time how much demand is hitting a service, and if that number keeps climbing past what the service is configured to handle, that is the most direct signal that the workload has outpaced the setup. The other options like server connections or load on the service are more about the state of existing connections, not about the incoming pressure that is overwhelming the max client limit you just set. To me, watching the request rate is like watching water pour into a bucket, it shows you the problem is happening right now, not just that the bucket is already full. Has anyone else reasoned through it this way, or am I missing something obvious here?
Giselle K.May 2, 2026Yusuf, the request rate tells you how fast new requests are arriving, but it does not tell you how many concurrent connections are actually open against the service at a given moment, and a max client limit is a ceiling on concurrent connections, not on throughput rate, so D, current connections (or server connections depending on your exact question wording), is what you need to watch because that value is what actually bumps against the limit you configured.