Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Developer Topic 11 Question 99 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 99
Topic #: 11
[All Professional Cloud Developer Questions]

You are using the Cloud Client Library to upload an image in your application to Cloud Storage. Users of the application report that occasionally the upload does not complete and the client library reports an HTTP 504 Gateway Timeout error. You want to make the application more resilient to errors. What changes to the application should you make?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Kristeen
1 months ago
I wonder if the developers have tried turning it off and on again. That usually fixes everything, right?
upvoted 0 times
...
Elvera
2 months ago
A queue? That's overkill. We just need to make the upload more resilient, not turn it into a whole new workflow.
upvoted 0 times
Louisa
18 days ago
A queue? That's overkill. We just need to make the upload more resilient, not turn it into a whole new workflow.
upvoted 0 times
...
William
21 days ago
B) Write a one-second wait time backoff process around the client library call.
upvoted 0 times
...
Yasuko
1 months ago
A) Write an exponential backoff process around the client library call.
upvoted 0 times
...
...
Noel
2 months ago
A retry button? Seriously? That's just putting the burden on the user. Not cool.
upvoted 0 times
Merri
28 days ago
D) Create a queue for the object and inform the users that the application will try again in 10 minutes.
upvoted 0 times
...
Sherman
1 months ago
B) Write a one-second wait time backoff process around the client library call.
upvoted 0 times
...
Bettye
1 months ago
A) Write an exponential backoff process around the client library call.
upvoted 0 times
...
...
Nilsa
2 months ago
A one-second backoff? Really? That's barely enough time for the server to recover. We need something with a bit more oomph.
upvoted 0 times
Corinne
2 months ago
A one-second backoff? Really? That's barely enough time for the server to recover. We need something with a bit more oomph.
upvoted 0 times
...
Joanna
2 months ago
A) Write an exponential backoff process around the client library call.
upvoted 0 times
...
...
Art
2 months ago
I'm not sure about option A. Maybe option D could work too, by queuing the object and retrying later. It gives users a clear expectation.
upvoted 0 times
...
Evangelina
2 months ago
I agree with Eleonora. Exponential backoff is a common strategy to handle errors and improve application resilience.
upvoted 0 times
...
Eleonora
2 months ago
I think option A is the best choice. Exponential backoff can help handle temporary errors like the HTTP 504 Gateway Timeout.
upvoted 0 times
...
Phyliss
2 months ago
Exponential backoff is definitely the way to go here. That will give us the best chance of success without overloading the system.
upvoted 0 times
Darrin
1 months ago
That sounds like a good approach to ensure the upload eventually goes through.
upvoted 0 times
...
Lino
1 months ago
D) Create a queue for the object and inform the users that the application will try again in 10 minutes.
upvoted 0 times
...
Lynna
1 months ago
Exponential backoff is a good strategy to handle errors like this.
upvoted 0 times
...
Nickolas
2 months ago
A) Write an exponential backoff process around the client library call.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77