Exam 350-901 topic 1 question 284 discussion

https://developer.cisco.com/meraki/api/#!rate-limit Best practices and tips for managing call budgets: - Handle limiting gracefully via respecting the 429 and using the Retry-After header Monitoring best practices: - Use the most efficient endpoints for your use case - Develop your application using the most efficient API calls available for your use case, especially if your application provides monitoring features.

https://developer.cisco.com/meraki/api/#!rate-limit The first best practice is to not do what is in the loop, and instead use a single larger request to avoid the rate limit.

C. Use fewer API calls to create a more efficient endpoint. E. Check for HTTP code 429 and wait until Retry-After time before further calls are made. To improve the performance of the application, two possible changes are: 1. Use fewer API calls to create a more efficient endpoint. This would reduce the number of requests sent to the Meraki API and reduce the load on the server. Check for HTTP code 429 and wait until Retry-After time before further calls are made. The 2. HTTP code 429 indicates that the API rate limit has been exceeded, and the Retry-After header indicates the number of seconds to wait before making another request. Implementing this check would help avoid unnecessary errors and prevent the application from overloading the Meraki API.

there is a rate limit of 5 calls per sec for 1 key https://developer.cisco.com/meraki/api/#!rate-limit So agree with given answer

given answer is correct.