Claude Certified Architect – Foundations Practice Question 20: Retry Backoff 429 529
Claude Certified Architect, Foundations · Test 2 · question 10 of 10
A document-processing service calls the Claude API from many workers. During peak load it intermittently receives HTTP 429 rate_limit_error and HTTP 529 overloaded_error responses. The current code retries immediately in a tight loop up to 20 times, which makes the failures worse and eventually exhausts the workers. Which retry strategy is recommended?
Show answer and explanation
Answer:
C is correct. 429 means a rate limit was reached and 529 means the API is temporarily overloaded; both are transient, so the client should retry with exponential backoff (plus jitter so workers do not retry in lockstep), cap the attempts, and wait at least as long as the retry-after header says when it is returned. The official SDKs already do this by default (twice, with exponential backoff, honoring retry-after), and max_retries can be tuned. Note that a spend-cap 429 has no retry-after and keeps failing until access resumes, so the cap on attempts matters.
A is wrong because max_tokens does not relieve request-rate limits, and immediate retries are the problem. B is wrong because these errors are transient and normally succeed on a later attempt. D is wrong because a short fixed delay with more workers increases pressure on the limit instead of backing off.
Reference: Errors - Claude API Docs