Deal of The Day! 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 4 Question 80 Discussion

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

Lucy
2 months ago
Forget all that technical stuff, I'm just glad the dLucyloper didn't try to solve this by unplugging the server. That's what my grandpa would've done!
upvoted 0 times
...
Tabetha
2 months ago
I see your point, Joseph, but rate limiting is more effective in preventing sudden throttling and attacks on the application.
upvoted 0 times
...
Amalia
2 months ago
Rate limiting all the way! Anything to prevent another API meltdown, am I right? Developers need their beauty sleep, you know.
upvoted 0 times
Art
27 days ago
Agreed! It's a necessary measure to prevent future attacks and ensure the application runs smoothly.
upvoted 0 times
...
Brande
1 months ago
Definitely! Rate limiting is crucial for protecting the application from overload.
upvoted 0 times
...
Lonny
1 months ago
B) rate limiting
upvoted 0 times
...
...
Joseph
2 months ago
I believe pagination could also be a good option to implement in this situation.
upvoted 0 times
...
Page
2 months ago
I agree with Laquita. Rate limiting can help prevent the application from being overloaded with API requests.
upvoted 0 times
...
Laquita
2 months ago
I think the developer should implement rate limiting to protect the application.
upvoted 0 times
...
Val
2 months ago
Filtering could also work, but rate limiting seems more straightforward and effective for this situation. Gotta keep those pesky API requests in check.
upvoted 0 times
Veronika
29 days ago
D) payload limiting
upvoted 0 times
...
Alonso
1 months ago
I agree, rate limiting is the best option to prevent overload from API requests.
upvoted 0 times
...
Micah
1 months ago
B) rate limiting
upvoted 0 times
...
Temeka
2 months ago
D) payload limiting
upvoted 0 times
...
Mariann
2 months ago
I agree, rate limiting is the best option to prevent overload from API requests.
upvoted 0 times
...
Tasia
2 months ago
B) rate limiting
upvoted 0 times
...
...
Gussie
3 months ago
Hmm, I'd go with payload limiting. Restricting the size of the requests seems like a good way to keep things under control.
upvoted 0 times
Nicholle
2 months ago
I agree, rate limiting would definitely help in controlling the number of API requests and protecting the application from future attacks.
upvoted 0 times
...
Rutha
2 months ago
I think rate limiting would be more effective in this situation. It can help prevent the application from being overloaded with too many requests.
upvoted 0 times
...
...
Annett
3 months ago
Rate limiting sounds like the right choice here. Gotta put a cap on those API requests before the app gets swamped again!
upvoted 0 times
Heike
2 months ago
D: Let's implement rate limiting to avoid any future security issues.
upvoted 0 times
...
Pete
2 months ago
C: Rate limiting is definitely the way to go in this situation.
upvoted 0 times
...
Theodora
2 months ago
B: Agreed, that will help prevent the app from being overloaded with API requests.
upvoted 0 times
...
Judy
2 months ago
A: I think we should go with rate limiting to protect the application.
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