Google Professional Cloud Developer
Get started today
Ultimate access to all questions.
You are conducting load testing on your server application. Initially, you notice that a previously idle Cloud Storage bucket is now handling 2000 write requests per second and 7500 read requests per second. As demand increases, your application starts receiving sporadic 5xx and 429 HTTP responses from the Cloud Storage JSON API. Your goal is to reduce these failed responses from the Cloud Storage API.
What should you do?
You are conducting load testing on your server application. Initially, you notice that a previously idle Cloud Storage bucket is now handling 2000 write requests per second and 7500 read requests per second. As demand increases, your application starts receiving sporadic 5xx and 429 HTTP responses from the Cloud Storage JSON API. Your goal is to reduce these failed responses from the Cloud Storage API.
What should you do?
Explanation:
The correct approach to decrease the failed responses from the Cloud Storage API is to distribute the uploads across a large number of individual storage buckets. This method directly addresses the issue by not exceeding the per-bucket write limit of the JSON API, which is 1,000 operations per second. By spreading the load across multiple buckets, you avoid hitting the rate limits that cause the 429 and 5xx HTTP responses. This solution is scalable and aligns with best practices for handling high request rates in Google Cloud Storage.