200-901 Cisco Platforms and Development Practice Question
A developer is building a Python application that uses the Cisco Meraki Dashboard API to update VLAN settings on a network. The application must handle API errors gracefully and avoid being rate-limited. The developer wants to implement logic that inspects the response status code and the Retry-After header. Which two actions should the developer take when the API returns HTTP 429? (Choose two.)
⚠ Common exam trap
The trap here is assuming that rate limits are tied to the API key or that a custom retry header can bypass them, when Meraki enforces limits per organization and expects clients to honor Retry-After.
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
✓
Read the Retry-After response header and pause requests for the specified number of seconds before retrying.
Meraki's Dashboard API enforces rate limits and returns HTTP 429 with a Retry-After header when exceeded. The robust client reads that header, waits the indicated time, and then retries using exponential backoff with jitter to avoid synchronized retries. Rotating keys or switching protocols does not change the per-organization limit and can introduce security or reliability problems.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immediately resend the same request with an incremented X-Retry-Count header to bypass the rate limit.
Why it's wrong here
Meraki does not recognize an X-Retry-Count header for bypassing rate limits. Resending immediately without waiting will consume more of the rate-limit budget and likely return another 429. The correct approach is to wait based on Retry-After, not to invent a custom header.
- ✓
Read the Retry-After response header and pause requests for the specified number of seconds before retrying.
Why this is correct
Meraki's Dashboard API returns a Retry-After header on 429 responses that indicates how many seconds the client must wait. Honoring this header prevents further throttling and aligns with Meraki's documented rate-limit behavior. Simply pausing for a fixed interval without reading the header may retry too soon or waste time.
- ✓
Implement exponential backoff starting from the Retry-After value and add jitter to spread retries across concurrent clients.
Why this is correct
Exponential backoff with jitter is a standard resilience pattern for rate-limited APIs. Using the Retry-After value as the starting point respects the server's guidance, and jitter prevents synchronized retries from multiple instances. This reduces the chance of repeated 429 responses and stabilizes the application.
- ✗
Switch the request from HTTPS to HTTP to reduce overhead and avoid rate limiting.
Why it's wrong here
Meraki APIs require HTTPS; switching to HTTP is not supported and would expose credentials. Rate limiting is independent of the transport scheme and is enforced per organization and API key. This option does not address the 429 condition and introduces a security risk.
- ✗
Rotate to a different API key for the same organization to reset the rate-limit counter.
Why it's wrong here
Meraki rate limits are enforced per organization, not per API key. Creating or rotating keys within the same organization does not reset the limit and may violate best practices for key management. The correct response is to honor Retry-After and back off, not to bypass limits.
Visual reference
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.