A developer checks the performance of a web application. The application is in the local data center and used a REST-based API. Based on the API logs, it is discovered that many users abandon API…

The correct answer is C. Rate limiting is not implemented. When rate limiting is not implemented, the API server has no mechanism to control the number of incoming requests. Under high user load, the server becomes overwhelmed with concurrent requests, exhausting resources such as CPU, memory, and database connections. This causes…

Understanding and Using APIs

Question

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

Options

AToken-based authentication is disabled.
BPagination is not implemented.
CRate limiting is not implemented.
DToken-based authentication is enabled.

How the community answered

(24 responses)

A
17% (4)
B
4% (1)
C
75% (18)
D
4% (1)

Explanation

When rate limiting is not implemented, the API server has no mechanism to control the number of incoming requests. Under high user load, the server becomes overwhelmed with concurrent requests, exhausting resources such as CPU, memory, and database connections. This causes response times to degrade significantly, leading users to abandon requests before receiving a response. Rate limiting protects the server by capping how many requests a client (or all clients collectively) can make in a given timeframe. Pagination (B) addresses large response payloads but does not prevent server overload from excessive concurrent requests. Authentication settings (A, D) control access but do not govern request throughput.

Topics

#API Performance#Rate Limiting#REST API#API Design

Community Discussion

No community discussion yet for this question.

Full 200-901 Practice