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

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

Contribute your Thoughts:

Kimbery
2 days 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 days 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
4 days 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
...
Hyun
8 days 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
12 days ago
I think we should create a new tag called stable and point the deployment to it.
upvoted 0 times
...
Lanie
19 days 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
Melvin
11 hours ago
Option C is definitely the safest approach.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77