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?

ACreate a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.

BApply the latest tag to the previous container image, and do a rolling update on the deployment.

CBuild a new container from a previous Git tag, and do a rolling update on the deployment to the new container.

DAlter the deployment to point to the sha2 56 digest of the previously working container.

Show Suggested 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

...

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