The answer is implementing retry logic with exponential backoff, which is a valid method to handle API rate limiting in Python because it systematically increases wait time between retries, preventing overwhelming the server while still allowing eventual success. This approach works hand-in-hand with parsing the Retry-After header, a standard HTTP mechanism defined in RFC 7231 that tells your script exactly how long to pause, making your automation dynamic rather than relying on arbitrary delays. On the Cisco DevNet Associate 200-901 exam, this concept tests your understanding of resilient API interaction patterns, often appearing in scenario-based questions where you must choose between fixed delays, queue-based throttling, or exponential backoff—with the trap being that simple sleep() calls lack the adaptive logic the exam expects. Remember the mnemonic “Backoff, Don’t Blast”: exponential backoff respects server limits, while fixed delays risk rate-limit errors.
200-901 Infrastructure and Automation Practice Question
This 200-901 practice question tests your understanding of infrastructure and automation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE of the following are valid methods to handle API rate limiting in a Python automation script? (Select exactly 3.)
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 from the response
Option A is correct because the Retry-After header is a standard HTTP mechanism (defined in RFC 7231) that explicitly tells the client how long to wait before making the next request. Parsing this header allows your Python script to respect the server's rate limit dynamically, rather than using a fixed or arbitrary delay. This is a common pattern when interacting with REST APIs that enforce rate limiting.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 from the response
Why this is correct
Respects server-specified wait time.
Related concept
Read the scenario before looking for a memorised answer.
✓
Use a token bucket algorithm to control request rate
Why this is correct
Token bucket limits request rate client-side.
Related concept
Read the scenario before looking for a memorised answer.
✗
Sleep for a fixed amount of time between requests
Why it's wrong here
Fixed sleep may not adapt to dynamic limits.
✗
Ignore the limit and send requests faster
Why it's wrong here
Will cause more blocks.
✓
Implement retry logic with exponential backoff
Why this is correct
Standard approach to handle rate limits.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between a fixed sleep (which is naive and not adaptive) versus dynamic methods like parsing Retry-After or using exponential backoff, and candidates mistakenly think a static delay is sufficient for rate limiting.
Detailed technical explanation
How to think about this question
The token bucket algorithm (Option B) controls request rate by maintaining a bucket of tokens that refill at a steady rate; each request consumes a token, and if the bucket is empty, the request is delayed or dropped. This is often implemented client-side using libraries like `pyrate-limiter` or `ratelimit` in Python. Retry logic with exponential backoff (Option E) is a robust approach where the script waits an increasing amount of time (e.g., 1s, 2s, 4s, 8s) after each failure, often combined with jitter to avoid thundering herd problems, and is recommended by major API providers like GitHub and Stripe.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Infrastructure and Automation — This question tests Infrastructure and Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Parse the Retry-After header from the response — Option A is correct because the Retry-After header is a standard HTTP mechanism (defined in RFC 7231) that explicitly tells the client how long to wait before making the next request. Parsing this header allows your Python script to respect the server's rate limit dynamically, rather than using a fixed or arbitrary delay. This is a common pattern when interacting with REST APIs that enforce rate limiting.
What should I do if I get this 200-901 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.