200-901 Understanding and Using APIs Practice Question
A developer is writing a Python script to interact with a REST API that returns JSON. The script must handle rate limiting gracefully. The API returns a 429 status code with a Retry-After header when the limit is exceeded. Which approach should the developer take to ensure the script continues to function without being blocked?
⚠ Common exam trap
The trap here is thinking that any retry will eventually work, but without honoring the Retry-After header, the client may be permanently blocked or cause more severe throttling.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Parse the Retry-After header and sleep for the specified number of seconds before retrying.
Respecting the Retry-After header is the correct way to handle 429 responses. It tells the client exactly how long to wait before retrying, allowing the script to back off appropriately and avoid overwhelming the API. This approach ensures compliance with the API's rate limiting policy and maintains reliable operation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Parse the Retry-After header and sleep for the specified number of seconds before retrying.
Why this is correct
The Retry-After header indicates how long the client should wait before making another request. By sleeping for that duration, the script respects the server's rate limiting policy, avoids being blocked, and ensures that subsequent requests are likely to succeed without hitting the limit again.
- ✗
Switch to a different HTTP method to bypass the rate limit.
Why it's wrong here
Changing the HTTP method does not bypass rate limits, as rate limiting is typically applied per client or per endpoint regardless of method. This approach is ineffective and may violate API usage policies, leading to further restrictions or account suspension.
- ✗
Ignore the 429 response and continue with the next request.
Why it's wrong here
Ignoring the 429 response means the script will continue to send requests that are over the limit, potentially resulting in further errors, IP blocking, or degraded service. It does not address the rate limiting issue and can lead to data loss or incomplete operations.
- ✗
Immediately retry the request in a tight loop until it succeeds.
Why it's wrong here
Retrying immediately in a tight loop will likely exacerbate the rate limiting issue and may lead to the client being temporarily banned. It ignores the Retry-After header and can overload the server, causing further 429 responses and potential service disruption.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.