MENU
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?
Suggested Answer: B, D
Get Premium Professional Cloud DevOps Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
DU
Dulce
11 months ago
Definitely A, it's the standard method for rollbacks!
KE
Kenda
11 months ago
Scaling to zero is a quick fix, but not the best option.
ST
Starr
11 months ago
Wait, can you really just delete the new image? Sounds risky!
AM
Amira
11 months ago
I think C makes more sense in this case.
KA
Kate
12 months ago
A is the way to go for rollbacks!
ER
Ernestine
12 months ago
Scaling the new Deployment to zero sounds like a way to stop the new version, but I wonder if that really counts as a rollback?
IV
Ivory
1 year ago
I practiced a similar question where we had to update the Service to point to a previous Deployment. That might be a valid option here too.
DE
Delbert
1 year ago
I'm not entirely sure, but I feel like deleting the new container image might not be the best approach since it could cause issues with the existing Pods.
BR
Brandon
1 year ago
I remember studying the rollback process, and I think the kubectl rollout undo command is the standard way to revert to a previous deployment.
RO
Royal
1 year ago
Okay, let me think this through. Since we're using a Kubernetes Deployment, Service, and Ingress, I think the best approach would be to update the Service to point to the previous Deployment. That way, we can easily switch back to the previous version.
CR
Craig
1 year ago
Hmm, I'm a bit unsure about this one. I know the kubectl rollout undo command is used for rollbacks, but I'm not sure if that's the right approach for a blue-green deployment.
IZ
Izetta
1 year ago
This looks like a classic Kubernetes deployment question. I think the key is understanding the blue-green deployment methodology and how to implement rollback actions.
LE
Leila
1 year ago
I've got this! The answer is definitely A - run the kubectl rollout undo command. That's the standard way to roll back a Kubernetes deployment.
RO
Rosio
1 year ago
Hmm, I'm a bit confused by all the details in this question. I'll need to make sure I fully understand the company's operations, the forward rate agreement, and the potential currency and commodity risks before I can decide on the appropriate hedging strategy.
NA
Nadine
1 year ago
Hmm, I'm a bit confused about the difference between expedited and auto-expedited queues. I'll need to review that part of the material again.
DA
Dannette
1 year ago
This one seems tricky, but I think I can figure it out. I'll start by checking the permissions for the security analyst role and see if that's the issue.
AN
Angelica
1 year 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!
PA
Patria
1 year 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?'
QU
Queenie
1 year ago
You could also use the kubectl rollout history command to view the history of the Deployment and rollback to a specific revision.
SH
Sharmaine
1 year ago
It's always good to have a clear understanding of the decisions being made.
JE
Jenelle
1 year ago
I think we should discuss this with the application team to understand their reasoning.
LI
Lisandra
1 year ago
Maybe there's a reason behind it that we're not aware of.
AZ
Azalee
1 year ago
I agree, that does seem like a strange approach.
ME
Merlyn
1 year ago
Another option is to update the image of the Deployment to the previous version.
YO
Yolando
1 year ago
You can use the kubectl rollout undo command to rollback to the previous version.
DO
Dorcas
1 year 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.
MA
Maile
1 year ago
I agree, updating the Service to point to the previous Deployment is not a proper rollback solution.
DE
Detra
1 year ago
Rolling back to the previous Deployment is the safest way to handle a failed blue-green deployment.
BU
Buddy
1 year ago
You can use Kubernetes' built-in rollback feature to easily switch back to the previous Deployment.
WI
Willis
1 year ago
B is a terrible idea! Deleting container images and running pods will just create more problems. We should never manually delete production resources.
TA
Tambra
1 year ago
Let's create a script to handle the rollback actions automatically.
DA
Daniela
1 year ago
We should automate the rollback process to avoid any issues.
SH
Sharen
1 year ago
You're right, manually deleting production resources is risky.
JA
Janna
2 years ago
A is the correct answer. The 'kubectl rollout undo' command is the simplest and most efficient way to rollback a deployment in Kubernetes.
DO
Dominic
1 year ago
A is the correct answer. The 'kubectl rollout undo' command is the simplest and most efficient way to rollback a deployment in Kubernetes.
ER
Erasmo
1 year ago
A) Run the kubectl rollout undo command
EN
Ena
2 years ago
I'm not sure, but maybe updating the Kubernetes Service to point to the previous Deployment could also work for rollback
RO
Rosalyn
2 years ago
I agree with Francisca, that seems like the best option to rollback the deployment
FR
Francisca
2 years ago
I think we should run the kubectl rollout undo command for rollback