350-201 Question 257
Single answerYou are configuring a custom integration with Cisco SecureX using its REST API to automate a security workflow. During testing, your automation script fails intermittently when making requests to the API. Upon investigation, you notice that the failures occur when the API is called in rapid succession. What could be the cause of this issue?
- A
The API has a rate limit that restricts the number of requests within a given time period.
- B
The API payload size exceeds the maximum allowed limit.
- C
The API is returning a timeout error due to server-side processing delays.
- D
The API requires additional authentication headers for each request.
Show answer and explanation
Correct answer: A
Explanation
APIs often enforce rate limits to control usage and protect system resources. Exceeding these limits in rapid succession can result in errors, such as HTTP 429. To address this, developers should implement rate-limiting mechanisms, such as retry logic or request throttling, in their scripts. This is a common constraint when consuming APIs like those provided by Cisco SecureX.
- A. Correct.
Correct. Many APIs, including Cisco SecureX APIs, enforce rate limits to prevent excessive usage. If requests exceed the allowed rate, the API may reject them or return errors such as HTTP 429 (Too Many Requests).
- B. Incorrect.
Incorrect. While payload size limitations might cause request failures, this particular issue is unrelated to payload size as it occurs due to rapid request rates.
- C. Incorrect.
Incorrect. Timeout errors indicate delays or resource constraints on the server but are not typically related to rapid successive requests as described in the scenario.
- D. Incorrect.
Incorrect. Authentication issues would consistently cause request failures rather than intermittent failures triggered by the rate of requests.