1Y0-231 · Question #160
A Citrix Administrator needs to configure a rate-limiting policy setting DNS requests to a threshold of 1,000 per second. Which command does the administrator need to run to correctly configure this…
The correct answer is A. SYS.CHECK.LIMIT(<limit_identifier>). SYS.CHECK.LIMIT(<limit_identifier>) is correct because DNS operates at the network/system level, not the HTTP application layer - making SYS.CHECK.LIMIT the appropriate Citrix ADC policy expression to enforce a rate threshold against DNS traffic using a pre-configured limit…
Question
A Citrix Administrator needs to configure a rate-limiting policy setting DNS requests to a threshold of 1,000 per second. Which command does the administrator need to run to correctly configure this policy?
Options
- ASYS.CHECK.LIMIT(<limit_identifier>)
- BSYS.CHECK.LIMIT(<limit_identifier>) || HTTP.REQ.LIMIT(<limit_identifier>)
- CHTTP.REQ.LIMIT(<limit_identifier>)
- DSYS.CHECK.LIMIT(<limit_identifier>) || CONNECTION.IP.LIMIT(<limit_identifier>)
How the community answered
(32 responses)- A78% (25)
- B3% (1)
- C6% (2)
- D13% (4)
Explanation
SYS.CHECK.LIMIT(<limit_identifier>) is correct because DNS operates at the network/system level, not the HTTP application layer - making SYS.CHECK.LIMIT the appropriate Citrix ADC policy expression to enforce a rate threshold against DNS traffic using a pre-configured limit identifier. Option C (HTTP.REQ.LIMIT) is wrong because it applies only to HTTP requests, and DNS is not an HTTP protocol. Options B and D are wrong because they combine expressions with a logical OR (||), which would bypass the limit if either condition evaluates to true - defeating the purpose of rate limiting - and CONNECTION.IP.LIMIT in option D is not a valid Citrix ADC policy expression. Memory tip: Associate SYS with system-level protocols like DNS and TCP, and HTTP.REQ strictly with web traffic - if the protocol isn't HTTP, reach for SYS.CHECK.LIMIT.
Topics
Community Discussion
No community discussion yet for this question.