Rollback to previous version in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Rollback Deployment to Previous Revision

You have a Kubernetes deployment named webapp. You run the command to rollback to the previous revision. What is the expected output?

Kubernetes

kubectl rollout undo deployment/webapp

A deployment.apps/webapp rolled back

B error: deployment "webapp" not found

C deployment.apps/webapp updated

D No resources found

💡 Hint

Think about what the rollback command does to the deployment state.

The command kubectl rollout undo deployment/webapp rolls back the deployment to the previous revision and confirms with the message deployment.apps/webapp rolled back.

🧠 Conceptual

intermediate

Understanding Rollback Behavior

Which statement correctly describes what happens when you run kubectl rollout undo deployment/myapp?

A It pauses the deployment without changing the current state.

B It deletes the deployment and recreates it from scratch.

C It updates the deployment to the latest image version automatically.

D It reverts the deployment to the last successful rollout revision.

💡 Hint

Rollback means going back to a previous working state.

The rollback command reverts the deployment to the last successful rollout revision, restoring the previous pod template and configuration.

❓ Troubleshoot

advanced

Rollback Failure Due to No Previous Revision

You try to rollback a deployment named api-server but get the error: error: deployment.apps "api-server" has no rollout history. What is the most likely cause?

A The deployment has never been updated since creation.

B The deployment name is misspelled in the command.

C The Kubernetes cluster is down.

D The rollback command requires a namespace flag.

💡 Hint

Rollback requires a previous revision to revert to.

If the deployment has never been updated, there is no previous revision to rollback to, causing this error.

🔀 Workflow

advanced

Steps to Rollback a Deployment

Arrange the correct sequence of commands to rollback a Kubernetes deployment named frontend to its previous version and verify the rollback status.

A 2,1,3,4

B 1,2,3,4

C 3,1,2,4

D 1,3,2,4

💡 Hint

First rollback, then check status, then inspect details.

The correct order is to rollback first, then check rollout status to confirm success, then get and describe deployment for details.

✅ Best Practice

expert

Best Practice for Safe Rollbacks

Which practice is best to ensure safe and reliable rollbacks of Kubernetes deployments?

A Disable rollout history to save cluster resources and rely on manual pod restarts.

B Always delete the deployment and recreate it with the previous image version manually.

C Use <code>kubectl rollout undo</code> only after verifying the deployment history and testing the previous version in a staging environment.

D Use <code>kubectl delete pod</code> to force pods to restart with the previous version.

💡 Hint

Safe rollback involves verification and testing before applying changes.

The best practice is to check deployment history and test the previous version in staging before rolling back in production to avoid downtime or errors.