mediumMultiple Choice
350-401 Practice Question: Is using the Cisco Meraki Dashboard API to…
A network engineer is using the Cisco Meraki Dashboard API to automate the creation of VLANs across multiple networks. The engineer writes a Python script that uses the 'createNetworkVlan' endpoint. The script runs successfully for the first few networks, but then starts returning HTTP 429 errors. The engineer checks the API documentation and finds that the Meraki API has rate limits. The script currently sends requests as fast as possible. What should the engineer implement to avoid hitting the rate limit?
⚠ Common exam trap
Cisco often tests the misconception that rate limits can be bypassed by changing request headers or using a different API version, when the correct solution is always to implement proper retry logic with backoff.
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
✓
Add a retry mechanism with exponential backoff when a 429 response is received.
HTTP 429 errors indicate rate limiting, and the standard mitigation is to implement a retry mechanism with exponential backoff. This approach respects the API's rate limits by pausing and retrying after increasing delays, allowing the script to eventually succeed without overwhelming the server. The Meraki Dashboard API documentation explicitly recommends exponential backoff for handling 429 responses.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reduce the number of networks being processed in a single script run.
Why it's wrong here
Reducing the number of networks processed per run only lessens the total request count but does not affect the per-second request rate against the API key. If the script still sends requests in a tight loop, it will exhaust the same rate limit; plus all networks must eventually be processed, so this "defer" approach just postpones the 429s and delays automation completion.
- ✗
Increase the 'per-second' rate limit by setting a higher value in the API request header.
Why it's wrong here
The per-second rate limit is enforced by Meraki's servers based on your API key and can't be overridden by any client-supplied header. HTTP request headers are for describing the client's intent or authentication, not for unilaterally raising server-side quotas, and attempting to send a higher limit would be ignored or rejected. You must instead handle the server's 429 responses within the client code.
- ✓
Add a retry mechanism with exponential backoff when a 429 response is received.
Why this is correct
A 429 Too Many Requests response signals that the client has hit a server-enforced rate limit, and the standard remedy is to wait and retry. Exponential backoff increases the delay between each retry (e.g., 1s, 2s, 4s) to avoid hammering the API, and it aligns with the server's expectation that the client will back off; optionally, you can combine it with the Retry-After header if provided. This is the widely recommended pattern for resilient API clients.
- ✗
Switch to using the Meraki API version 1.0 which has no rate limits.
Why it's wrong here
Every version of the Meraki API—including v1.0—applies the same rate limiting rules to protect the platform from abuse; there is no "unlimited" version. Even if a version did not have rate limits in its own spec, the platform-level policy still governs usage, so switching versions would not let you bypass it. The only correct fix is to handle rate limits in your automation code.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every 350-401 question from scratch — 1,923 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 350-401 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 350-401 exam.