Which mechanism enables safely updating applications to new image versions while retaining rollback capability?

• A. ImageStream promotion policies.
• B. Rollout strategy from a Deployment.
• C. Kubernetes Secrets.
• D. Deployment supports rolling updates and rollbacks declaratively.

Answer: (D)

Deployment-based rolling updates with built-in rollback history let you upgrade applications to new image versions safely while preserving a way back to the previous state. You define the desired state in a Deployment manifest, including the container image. When you apply an update, the system performs a rolling update: it creates a new ReplicaSet for the updated pods and gradually replaces the old ones, following the rollout strategy (how many pods can be updated at once, how many can be unavailable, etc.). At the same time, the Deployment keeps the history of previous ReplicaSets, so if the new version has issues you can revert to a prior revision with a rollback operation. This declarative approach means you manage updates through your manifest and the system enforces the update process and provides an straightforward path to rollback if needed. Tools or policies that focus only on image promotion or secrets don’t offer the same integrated rollback mechanism.