Cyber Monday 2024! 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 Exam Professional Cloud DevOps Engineer Topic 4 Question 80 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 80
Topic #: 4
[All Professional Cloud DevOps Engineer Questions]

You are investigating issues in your production application that runs on Google Kubernetes Engine (GKE). You determined that the source Of the issue is a recently updated container image, although the exact change in code was not identified. The deployment is currently pointing to the latest tag. You need to update your cluster to run a version of the container that functions as intended. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Doyle at Sep 17, 2024, 02:44 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Belen
2 months ago
C is definitely the way to go. You don't want to be playing around with the latest tag or digest when you're trying to fix a production issue. Keep it simple and go with the known-good version.
upvoted 0 times
...
Kimbery
2 months ago
But what if the issue is with the latest tag itself? Maybe building a new container from a previous Git tag is a safer option.
upvoted 0 times
...
Zita
2 months ago
Haha, I'd just unplug the whole cluster and hope it turns itself off and on again. But in all seriousness, Option C seems like the most logical solution.
upvoted 0 times
...
Kanisha
2 months ago
Agreed, Option C is the best choice here. Maintaining a stable and reliable deployment is crucial, and rolling back to a previous working version is the smart move.
upvoted 0 times
Krystal
29 days ago
Rolling update to a previous container version is a good practice. Option C is the best choice in this scenario.
upvoted 0 times
...
Erick
1 months ago
I agree, it's important to maintain stability in production environments. Option C seems like the most reliable solution.
upvoted 0 times
...
Sheron
1 months ago
Option C is definitely the way to go. Rolling back to a previous working version is the safest bet.
upvoted 0 times
...
Jill
2 months ago
Agreed, Option C is the best choice here. Maintaining a stable and reliable deployment is crucial, and rolling back to a previous working version is the smart move.
upvoted 0 times
...
Estrella
2 months ago
C) Build a new container from a previous Git tag, and do a rolling update on the deployment to the new container.
upvoted 0 times
...
Effie
2 months ago
A) Create a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.
upvoted 0 times
...
...
Hyun
2 months ago
I disagree, I believe we should apply the latest tag to the previous container image and do a rolling update.
upvoted 0 times
...
Kimbery
2 months ago
I think we should create a new tag called stable and point the deployment to it.
upvoted 0 times
...
Lanie
3 months ago
Option C is the way to go. Building a new container from a previous Git tag and doing a rolling update is the safest approach to ensure the cluster runs a known-good version.
upvoted 0 times
Brittney
2 months ago
Doing a rolling update on the deployment will help with a smooth transition to the new container.
upvoted 0 times
...
Sharika
2 months ago
It's important to make sure the cluster runs a known-good version to avoid any issues.
upvoted 0 times
...
Lacey
2 months ago
I agree, building a new container from a previous Git tag is a good way to ensure stability.
upvoted 0 times
...
Melvin
2 months ago
Option C is definitely the safest approach.
upvoted 0 times
...
...

Save Cancel