PROFESSIONAL-CLOUD-DEVELOPER · Question #313
Your team uses Cloud Storage for a video and image application that was recently migrated to Google Cloud. Following a viral surge, users are reporting application instability, coinciding with a 10x i
The correct answer is D. Implement a retry strategy with exponential backoff for requests that encounter HTTP 429 errors.. HTTP 429 errors from Cloud Storage indicate the application is hitting API rate limits or quotas. The correct and Google-recommended long-term solution (option D) is to implement a retry strategy with exponential backoff. Exponential backoff automatically spaces out retry attempt
Question
Your team uses Cloud Storage for a video and image application that was recently migrated to Google Cloud. Following a viral surge, users are reporting application instability, coinciding with a 10x increase in HTTP 429 error codes from Cloud Storage APIs. You need to resolve the errors and establish a long-term solution. You want to ensure that the application remains stable if the load increases again in the future. What should you do?
Options
- AOptimize the application code to reduce unnecessary calls to Cloud Storage APIs to prevent
- BCompress the video and images files to reduce their size, and minimize storage costs and
- CMigrate all image and video data to Firestore. Replace the Cloud Storage APIs in the application
- DImplement a retry strategy with exponential backoff for requests that encounter HTTP 429 errors.
How the community answered
(34 responses)- A3% (1)
- B6% (2)
- C9% (3)
- D82% (28)
Explanation
HTTP 429 errors from Cloud Storage indicate the application is hitting API rate limits or quotas. The correct and Google-recommended long-term solution (option D) is to implement a retry strategy with exponential backoff. Exponential backoff automatically spaces out retry attempts with increasing delays plus random jitter, reducing the thundering-herd effect and preventing the application from overwhelming the API further. This makes the application resilient to future spikes without requiring architectural changes. Option A (reducing unnecessary API calls) is also good hygiene but does not address burst traffic scenarios. Option B (compressing files) addresses storage cost, not rate limiting. Option C (migrating to Firestore) is a costly, complex migration that is not appropriate for video/image blob storage.
Topics
Community Discussion
No community discussion yet for this question.