Cisco Platforms and Development →mediumMultiple ChoiceObjective-mapped

200-901 Cisco Platforms and Development Practice Question

A developer is using the Meraki Dashboard API to retrieve a list of clients for a given network. The initial GET request returns a 429 HTTP status. What should the developer do to handle this response appropriately?

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

✓

Check the Retry-After header and wait that many seconds before retrying

The Meraki API rate limits at 5 requests per second. A 429 response includes a Retry-After header indicating the number of seconds to wait before retrying.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Convert the request to a POST method to bypass the rate limit
Why it's wrong here
Rate limits apply to all HTTP methods.
✓
Check the Retry-After header and wait that many seconds before retrying
Why this is correct
Correct. The Retry-After header tells the client how long to wait.
✗
Ignore the 429 and send the request again with a different API key
Why it's wrong here
Changing the API key does not help; the rate limit is per key.
✗
Send a DELETE request to clear the rate limit counter
Why it's wrong here
No such endpoint exists.

Go deeper

200-901 Cisco Platforms and Development Practice Question

Why each option matters

Option-by-option breakdown

Related to this question