Answer-first summary for fast verification
Answer: Implement a retry strategy with exponential backoff for requests that encounter HTTP 429 errors.
The HTTP 429 error codes indicate that the application is hitting the rate limits of Cloud Storage APIs due to the increased load. To resolve these errors and ensure the application remains stable under future load increases, implementing a retry strategy with exponential backoff (Option D) is the most effective solution. This approach not only handles the immediate issue by automatically retrying failed requests with increasing delays but also provides a long-term solution by preventing the application from overwhelming the Cloud Storage APIs during traffic surges. While optimizing the application code (Option A) can reduce unnecessary calls, it may not be sufficient during legitimate surges in traffic. Compressing files (Option B) reduces size and costs but does not address the rate limit issue. Migrating to Firestore (Option C) is not suitable for storing large media files like videos and images. Therefore, Option D is the correct choice for both resolving the current errors and ensuring future stability.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your team's video and image application, recently migrated to Google Cloud, uses Cloud Storage. After a viral surge, users report instability with a 10x increase in HTTP 429 errors from Cloud Storage APIs. How do you resolve these errors and implement a long-term solution to maintain application stability during future load spikes?
A
Optimize the application code to reduce unnecessary calls to Cloud Storage APIs to prevent HTTP 429 errors.
B
Compress the video and images files to reduce their size, and minimize storage costs and bandwidth usage. Implement a custom throttling mechanism in the application that limits the number of concurrent API calls.
C
Migrate all image and video data to Firestore. Replace the Cloud Storage APIs in the application code with the new Firestore database.
D
Implement a retry strategy with exponential backoff for requests that encounter HTTP 429 errors.
No comments yet.