Implement Robust REST API Error Handling for Time Outs and Rate Limits 350-901 Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A Python application consumes a Cisco Intersight API that provides X-RateLimit-Limit: 600 and X-RateLimit-Remaining: 5 in the response headers. The application needs to make 10 more requests in the next minute. What should the application do?

   • AMake the 5 remaining requests immediately, then wait for the rate limit window to reset before making the remaining 5 requests.
   • BWait 60 seconds before making any requests to ensure the window resets.
   • CMake all 10 requests immediately, since the limit is 600 per window.
   • DIgnore the remaining count and rely on the server to return 429 responses for excess requests.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   A client sends a POST request to create a resource and receives a timeout error. The request may or may not have been processed by the server. Which approach is most appropriate?

   • ARetry with a different HTTP method
   • BDo not retry; treat it as a permanent failure
   • CQuery the server to check if the resource was created, then decide whether to retry
   • DRetry the POST request immediately
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   What is the primary purpose of client-side rate limiting based on response headers?

   • ATo increase the server's rate limit
   • BTo reduce the number of API calls the client makes
   • CTo avoid exceeding the API's allowed request rate
   • DTo improve the server's response time
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   An application makes concurrent requests to a Cisco Meraki API. The application receives a 429 response with 'Retry-After: 30' and X-RateLimit-Remaining: 0. The application has 10 threads, each making requests. What should the application do to handle this correctly?

   • AHave only the thread that received the 429 wait 30 seconds; other threads continue making requests.
   • BHave all threads wait 30 seconds, then resume making requests without checking the Remaining header.
   • CHave all threads stop making requests, wait 30 seconds, then resume, but also check X-RateLimit-Remaining before each request.
   • DIgnore the 429 and have all threads retry immediately with a 1-second delay.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   Which HTTP method is generally considered safe to retry automatically after a timeout because it is idempotent?

   • ADELETE
   • BPATCH
   • CPOST
   • DGET
   Reveal Solution Discussion Select an answer first