PROFESSIONAL-CLOUD-DEVELOPER · Question #110
You support an application that uses the Cloud Storage API. You review the logs and discover multiple HTTP 503 Service Unavailable error responses from the API. Your application logs the error and doe
The correct answer is C. Retry each failure at increasing time intervals up to a maximum number of tries.. Google explicitly recommends exponential backoff with jitter as the retry strategy for transient errors like HTTP 503 (Service Unavailable). Exponential backoff means each subsequent retry waits progressively longer (e.g., 1s, 2s, 4s, 8s...) up to a maximum number of attempts. Th
Question
You support an application that uses the Cloud Storage API. You review the logs and discover multiple HTTP 503 Service Unavailable error responses from the API. Your application logs the error and does not take any further action. You want to implement Google-recommended retry logic to improve success rates. Which approach should you take?
Options
- ARetry the failures in batch after a set number of failures is logged.
- BRetry each failure at a set time interval up to a maximum number of times.
- CRetry each failure at increasing time intervals up to a maximum number of tries.
- DRetry each failure at decreasing time intervals up to a maximum number of tries.
How the community answered
(31 responses)- A13% (4)
- B3% (1)
- C77% (24)
- D6% (2)
Explanation
Google explicitly recommends exponential backoff with jitter as the retry strategy for transient errors like HTTP 503 (Service Unavailable). Exponential backoff means each subsequent retry waits progressively longer (e.g., 1s, 2s, 4s, 8s...) up to a maximum number of attempts. This prevents thundering-herd problems where many clients simultaneously retry and overwhelm an already-stressed service, giving it time to recover. Choice B (fixed interval retries) doesn't back off and can perpetuate overload. Choice D (decreasing intervals) worsens the problem by retrying faster over time. Choice A (batch retries after a threshold) introduces unnecessary delay and doesn't align with Google's per-request retry guidance.
Topics
Community Discussion
No community discussion yet for this question.