You want to rollback your deployment 'backend' to the previous version after a failed update. Which sequence of commands correctly checks the history and rolls back?

hard📝 Workflow Q15 of 15

Kubernetes - ReplicaSets and Deployments

Akubectl rollout history deployment/backend<br>kubectl rollout undo deployment/backend

Bkubectl rollout status deployment/backend<br>kubectl delete deployment/backend

Ckubectl get pods -l app=backend<br>kubectl rollout history deployment/backend

Dkubectl rollout undo deployment/backend<br>kubectl rollout history deployment/backend

Step-by-Step Solution

Solution:

Step 1: Check rollout history
Use kubectl rollout history deployment/backend to see past versions and confirm rollback target.
Step 2: Rollback to previous version
Use kubectl rollout undo deployment/backend to revert to the last successful deployment.
Final Answer:
kubectl rollout history deployment/backend followed by kubectl rollout undo deployment/backend -> Option A
Quick Check:
History then undo = safe rollback steps [OK]

Quick Trick: Always check history before undoing a rollout [OK]

Common Mistakes:

Deleting deployment instead of rolling back
Undoing before checking history
Confusing status command with rollback

Master "ReplicaSets and Deployments" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kubernetes Quizzes

You want to rollback your deployment 'backend' to the previous version after a failed update. Which sequence of commands correctly checks the history and rolls back?

Step 1: Check rollout history

Step 2: Rollback to previous version

Final Answer:

Quick Check:

Want More Practice?