Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Architect (PR000213) Exam - Topic 3 Question 113 Discussion

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?
A) Use kubect1 set image deployment/echo-deployment <new-image>
B) Use the rolling update functionality of the Instance Group behind the Kubernetes cluster
C) Update the deployment yaml file with the new container image. Use kubect1 delete deployment/ echo-deployment and kubect1 create --f <yaml-file>
D) Update the service yaml file which the new container image. Use kubect1 delete service/echoservice and kubect1 create --f <yaml-file>

Google Professional Cloud Architect (PR000213) Exam - Topic 3 Question 113 Discussion

Actual exam question for Google's Professional Cloud Architect (PR000213) exam
Question #: 113
Topic #: 3
[All Professional Cloud Architect (PR000213) 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
Suggested Answer: A

https://cloud.google.com/kubernetes-engine/docs/how-to/updating-apps#updating_an_application


by Ricarda at Nov 21, 2025, 06:41 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sheron
5 months ago
D is definitely not the way to go. Services don’t handle images.
upvoted 0 times
...
Lilli
5 months ago
C seems risky. Deleting the deployment could cause issues.
upvoted 0 times
...
Tayna
5 months ago
B is good, but A feels more straightforward for this case.
upvoted 0 times
...
Gwen
5 months ago
But what about B? Rolling updates are solid too.
upvoted 0 times
...
Trina
6 months ago
I agree, A minimizes downtime effectively.
upvoted 0 times
...
Edelmira
6 months ago
I think option A is the best choice. Quick and easy!
upvoted 0 times
...
Paz
6 months ago
Just update the image directly with A), super easy!
upvoted 0 times
...
Kris
7 months ago
Surprised that D) is even an option, that won't help!
upvoted 0 times
...
Annett
7 months ago
C) seems risky, deleting the deployment?
upvoted 0 times
...
Ernest
7 months ago
I disagree, B) is better for rolling updates.
upvoted 0 times
...
Marilynn
7 months ago
A) is the way to go for minimal downtime!
upvoted 0 times
...
Blondell
7 months 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
7 months ago
A) Updating the image on the fly is the way to go. Gotta keep that app up and running!
upvoted 0 times
...
Alyssa
8 months 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
8 months 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
8 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
8 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
8 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
8 months ago
C) Updating the deployment YAML file and recreating the deployment is a more robust approach.
upvoted 0 times
...
Oretha
9 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
9 months ago
A) Looks like the easiest way to update the image without downtime.
upvoted 0 times
...
Tammara
9 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
9 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
9 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
10 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
Darrin
4 months ago
I’d stick with A as well. It’s straightforward!
upvoted 0 times
...
Shayne
4 months ago
True, but A minimizes downtime better.
upvoted 0 times
...
Janessa
4 months ago
But what about option B? Rolling updates can be useful too.
upvoted 0 times
...
Leah
5 months ago
Yeah, `kubectl set image` is quick and easy.
upvoted 0 times
...
Lizbeth
5 months ago
I agree, option A seems the most efficient.
upvoted 0 times
...
...

Save Cancel