Google Professional Cloud DevOps Engineer Exam - 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?

ARun the kubectl rollout undo command

BDelete the new container image, and delete the running Pods

CUpdate the Kubernetes Service to point to the previous Kubernetes Deployment

DScale the new Kubernetes Deployment to zero

Show Suggested Answer

Suggested Answer: B, D

by Paul at Jun 23, 2024, 10:30 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

Dulce

6 months ago

Definitely A, it's the standard method for rollbacks!

upvoted 0 times

...

Kenda

6 months ago

Scaling to zero is a quick fix, but not the best option.

upvoted 0 times

...

Starr

6 months ago

Wait, can you really just delete the new image? Sounds risky!

upvoted 0 times

...

Amira

7 months ago

I think C makes more sense in this case.

upvoted 0 times

...

Kate

7 months ago

A is the way to go for rollbacks!

upvoted 0 times

...

Ernestine

7 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?

upvoted 0 times

...

Ivory

7 months 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.

upvoted 0 times

...

Delbert

7 months 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.

upvoted 0 times

...

Brandon

8 months 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.

upvoted 0 times

...

Royal

8 months 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.

upvoted 0 times

...

Craig

8 months 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.

upvoted 0 times

...

Izetta

8 months 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.

upvoted 0 times

...

Leila

8 months 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.

upvoted 0 times

...

Rosio

8 months 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.

upvoted 0 times

...

Nadine

8 months 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.

upvoted 0 times

...

Dannette

8 months 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.

upvoted 0 times

...

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!

upvoted 0 times

...

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?'

upvoted 0 times

Queenie

11 months ago

You could also use the kubectl rollout history command to view the history of the Deployment and rollback to a specific revision.

upvoted 0 times

...

Sharmaine

11 months ago

It's always good to have a clear understanding of the decisions being made.

upvoted 0 times

...

Jenelle

12 months ago

I think we should discuss this with the application team to understand their reasoning.

upvoted 0 times

...

Lisandra

12 months ago

Maybe there's a reason behind it that we're not aware of.

upvoted 0 times

...

Azalee

12 months ago

I agree, that does seem like a strange approach.

upvoted 0 times

...

Merlyn

12 months ago

Another option is to update the image of the Deployment to the previous version.

upvoted 0 times

...

Yolando

12 months ago

You can use the kubectl rollout undo command to rollback to the previous version.

upvoted 0 times

...

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.

upvoted 0 times

Maile

12 months ago

I agree, updating the Service to point to the previous Deployment is not a proper rollback solution.

upvoted 0 times

...

Detra

12 months ago

Rolling back to the previous Deployment is the safest way to handle a failed blue-green deployment.

upvoted 0 times

...

Buddy

12 months ago

You can use Kubernetes' built-in rollback feature to easily switch back to the previous Deployment.

upvoted 0 times

...

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.

upvoted 0 times