Question: Why is it best practice to add a delay between automatic, repeated API calls?
- It ensures another call won’t happen if the first call isn’t successful.
- It lessens the chance you’ll receive 404 errors.
- It lessens the chance you’ll receive 5xx temporarily overloaded errors.
- It keeps your integration running faster.
Explanation
Adding a delay between repeated calls gives the service time to recover before another request is sent. Temporary server-side issues can return 5xx errors when the platform is overloaded or unavailable. In Amazon Ads integrations, controlled retry behavior helps protect API stability and prevents repeated failed requests from increasing load. Delays are especially useful when paired with rate limiting handling. This approach improves reliability without forcing unnecessary request volume.
Why the other options are incorrect
First call This is incorrect because a delay does not guarantee that later calls will stop after one failed request.
404 errors This is incorrect because 404 errors usually mean the requested resource or endpoint was not found.
Faster integration This is incorrect because delays may slow repeated calls, but they improve stability.
Source for verification
https://advertising.amazon.com/API/docs/en-us/reference/concepts/rate-limiting
The answer(s) to the question is highlighted in the BOLD text above. You can also find more questions and answers related to the exams on the "Integrating With HubSpot I: Foundations" page.