New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud Architect Exam - Topic 3 Question 113 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 113
Topic #: 3
[All Professional Cloud Architect Questions]

You have an application deployed on Kubernetes Engine using a Deployment named echo-deployment. The deployment is exposed using a Service called echo-service. You need to perform an update to the application with minimal downtime to the application. What should you do?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Paz
9 hours ago
Just update the image directly with A), super easy!
upvoted 0 times
...
Kris
6 days ago
Surprised that D) is even an option, that won't help!
upvoted 0 times
...
Annett
11 days ago
C) seems risky, deleting the deployment?
upvoted 0 times
...
Ernest
16 days ago
I disagree, B) is better for rolling updates.
upvoted 0 times
...
Marilynn
21 days ago
A) is the way to go for minimal downtime!
upvoted 0 times
...
Blondell
26 days ago
B) Using the rolling update on the Instance Group is a good option too, but might be overkill for a simple image update.
upvoted 0 times
...
Annmarie
1 month ago
A) Updating the image on the fly is the way to go. Gotta keep that app up and running!
upvoted 0 times
...
Alyssa
1 month ago
I don't think updating the service yaml is the right approach here; it seems like the deployment is what needs the new image.
upvoted 0 times
...
Brunilda
1 month ago
I practiced updating deployments before, and I feel like deleting and recreating the deployment isn't ideal since it might cause downtime.
upvoted 0 times
...
Kenneth
2 months ago
I think option B sounds familiar; I recall something about rolling updates being a good practice for keeping services available during updates.
upvoted 0 times
...
Yong
2 months ago
I remember we talked about using `kubectl set image` for updates, but I'm not sure if that's the best option for minimizing downtime.
upvoted 0 times
...
Chi
2 months ago
I'm not sure about option B - updating the Instance Group behind the cluster seems like it might be overkill for just updating the container image. I think I'll go with option A as well.
upvoted 0 times
...
Lea
2 months ago
C) Updating the deployment YAML file and recreating the deployment is a more robust approach.
upvoted 0 times
...
Oretha
2 months ago
I agree with Bernardo - option A is the easiest way to update the image without having to delete and recreate the deployment. The rolling update functionality should handle the transition smoothly.
upvoted 0 times
...
Regenia
2 months ago
A) Looks like the easiest way to update the image without downtime.
upvoted 0 times
...
Tammara
3 months ago
Hmm, I wonder if there's a way to do this with a single command and no YAML files? That would be the ultimate hack.
upvoted 0 times
...
Terina
3 months ago
Option D doesn't make much sense to me. Updating the service YAML file won't actually update the container image in the deployment. I'd stick with option A or C for this.
upvoted 0 times
...
Mirta
3 months ago
Hmm, I'm a bit confused. Wouldn't option C be better, where we update the deployment YAML file and then apply the changes? That way we have the full configuration in version control.
upvoted 0 times
...
Bernardo
3 months ago
This looks like a straightforward Kubernetes update question. I think option A is the way to go - using `kubectl set image` to update the container image in the deployment with minimal downtime.
upvoted 0 times
...

Save Cancel