MENU
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?
Suggested Answer: A
Get Premium Professional Cloud Architect (PR000213) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
SH
Sheron
6 months ago
D is definitely not the way to go. Services don’t handle images.
LI
Lilli
7 months ago
C seems risky. Deleting the deployment could cause issues.
TA
Tayna
7 months ago
B is good, but A feels more straightforward for this case.
GW
Gwen
7 months ago
But what about B? Rolling updates are solid too.
TR
Trina
7 months ago
I agree, A minimizes downtime effectively.
ED
Edelmira
7 months ago
I think option A is the best choice. Quick and easy!
PA
Paz
8 months ago
Just update the image directly with A), super easy!
KR
Kris
8 months ago
Surprised that D) is even an option, that won't help!
AN
Annett
8 months ago
C) seems risky, deleting the deployment?
ER
Ernest
8 months ago
I disagree, B) is better for rolling updates.
MA
Marilynn
9 months ago
A) is the way to go for minimal downtime!
BL
Blondell
9 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.
AN
Annmarie
9 months ago
A) Updating the image on the fly is the way to go. Gotta keep that app up and running!
AL
Alyssa
9 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.
BR
Brunilda
9 months ago
I practiced updating deployments before, and I feel like deleting and recreating the deployment isn't ideal since it might cause downtime.
KE
Kenneth
9 months ago
I think option B sounds familiar; I recall something about rolling updates being a good practice for keeping services available during updates.
YO
Yong
10 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.
CH
Chi
10 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.
LE
Lea
10 months ago
C) Updating the deployment YAML file and recreating the deployment is a more robust approach.
OR
Oretha
10 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.
RE
Regenia
10 months ago
A) Looks like the easiest way to update the image without downtime.
TA
Tammara
11 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.
TE
Terina
11 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.
MI
Mirta
11 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.
BE
Bernardo
11 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.
DA
Darrin
6 months ago
I’d stick with A as well. It’s straightforward!
SH
Shayne
6 months ago
True, but A minimizes downtime better.
JA
Janessa
6 months ago
But what about option B? Rolling updates can be useful too.
LE
Leah
6 months ago
Yeah, `kubectl set image` is quick and easy.
LI
Lizbeth
6 months ago
I agree, option A seems the most efficient.