MENU
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?
Suggested Answer: D
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
HO
Hoa
11 months ago
Queuing the uploads could complicate things too much.
GE
Georgeanna
11 months ago
Wait, does a 504 error really mean the server is down?
GA
Gabriele
11 months ago
A retry button sounds like a good idea!
IS
Isreal
11 months ago
I disagree, a one-second wait might be enough.
KA
Kanisha
12 months ago
Exponential backoff is the way to go!
BA
Barbra
12 months ago
Creating a queue sounds interesting, but I'm not sure if users would be okay with waiting 10 minutes. Option D might be too complicated.
BL
Blondell
1 year ago
I practiced a similar question where a retry button was suggested. It seems like option C could work, but it might not be the most user-friendly solution.
KE
Kenneth
1 year ago
I'm not entirely sure, but I feel like a one-second wait might not be enough for a 504 error. Maybe option B isn't the right approach?
DI
Diane
1 year ago
I remember studying about exponential backoff for handling retries, so I think option A might be the best choice.
JA
Janessa
1 year ago
I'm not sure about the retry button approach in option C. That seems like it would just shift the burden onto the user, which isn't ideal. I think I'll focus on the automated retry options.
TH
Theola
1 year ago
Ah, I see. The key here is making the application more resilient to errors. I'd say option A is the way to go - the exponential backoff will give us the best chance of retrying the upload successfully.
AL
Aleshia
1 year ago
Okay, I'm a bit confused by this question. I'm not sure if I should go with the one-second backoff or the exponential one. I'll need to think this through carefully.
ES
Essie
1 year ago
Hmm, this looks like a tricky one. I think I'll go with option A - an exponential backoff process. That should help handle the timeout errors more gracefully.
KR
Kristeen
1 year ago
I wonder if the developers have tried turning it off and on again. That usually fixes everything, right?
EL
Elvera
1 year ago
A queue? That's overkill. We just need to make the upload more resilient, not turn it into a whole new workflow.
LO
Louisa
1 year ago
A queue? That's overkill. We just need to make the upload more resilient, not turn it into a whole new workflow.
WI
William
1 year ago
B) Write a one-second wait time backoff process around the client library call.
YA
Yasuko
1 year ago
A) Write an exponential backoff process around the client library call.
NO
Noel
1 year ago
A retry button? Seriously? That's just putting the burden on the user. Not cool.
ME
Merri
1 year ago
D) Create a queue for the object and inform the users that the application will try again in 10 minutes.
SH
Sherman
1 year ago
B) Write a one-second wait time backoff process around the client library call.
BE
Bettye
1 year ago
A) Write an exponential backoff process around the client library call.
NI
Nilsa
2 years ago
A one-second backoff? Really? That's barely enough time for the server to recover. We need something with a bit more oomph.
CO
Corinne
1 year ago
A one-second backoff? Really? That's barely enough time for the server to recover. We need something with a bit more oomph.
JO
Joanna
1 year ago
A) Write an exponential backoff process around the client library call.
AR
Art
2 years 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.
EV
Evangelina
2 years ago
I agree with Eleonora. Exponential backoff is a common strategy to handle errors and improve application resilience.
EL
Eleonora
2 years ago
I think option A is the best choice. Exponential backoff can help handle temporary errors like the HTTP 504 Gateway Timeout.
PH
Phyliss
2 years ago
Exponential backoff is definitely the way to go here. That will give us the best chance of success without overloading the system.
DA
Darrin
1 year ago
That sounds like a good approach to ensure the upload eventually goes through.
LI
Lino
1 year ago
D) Create a queue for the object and inform the users that the application will try again in 10 minutes.
LY
Lynna
1 year ago
Exponential backoff is a good strategy to handle errors like this.
NI
Nickolas
1 year ago
A) Write an exponential backoff process around the client library call.