Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 200-901 Topic 9 Question 71 Discussion

Actual exam question for Cisco's 200-901 exam
Question #: 71
Topic #: 9
[All 200-901 Questions]

A developer has experienced security issues with a previously developed application. The API offered by that application is open and without any constraints. During a recent attack, the application was overloaded with API requests. To address this issue, an API constraint is implemented to protect the application from future attacks or any sudden throttling. Which API constraint must the application developer implement in this situation?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Billy
6 months ago
Pagination is more about splitting large datasets, I believe rate limiting is more suitable for preventing overload attacks.
upvoted 0 times
...
Brandon
6 months ago
But what about pagination? Wouldn't that also help in managing the API requests?
upvoted 0 times
...
Dean
6 months ago
I agree with Billy. Rate limiting would help prevent overloading the application with API requests.
upvoted 0 times
...
Billy
6 months ago
I think the developer should implement rate limiting to address the security issue.
upvoted 0 times
...
Stevie
7 months ago
I'm not sure about rate limiting, maybe pagination could also help in controlling the requests.
upvoted 0 times
...
Argelia
7 months ago
I believe rate limiting is the best choice because it will prevent the application from being overloaded.
upvoted 0 times
...
Arminda
7 months ago
I agree with Dean, rate limiting will help control the number of API requests.
upvoted 0 times
...
Dean
7 months ago
I think the developer should implement rate limiting to prevent future attacks.
upvoted 0 times
...
Leslie
8 months ago
That's a good point, Stephaine. Payload limiting could definitely help in this situation. But I think rate limiting is still the primary concern. We need to control the number of requests coming in, regardless of their size.
upvoted 0 times
...
Stephaine
8 months ago
But wait, what about payload limiting? If the API requests are large in size, that could also contribute to the overload. Maybe we should consider limiting the size of the payloads as well.
upvoted 0 times
...
Nu
8 months ago
I agree with Misty. Rate limiting is the way to go. We can set a maximum number of requests per second or minute to prevent the application from being overwhelmed.
upvoted 0 times
Maybelle
8 months ago
User C
upvoted 0 times
...
Lindsey
8 months ago
User B
upvoted 0 times
...
Allene
8 months ago
User A
upvoted 0 times
...
...
Misty
8 months ago
Hmm, this is a tricky one. The application was overloaded with API requests, so we need a way to limit the number of requests that can be made. I think rate limiting is the best option here.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77