Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - 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
1 months 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
1 months 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
Sharmaine
5 days ago
It's always good to have a clear understanding of the decisions being made.
upvoted 0 times
...
Jenelle
9 days ago
I think we should discuss this with the application team to understand their reasoning.
upvoted 0 times
...
Lisandra
11 days ago
Maybe there's a reason behind it that we're not aware of.
upvoted 0 times
...
Azalee
15 days ago
I agree, that does seem like a strange approach.
upvoted 0 times
...
Merlyn
18 days ago
Another option is to update the image of the Deployment to the previous version.
upvoted 0 times
...
Yolando
19 days ago
You can use the kubectl rollout undo command to rollback to the previous version.
upvoted 0 times
...
...
Dorcas
2 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
Maile
15 days ago
I agree, updating the Service to point to the previous Deployment is not a proper rollback solution.
upvoted 0 times
...
Detra
18 days ago
Rolling back to the previous Deployment is the safest way to handle a failed blue-green deployment.
upvoted 0 times
...
Buddy
19 days ago
You can use Kubernetes' built-in rollback feature to easily switch back to the previous Deployment.
upvoted 0 times
...
...
Willis
2 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
Tambra
10 days ago
Let's create a script to handle the rollback actions automatically.
upvoted 0 times
...
Daniela
11 days ago
We should automate the rollback process to avoid any issues.
upvoted 0 times
...
Sharen
26 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
1 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
...
Erasmo
2 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
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