Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 32 of 108
Free Preview · 108 of 359 · questions 1–108 of 359 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
D. Limit the upload rate from your application clients so that the dormant bucket's peak request rate is reached more gradually. Google Cloud Storage buckets have throughput limits that ramp up as sustained traffic increases, especially for previously inactive buckets. When you start sending traffic to an inactive bucket, it takes time for Cloud Storage to automatically scale to accommodate the sudden increase in traffic. By gradually increasing the traffic to the bucket, you give the Cloud Storage infrastructure time to scale and handle the increased load without failing requests.
Google Cloud Storage buckets have an initial limit on the request rate. If a bucket is inactive for a period of time, it will have a lower limit. As traffic increases, Google Cloud Storage dynamically increases the request rate limit. This process can take several minutes. If the traffic increases too quickly, you may see intermittent 5xx and 429 HTTP responses. By limiting the upload rate from your application clients, you allow the bucket’s peak request rate to increase more gradually, reducing the chance of receiving these errors.
To decrease the failed responses from the Cloud Storage API, you should limit the upload rate from your application clients so that the dormant bucket's peak request rate is reached more gradually. This will help prevent the bucket from being overwhelmed by a sudden increase in requests. A, distributing the uploads across a large number of individual storage buckets, may not necessarily decrease the failed responses and could potentially increase the complexity of the system. B, using the XML API instead of the JSON API, may not necessarily improve performance and could require significant changes to the application. C, passing the HTTP response codes back to clients, may not address the root cause of the issue and could lead to further errors.