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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Cisco 200-901 Exam - Topic 9 Question 71 Discussion

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?
B) rate limiting
A) pagination
C) filtering
D) payload limiting

Cisco 200-901 Exam - 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

by Minna at Mar 15, 2024, 07:35 PM

Limited Time Offer

25%

Off

Get Premium 200-901 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Aileen
9 months ago
Really? I thought payload limiting was the main fix for overloads.
upvoted 0 times
...
Gary
9 months ago
Rate limiting is the best choice here, no doubt!
upvoted 0 times
...
Lashunda
10 months ago
Wait, isn't filtering also important for security?
upvoted 0 times
...
Ciara
10 months ago
I think pagination could help too, but not for this issue.
upvoted 0 times
...
Geoffrey
10 months ago
Definitely rate limiting! That's the way to go.
upvoted 0 times
...
Olene
10 months ago
I practiced a similar question where rate limiting was the answer for API security. I think that’s what we need here too.
upvoted 0 times
...
Shawnda
11 months ago
Filtering could help, but I feel like it’s not the main solution for this specific issue. Rate limiting sounds more appropriate.
upvoted 0 times
...
Kirk
11 months ago
I’m not entirely sure, but I think pagination is more about managing data responses rather than protecting against attacks.
upvoted 0 times
...
Deandrea
11 months ago
I remember studying about rate limiting in our security module. It seems like the right choice to prevent overloads.
upvoted 0 times
...
Stacey
11 months ago
I'm a bit confused on this one. Payload limiting could also be an option to prevent the API from being overwhelmed, but I'm not sure if that's the best fit for this scenario. I'll have to think it through a bit more.
upvoted 0 times
...
Valentin
11 months ago
I'm pretty confident that the answer is rate limiting. That's the most common way to prevent API abuse and protect against sudden spikes in traffic. Pagination or filtering wouldn't really address the issue of overloading the API.
upvoted 0 times
...
Clorinda
11 months ago
Okay, so the key here is that the application was overloaded with API requests during a recent attack. That tells me we need to implement some kind of constraint to protect the API from being abused. I'm leaning towards rate limiting as the best option.
upvoted 0 times
...
Eveline
11 months ago
Hmm, I'm a bit unsure about this one. I know rate limiting is used to control API access, but I'm not sure if that's the best solution here. Let me think this through a bit more.
upvoted 0 times
...
Doug
11 months ago
This one seems pretty straightforward. I think the answer is rate limiting to prevent the API from being overloaded with requests.
upvoted 0 times
...
Alpha
11 months ago
Hmm, I'm a bit confused by this question. I'm not entirely sure what "bank-assisted controls" are referring to. I'll need to think this through carefully.
upvoted 0 times
...
Tamekia
11 months ago
Hmm, the diagram shows routers R1, R2, R4, and R5, so I'm guessing the answer has to do with the routing protocol used between those routers. Let me think this through.
upvoted 0 times
...
Vernice
11 months ago
Ah, this is a classic networking question. I've got this - the key is knowing the valid multicast address ranges for IPv6.
upvoted 0 times
...
Lawana
11 months ago
This seems like a tricky question. I'm not sure if increasing the batch size or the number of enqueued batches is the right approach, as that could lead to higher latency. Maybe I should look into the CPU-specific optimizations for TensorFlow Serving.
upvoted 0 times
...
Nickie
11 months ago
Ah, I remember learning about Cisco Meraki's Auto VPN feature. That sounds like the right answer here.
upvoted 0 times
...
Alisha
11 months ago
Okay, I've got this. The key is to identify the two configuration parameters that are required for Native Call Queuing. I'll go through the options systematically.
upvoted 0 times
...
Billy
2 years ago
Pagination is more about splitting large datasets, I believe rate limiting is more suitable for preventing overload attacks.
upvoted 0 times
...
Brandon
2 years ago
But what about pagination? Wouldn't that also help in managing the API requests?
upvoted 0 times
...
Dean
2 years ago
I agree with Billy. Rate limiting would help prevent overloading the application with API requests.
upvoted 0 times
...
Billy
2 years ago
I think the developer should implement rate limiting to address the security issue.
upvoted 0 times
...
Stevie
2 years ago
I'm not sure about rate limiting, maybe pagination could also help in controlling the requests.
upvoted 0 times
...
Argelia
2 years ago
I believe rate limiting is the best choice because it will prevent the application from being overloaded.
upvoted 0 times
...
Arminda
2 years ago
I agree with Dean, rate limiting will help control the number of API requests.
upvoted 0 times
...
Dean
2 years ago
I think the developer should implement rate limiting to prevent future attacks.
upvoted 0 times
...
Leslie
2 years 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
2 years 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
2 years 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
2 years ago
User C
upvoted 0 times
...
Lindsey
2 years ago
User B
upvoted 0 times
...
Allene
2 years ago
User A
upvoted 0 times
...
...
Misty
2 years 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