What happens when you roll back to a specific revision of a Deployment?

What happens when you roll back to a specific revision of a Deployment?

• A. It reuses the original ReplicaSet and becomes the latest revision
• B. It deletes the previous ReplicaSet
• C. It creates a new ReplicaSet for the previous revision
• D. It pauses the deployment until manual confirmation

Answer: (A)

Rolling back to a specific revision reactivates the ReplicaSet that was created for that revision. Kubernetes keeps a history of ReplicaSets for each Deployment, one per revision. When you roll back, the Deployment switches its active Pod template back to that older revision and the corresponding ReplicaSet becomes the current one. The old ReplicaSet isn’t deleted; it’s simply reused as the latest revision, and the system reconciles pods to match that revision.

Rolling back to a specific revision reactivates the ReplicaSet that was created for that revision. Kubernetes keeps a history of ReplicaSets for each Deployment, one per revision. When you roll back, the Deployment switches its active Pod template back to that older revision and the corresponding ReplicaSet becomes the current one. The old ReplicaSet isn’t deleted; it’s simply reused as the latest revision, and the system reconciles pods to match that revision.