The answer is to introduce a delay between API calls to fix the Meraki API rate limiting issue. This is correct because the HTTP 429 errors indicate the script is exceeding the per-key rate limit, even though it runs sequentially; the Meraki API enforces a maximum number of requests per second per API key, and without a pause, the script’s rapid-fire calls to the /devices/{serial}/uplink and /wireless/status endpoints for 250 devices can momentarily spike above that threshold. On the Cisco DevNet Associate 200-901 exam, this scenario tests your understanding of API rate limiting as a common REST API constraint—a frequent trap is assuming concurrency or multiple keys are needed, when a simple time.sleep() delay is the minimal-change fix. Remember the mnemonic: “429 means slow your pace, not change your face.”
200-901 Understanding and Using APIs Practice Question
This 200-901 practice question tests your understanding of understanding and using apis. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A DevOps team manages a multi-site Cisco Meraki network with 50 MX appliances and 200 MR access points. They use a Python script that calls the Meraki API to collect device utilization data every hour and stores it in a CSV file. Recently, the script started failing intermittently with HTTP 429 status codes. The team suspects rate limiting but notices that the failures occur even when only one script instance runs. The script uses a single API key and makes requests to the /devices/{serial}/uplink endpoint for each MX and the /devices/{serial}/wireless/status endpoint for each MR. The script is scheduled via cron and runs sequentially. The team wants to resolve the rate limiting while minimizing changes to the script. Which course of action should the team take?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Introduce a delay between API calls to stay within the rate limit.
The intermittent HTTP 429 errors indicate the script is exceeding the Meraki API rate limit, which applies per API key. Since the script runs sequentially with a single key, introducing a delay between API calls (e.g., using time.sleep()) is the simplest fix that stays within the rate limit without requiring architectural changes. This directly addresses the root cause while minimizing modifications to the existing script.
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.
✓
Introduce a delay between API calls to stay within the rate limit.
Why this is correct
Adding a small delay reduces request rate and avoids 429 errors.
Related concept
Read the scenario before looking for a memorised answer.
✗
Distribute the API requests across multiple API keys.
Why it's wrong here
The issue is rate limiting per key, but adding delays is simpler.
✗
Switch to a webhook-based approach to receive data instead of polling.
Why it's wrong here
Requires significant re-architecture and is not minimal.
✗
Use the bulk API request feature to collect data in fewer calls.
Why it's wrong here
Meraki does not have a bulk endpoint for these data.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that rate limiting can be solved by distributing requests across multiple keys, but the trap here is that the rate limit applies per key and the script's sequential nature means a single key is sufficient if delays are added.
Detailed technical explanation
How to think about this question
The Meraki API rate limit is typically 5 requests per second per API key, but it can vary by organization. When the script calls 250 endpoints (50 MX + 200 MR) sequentially without delay, it can easily exceed this limit, especially if network latency or processing time is low. Introducing a delay of 0.2–0.5 seconds between calls ensures compliance with the rate limit while keeping the total runtime under an hour, which is acceptable for hourly data collection.
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 practitioner preparing for the 200-901 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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.
Understanding and Using APIs — This question tests Understanding and Using APIs — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Introduce a delay between API calls to stay within the rate limit. — The intermittent HTTP 429 errors indicate the script is exceeding the Meraki API rate limit, which applies per API key. Since the script runs sequentially with a single key, introducing a delay between API calls (e.g., using time.sleep()) is the simplest fix that stays within the rate limit without requiring architectural changes. This directly addresses the root cause while minimizing modifications to the existing script.
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.