1Y0-A28 · Question #125
A network engineer needs to prevent too many simultaneous HTTP requests that can cause a Denial Of Service (DDoS). What could the engineer enable to prevent too many simultaneous HTTP requests?
The correct answer is A. Rate Limiting. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test…
Question
A network engineer needs to prevent too many simultaneous HTTP requests that can cause a Denial Of Service (DDoS). What could the engineer enable to prevent too many simultaneous HTTP requests?
Options
- ARate Limiting
- BSureConnect
- CPriority Queuing
- DAuthorization Policy
How the community answered
(58 responses)- A72% (42)
- B16% (9)
- C3% (2)
- D9% (5)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
5
Yusuf A.Dec 20, 2025Rate Limiting is the right call here. It lets you cap how many HTTP requests hit a service in a given timeframe, so a flood of connections gets throttled before it can overwhelm your server, which is exactly what you need to stop a DoS scenario like this.
Orla P.Dec 3, 2025Rate Limiting is right, it throttles concurrent HTTP connections per client.
Jovan I.Dec 16, 2025Rate Limiting is correct, it throttles concurrent HTTP connections per client or vServer.
Hiroshi T.Dec 19, 2025Rate limiting governs the rate of new connections or requests over time, not concurrent connections; concurrent connection throttling is a separate control typically called a connection limit or connection rate limit in the vendor documentation, so conflating the two will cost you points on the exam.
Hiroshi T.Dec 14, 2025Rate Limiting is what the blueprint points to here, and the official Citrix documentation on NetScaler (now Citrix ADC) covers this under the "Protect Against Denial of Service Attacks" section, where it explicitly describes rate limiting as the mechanism for capping the number of simultaneous or per-interval HTTP requests from a client. SureConnect is a queuing feature that manages how users experience wait times when a server is overloaded, not a tool for capping request volume at the ingress point. Priority Queuing similarly handles request ordering under load rather than hard-limiting how many get through. Authorization Policy is an access control construct and has no role in connection-rate enforcement. One thing worth locking down before exam day: do you understand the difference between limiting concurrent connections versus limiting requests per second, and does the Citrix documentation treat those as the same Rate Limiting control or separate ones? Getting that distinction clear will help you eliminate wrong options faster on any question that touches this topic.