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 6 Question 78 Discussion

Actual exam question for Cisco's 200-901 exam
Question #: 78
Topic #: 6
[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:

Precious
5 months ago
B) rate limiting, for sure. It's the API security equivalent of a bouncers at a club - only letting in a certain number of people at a time.
upvoted 0 times
Dorothy
3 months ago
B) rate limiting, for sure. It's the API security equivalent of a bouncer at a club - only letting in a certain number of people at a time.
upvoted 0 times
...
Elouise
3 months ago
D) payload limiting
upvoted 0 times
...
Edna
4 months ago
C) filtering
upvoted 0 times
...
Meaghan
4 months ago
B) rate limiting
upvoted 0 times
...
Earleen
4 months ago
A) pagination
upvoted 0 times
...
Roosevelt
4 months ago
D) payload limiting might also be necessary to restrict the size of data that can be sent in each API request.
upvoted 0 times
...
Edison
4 months ago
A) pagination could also be helpful in breaking up large sets of data into smaller, more manageable chunks.
upvoted 0 times
...
Justine
4 months ago
B) rate limiting is definitely the way to go. It will help prevent the application from being overloaded with too many API requests.
upvoted 0 times
...
...
Kirk
5 months ago
I think rate limiting makes sense. It will help prevent future attacks and ensure the application runs smoothly.
upvoted 0 times
...
Ezekiel
5 months ago
Hmm, I'd have to say B) rate limiting. It's the most straightforward approach to address the security issues mentioned in the question.
upvoted 0 times
...
Laurel
5 months ago
I believe rate limiting is the best option too. It will help control the number of requests being made to the API.
upvoted 0 times
...
Fallon
5 months ago
I'm leaning towards B) rate limiting. It's a proven technique for managing API traffic and preventing abuse.
upvoted 0 times
...
Eleonora
5 months ago
B) rate limiting is the way to go. It's a classic solution for API security, and it should do the trick in this case.
upvoted 0 times
Johnetta
4 months ago
D: Rate limiting it is then, let's implement it to address the security issues.
upvoted 0 times
...
Jeannetta
4 months ago
A) pagination wouldn't really solve the security issue. Rate limiting is a more effective way to protect the application from attacks.
upvoted 0 times
...
Jordan
4 months ago
C: It's a good choice, it will help prevent the application from being overloaded with API requests.
upvoted 0 times
...
Yvette
4 months ago
B: Agreed, rate limiting is a classic solution for API security.
upvoted 0 times
...
Billy
4 months ago
B) rate limiting is definitely the best choice here. It will help prevent the application from being overloaded with too many API requests.
upvoted 0 times
...
Lashaunda
5 months ago
A: I think we should go with rate limiting to protect the application from future attacks.
upvoted 0 times
...
...
Justine
5 months ago
I agree with Elenor. Rate limiting will help prevent the application from being overloaded with API requests.
upvoted 0 times
...
Elenor
5 months ago
I think the developer should implement rate limiting to protect the application.
upvoted 0 times
...
Johnna
6 months ago
I'd go with D) payload limiting. Restricting the size of the request payload can help mitigate against resource-intensive attacks.
upvoted 0 times
Alisha
5 months ago
I think B) rate limiting would also be effective in preventing the application from being overloaded with API requests.
upvoted 0 times
...
Alisha
5 months ago
I agree, D) payload limiting is a good choice to prevent resource-intensive attacks.
upvoted 0 times
...
...
Dahlia
6 months ago
Definitely B) rate limiting. It's the best way to prevent API overload and protect the application from sudden spikes in traffic.
upvoted 0 times
Paola
5 months ago
Implementing rate limiting will definitely help in preventing future attacks on the application.
upvoted 0 times
...
Felicidad
5 months ago
Rate limiting can help prevent sudden spikes in traffic and keep the application running smoothly.
upvoted 0 times
...
Rikki
5 months ago
I agree, B) rate limiting is crucial for protecting the application from overload.
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