You have an application that makes HTTP requests to Cloud Storage. Occasionally the requests fail with HTTP status codes of 5xx and 429. How should you handle these types of errors?

The correct answer is B. Implement retry logic using a truncated exponential backoff strategy.. You should use exponential backoff to retry your requests when receiving errors with 5xx or 429 response codes from Cloud Storage. https://cloud.google.com/storage/docs/request-rate

Submitted by katya_ua· Mar 30, 2026Ensuring solution and operations reliability

Question

You have an application that makes HTTP requests to Cloud Storage. Occasionally the requests fail with HTTP status codes of 5xx and 429. How should you handle these types of errors?

Options

AUse gRPC instead of HTTP for better performance.
BImplement retry logic using a truncated exponential backoff strategy.
CMake sure the Cloud Storage bucket is multi-regional for geo-redundancy.
DMonitor https://status.cloud.google.com/feed.atom and only make requests if Cloud Storage is not

How the community answered

(24 responses)

A
4% (1)
B
92% (22)
D
4% (1)

Explanation

You should use exponential backoff to retry your requests when receiving errors with 5xx or 429 response codes from Cloud Storage. https://cloud.google.com/storage/docs/request-rate

Topics

#exponential backoff#retry logic#HTTP 5xx#error handling

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-ARCHITECT Practice