Explanation:
The HTTP 429 error indicates the client is exceeding the rate limits for Cloud Storage requests. The recommended approach to handle transient errors like 429 is to implement retries with a truncated exponential backoff strategy. This allows the client to automatically retry failed requests with increasing delays, reducing pressure on the server and avoiding immediate retry floods. While a quota increase (Option B) might address persistent capacity issues, it is not the standard solution for transient rate limits during temporary traffic spikes. Cache-control headers (A) and storage class changes (D) do not directly address rate-limiting errors.
Ultimate access to all questions.
How should you handle HTTP 429 "Too Many Requests" errors when your service reads images from Cloud Storage during peak traffic periods?
A
Add a cache-control header to the objects.
B
Request a quota increase from the GCP Console.
C
Retry the request with a truncated exponential backoff strategy.
D
Change the storage class of the Cloud Storage bucket to Multi-regional.
No comments yet.