A healthcare platform runs a read-text service as containers in a Kubernetes cluster. Release managers want repeatable deployments and quick reversion when a build misbehaves. Which approach meets this?
Show answer and explanation
Answer: D
Explicit image tags in manifests stored under version control make every deployment reproducible, and the rollback target is simply the previous manifest. Operators can see exactly which build is running at any time. Floating tags can change between pulls, so nodes may run different builds. Manual pod edits create drift that the manifests do not reflect, and hard-coded keys in images expose credentials to anyone who can pull them.
Why the other options are wrong
- A. A floating tag such as latest can change between pulls, so two nodes may run different builds and the rollback target becomes unclear.
- B. Baking a key into an image exposes the credential to anyone who can pull the image, and it forces a rebuild for every key change.
- C. Manual pod edits create configuration drift that the manifests do not reflect, which makes the cluster state hard to audit and reproduce.