1Y0-241 · Question #108
A Citrix Administrator needs to configure a rate-limiting policy setting DNS requests to a threshold of 1,000 per second. Which set of commands does the administrator need to run to correctly…
The correct answer is B. > add stream selector DNSSelector1 client.udp.dns.domain > add ns limitIdentifier. See the full explanation below for the reasoning.
Question
A Citrix Administrator needs to configure a rate-limiting policy setting DNS requests to a threshold of 1,000 per second. Which set of commands does the administrator need to run to correctly configure and enable this policy?
Options
- A
add stream selector DNSSelector1 client.udp.dns.domain > add ns limitIdentifier
- B
add stream selector DNSSelector1 client.udp.dns.domain > add ns limitIdentifier
- C
add stream selector DNSSelector1 client.udp.dns.domain > add ns limitIdentifier
- D
add stream selector DNSSelector1 client.udp.dns.domain > add ns limitIdentifier
How the community answered
(28 responses)- A14% (4)
- B75% (21)
- C7% (2)
- D4% (1)
Community Discussion
5
Viktor S.Jun 10, 2026Saw this exact setup on my exam, picked B because limitIdentifier needs the selector first.
Giselle K.May 2, 2026The DNS rate-limiting flow on NetScaler goes stream selector first, then limitIdentifier bound to that selector with your threshold, then the rate limit policy itself referencing the identifier, and finally binding that policy to the DNS vserver. Which part of that chain are you most unsure about, the limitIdentifier syntax or where exactly the policy gets bound?
Giovanna H.May 5, 2026Solid sequence, though I would flag for exam purposes that candidates often lose points by forgetting to set the limitIdentifier mode to SOURCEIPADDRESS explicitly, because the default mode assumption burns them on the CCP-V scenario questions even when the rest of the chain is perfect.
Toby R.May 31, 2026This one tripped me up at first because the options all looked almost identical on screen and I had to slow down and actually read the threshold and timeslice values in each command block to spot that B had the correct combination of 1000 for the limit and 1000 for the timeslice to get you that per-second rate. The stream selector targeting client.udp.dns.domain is the piece that locks this to DNS specifically, and once I remembered that the limitIdentifier ties it all together, B was the clear pick.
Giselle K.May 31, 2026The limitIdentifier piece is what a lot of people gloss over, but worth noting the stream selector alone would not save you if the identifier is scoped wrong, so reading those two together is really the discipline the question is testing.