Question: 1/50
A developer is consuming a REST API that returns HTTP 429 responses during traffic spikes. The API includes a Retry-After header. What is the best client-side behavior?
Immediately retry the request in a tight loop until it succeeds
Retry after the time indicated by Retry-After, using backoff to avoid repeated throttling
Switch the request method from POST to GET to reduce rate limiting
Disable certificate validation to reduce connection overhead and avoid 429s