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 5 Question 108 Discussion

A developer checks the performance of a web application. The application is in the local data center and uses a REST-based API. Based on the API logs, it is discovered that many its abandon API requests. Also, the response is taking too long to get back. What is the reason for this issue?
C) Rate limiting is not implemented.
A) Pagination is not implemented
D) Token-based authentication is disabled
B) Token-based authentication is enabled.

Cisco 200-901 Exam - Topic 5 Question 108 Discussion

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

A developer checks the performance of a web application. The application is in the local data center and uses a REST-based API. Based on the API logs, it is discovered that many its abandon API requests. Also, the response is taking too long to get back. What is the reason for this issue?

Show Suggested Answer Hide Answer
Suggested Answer: C

Rate limiting is a technique to control the rate of incoming and outgoing traffic to or from a network. If rate limiting is not implemented, excessive API requests can overwhelm the server, causing long response times and abandoned requests.

Abandoned Requests: When a server is overwhelmed with too many requests, it may not process them all, leading to abandoned requests.

Long Response Times: Without rate limiting, the server might be handling more requests than it can efficiently process, resulting in delayed responses.

Solution: Implementing rate limiting ensures that the server processes requests at a manageable rate, improving performance and reliability.


Rate Limiting and API Performance: Understanding Rate Limiting

by Laquanda at Jan 22, 2026, 05:41 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
Kate
2 months ago
I think it's the API design. Needs optimization for speed.
upvoted 0 times
...
Deonna
2 months ago
Abandon requests might indicate client-side problems.
upvoted 0 times
...
Cora
2 months ago
Could be server overload too. Too many requests at once.
upvoted 0 times
...
Ilene
2 months ago
Sounds like a network issue. Latency could be high.
upvoted 0 times
...
Juliann
4 months ago
Nah, I think it's just user error.
upvoted 0 times
...
Ria
4 months ago
Could be a problem with the API design.
upvoted 0 times
...
Luisa
4 months ago
Abandon requests? That's surprising!
upvoted 0 times
...
Azalee
4 months ago
I bet the server is overloaded.
upvoted 0 times
...
Lorrine
5 months ago
Sounds like a network latency issue.
upvoted 0 times
...
Rozella
5 months ago
I bet the developer forgot to enable caching on the API responses.
upvoted 0 times
...
Albert
5 months ago
Haha, the developer should have tested the API performance before going live!
upvoted 0 times
...
Jeannetta
5 months ago
Maybe the API is not optimized for performance or is making too many database calls.
upvoted 0 times
...
Julieta
5 months ago
Looks like a problem with the API implementation or the server-side processing.
upvoted 0 times
...
Jannette
5 months ago
The issue could be due to network latency between the client and the server.
upvoted 0 times
...
Erinn
6 months ago
It might also be a problem with the API design itself. I recall a case study where inefficient endpoints led to similar issues.
upvoted 0 times
...
Bea
6 months ago
I'm not entirely sure, but could it be related to server overload? I feel like we discussed server capacity in one of our sessions.
upvoted 0 times
...
Dell
7 months ago
Abandoned API requests could indicate that clients are timing out. I think we covered that in a practice question about API performance.
upvoted 0 times
...
Han
7 months ago
I remember studying about network latency issues that can cause slow response times. Maybe that's what's happening here?
upvoted 0 times
...
Isreal
7 months ago
This sounds like a performance issue, but I'm not sure if the problem is with the API or the web application. I'd start by profiling the application to see where the bottlenecks are.
upvoted 0 times
...
Mitsue
7 months ago
I've seen issues like this before. My first step would be to check the API response times and see if there are any spikes or inconsistencies. That could give me a clue as to where the problem is.
upvoted 0 times
...
Moira
7 months ago
Okay, let's think this through. If the API is taking too long to respond, it could be a bottleneck in the system. Maybe the API is overloaded or there's a problem with the network connection.
upvoted 0 times
...
Felice
7 months ago
I'm a bit confused by this question. Is the issue with the API itself or the web application? I'd need to gather more information before I can make a guess.
upvoted 0 times
...
Leatha
8 months ago
Hmm, this seems like a tricky one. I'd start by looking at the API logs to see if there are any patterns or common issues with the abandoned requests.
upvoted 0 times
Cheryl
1 month ago
Definitely check for error responses in the logs.
upvoted 0 times
...
Sharee
1 month ago
Or maybe the server is overloaded?
upvoted 0 times
...
Apolonia
2 months ago
Could be network latency issues.
upvoted 0 times
...
...

Save Cancel