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 1 Question 70 Discussion

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

You are building the Cl/CD pipeline for an application deployed to Google Kubernetes Engine (GKE) The application is deployed by using a Kubernetes Deployment, Service, and Ingress The application team asked you to deploy the application by using the blue'green deployment methodology You need to implement the rollback actions What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

Angelica
14 days ago
I'm just imagining the poor sysadmin frantically pressing 'Ctrl+Z' in the terminal, hoping for a rollback. Kubernetes is like a genie - you gotta be really specific with your wishes!
upvoted 0 times
...
Patria
17 days ago
D is just plain weird. Scaling the new Deployment to zero? That's like asking the Kubernetes equivalent of 'Have you tried turning it off and on again?'
upvoted 0 times
Merlyn
1 days ago
Another option is to update the image of the Deployment to the previous version.
upvoted 0 times
...
Yolando
2 days ago
You can use the kubectl rollout undo command to rollback to the previous version.
upvoted 0 times
...
...
Dorcas
1 months ago
C is an interesting approach, but it's a bit hacky. Updating the Service to point to the previous Deployment seems like a workaround, not a proper rollback.
upvoted 0 times
Detra
1 days ago
Rolling back to the previous Deployment is the safest way to handle a failed blue-green deployment.
upvoted 0 times
...
Buddy
2 days ago
You can use Kubernetes' built-in rollback feature to easily switch back to the previous Deployment.
upvoted 0 times
...
...
Willis
1 months ago
B is a terrible idea! Deleting container images and running pods will just create more problems. We should never manually delete production resources.
upvoted 0 times
Sharen
9 days ago
You're right, manually deleting production resources is risky.
upvoted 0 times
...
...
Janna
2 months ago
A is the correct answer. The 'kubectl rollout undo' command is the simplest and most efficient way to rollback a deployment in Kubernetes.
upvoted 0 times
Dominic
19 days ago
A is the correct answer. The 'kubectl rollout undo' command is the simplest and most efficient way to rollback a deployment in Kubernetes.
upvoted 0 times
...
Erasmo
1 months ago
A) Run the kubectl rollout undo command
upvoted 0 times
...
...
Ena
2 months ago
I'm not sure, but maybe updating the Kubernetes Service to point to the previous Deployment could also work for rollback
upvoted 0 times
...
Rosalyn
2 months ago
I agree with Francisca, that seems like the best option to rollback the deployment
upvoted 0 times
...
Francisca
2 months ago
I think we should run the kubectl rollout undo command for rollback
upvoted 0 times
...

Save Cancel