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 DevOps Engineer Exam - Topic 6 Question 61 Discussion

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?
D) Alter the deployment to point to the sha2 56 digest of the previously working container.
A) Create a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.
B) Apply the latest tag to the previous container image, and do a rolling update on the deployment.
C) Build a new container from a previous Git tag, and do a rolling update on the deployment to the new container.

Google Professional Cloud DevOps Engineer Exam - Topic 6 Question 61 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 61
Topic #: 6
[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 Mozell at Feb 13, 2024, 01:01 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Margart
7 months ago
I’ve always used option A, it’s straightforward and effective!
upvoted 0 times
...
Ernest
8 months ago
Wait, can we really just revert to a previous Git tag like that?
upvoted 0 times
...
Dyan
8 months ago
C could work too, but it feels a bit more complicated than necessary.
upvoted 0 times
...
Miriam
8 months ago
I disagree, I think option D is more precise with the sha256 digest.
upvoted 0 times
...
Adelle
8 months ago
Option A sounds solid, creating a stable tag is a good practice.
upvoted 0 times
...
Linsey
9 months ago
I think building a new container from a previous Git tag might be overkill. Isn't there a simpler way to just point to the previous image?
upvoted 0 times
...
Lenny
9 months ago
I feel like we practiced a question similar to this where we had to revert to a previous version. Was it about using the sha256 digest?
upvoted 0 times
...
Giuseppe
9 months ago
I'm not entirely sure, but I think creating a stable tag could be a good option. It seems like a safer way to revert.
upvoted 0 times
...
Pa
9 months ago
I remember we discussed the importance of using specific tags instead of the latest tag to avoid issues like this.
upvoted 0 times
...
Ilda
9 months ago
I think I've got a good handle on this. Option C seems like the most straightforward way to revert to a known working version. I'll make sure to test it thoroughly before applying the changes to the production environment.
upvoted 0 times
...
Dominga
9 months ago
Option D looks interesting - altering the deployment to point to the previous container's SHA-256 digest. I wonder if that would be a more reliable way to revert to a working version. I'll have to research that a bit more.
upvoted 0 times
...
Rossana
9 months ago
Hmm, I'm a bit unsure about this one. I'm considering option A, creating a new "stable" tag, but I'm not sure if that's the best approach. I'll have to think it through carefully.
upvoted 0 times
...
Jenifer
9 months ago
This seems like a straightforward question. I think I'll go with option C - building a new container from a previous Git tag and doing a rolling update on the deployment. That way, I can easily revert to a known working version without having to create a new tag.
upvoted 0 times
...
Phillip
9 months ago
This looks like a straightforward question about the types of variables used in discovery patterns. I'll need to carefully review the options and choose the three that best fit the description.
upvoted 0 times
...
Vashti
9 months ago
This is a good question to test our understanding of FC fabric security. WWPN zoning is definitely the way to go, and VLAN is a smart choice to add an extra layer of isolation. I feel confident about these two options.
upvoted 0 times
...
Karan
9 months ago
This is a good test of our understanding of Power BI security features. I think option B, where we have the Azure network security team create security groups and then configure RLS to use those groups, is the best approach to meet the requirements.
upvoted 0 times
...
Isaiah
10 months ago
Okay, I've got this. Services are enterprise-centric because the service-orientation approach is focused on aligning IT capabilities with business needs and requirements. I'll select the answer that best captures this idea.
upvoted 0 times
...
Bo
10 months ago
Hmm, not sure I fully understand the difference between the employer's duties and the employee's duties here. I'll need to re-read this carefully.
upvoted 0 times
...
Germaine
2 years ago
That could work too, as long as we ensure we are pointing to the correct version of the container.
upvoted 0 times
...
Jaime
2 years ago
But what about altering the deployment to point to the sha256 hash of the previous working container?
upvoted 0 times
...
Kenneth
2 years ago
Building a new container from a previous Git tag could also be a good option for updating the deployment.
upvoted 0 times
...
Germaine
2 years ago
I disagree. I believe we should apply the latest tag to the previous container image for the rolling update.
upvoted 0 times
...
Jaime
2 years ago
I think we should create a new tag called stable and point the deployment to it.
upvoted 0 times
...
Lezlie
2 years ago
I don't know, I'm kind of leaning towards option D. Pointing to the SHA256 digest seems like it might be a bit more robust, you know? It's not dependent on tags or anything like that. But I can see the appeal of C as well. Tough call.
upvoted 0 times
...
Emerson
2 years ago
Haha, can you imagine if we tried option B? 'Apply the latest tag to the previous container image'? That's like trying to put a fresh coat of paint on a broken-down car and expecting it to run better. No, I think C is the way to go. Keep it simple, you know?
upvoted 0 times
Della
2 years ago
Good call. Option C seems like the most reliable solution to get our application back on track.
upvoted 0 times
...
Reiko
2 years ago
Absolutely, simplicity is key when dealing with these kind of issues. Let's stick with option C for now.
upvoted 0 times
...
Lynna
2 years ago
Yeah, option B does sound pretty risky. I agree with you on going with option C for a safer approach.
upvoted 0 times
...
Von
2 years ago
D) Alter the deployment to point to the sha2 56 digest of the previously working container.
upvoted 0 times
...
Rex
2 years 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
...
Elden
2 years ago
B) Apply the latest tag to the previous container image, and do a rolling update on the deployment.
upvoted 0 times
...
Willard
2 years 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
...
...
Weldon
2 years ago
Yeah, I agree with you there. Option C seems like the most straightforward approach. We know the previous version was working, so let's just build a new container from that and swap it in. I'm not a big fan of the other options - they seem like they might introduce more complexity than necessary.
upvoted 0 times
...
Maile
2 years ago
Hmm, this is a tricky one. I'm not sure if I fully understand the context here. But from what I can gather, it seems like we need to revert to a previous, working version of the container image. I think option C might be the way to go - building a new container from a previous Git tag and doing a rolling update on the deployment.
upvoted 0 times
...

Save Cancel