hardMultiple Choice
200-901 Practice Question: A Python script using the Cisco Meraki API v1 is…
A Python script using the Cisco Meraki API v1 is failing with a 429 status code. What is the recommended course of action?
⚠ Common exam trap
Cisco often tests the distinction between HTTP status codes, so the trap here is that candidates confuse a 429 (rate limit) with authentication errors (401/403) or assume they can modify server-side limits, leading them to pick options like B or C.
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
✓
Implement retry logic with exponential backoff and respect Retry-After header
A 429 status code indicates rate limiting, meaning the client has exceeded the allowed number of requests per time window. The correct response is to implement retry logic with exponential backoff and respect the Retry-After header, which tells the client how long to wait before retrying. This is a standard best practice for REST APIs, including Cisco Meraki's API v1, to handle rate limits gracefully without overwhelming the server.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the API endpoint to a different region
Why it's wrong here
A 429 signals rate limiting, so switching regions leaves the request volume against the same organisation's limits unchanged. Regional endpoints exist for data residency and latency, and would be the right answer if the script targeted the wrong geographic cluster. Retrying with exponential backoff and honouring the Retry-After header addresses the actual cause.
- ✗
Check the API token
Why it's wrong here
A 429 signals rate limiting, not authentication, so the token is irrelevant here; the script must back off and retry after the Retry-After interval. Checking the token is tempting because invalid or expired credentials commonly cause failures, and that check would be right for a 401 response instead.
- ✗
Increase the rate limit on the dashboard
Why it's wrong here
Meraki rate limits are fixed per organisation and cannot be raised from the dashboard, so this action is impossible. The 429 signals the script exceeded the API's call quota, requiring retry with backoff. Dashboard settings do control per-SSID bandwidth limits and traffic shaping, which is a different feature entirely.
- ✓
Implement retry logic with exponential backoff and respect Retry-After header
Why this is correct
A 429 signals rate limiting, so the script must throttle itself rather than retry immediately. Exponential backoff spaces retries progressively, and honouring the Retry-After header respects the server's stated wait window, satisfying the API's rate-limit constraint without triggering further 429s.
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.