Which statement best describes why immutable image tags are important in deployment pipelines?

Which statement best describes why immutable image tags are important in deployment pipelines?

• A. It allows editing image content after tag creation.
• B. It ties a particular build to a unique identifier that cannot be overwritten, ensuring reproducibility across environments.
• C. It is only for archival.
• D. It makes images larger.

Answer: (B)

Immutability of image tags means that once a tag is created, it cannot be updated to point to a different image. This locks a specific build to a fixed identifier, so every deployment that uses that tag will pull the exact same image across environments. That consistency is crucial for reproducible deployments: tests, staging, and production can rely on the same content, making failures easier to reproduce and allowing seamless rollbacks by redeploying the same build. It also improves traceability, since you can tie a release, logs, and audit trails to the exact image digest behind that tag. The idea isn’t about editing the image after tagging, it isn’t merely about archival, and it doesn’t affect image size.

Immutability of image tags means that once a tag is created, it cannot be updated to point to a different image. This locks a specific build to a fixed identifier, so every deployment that uses that tag will pull the exact same image across environments. That consistency is crucial for reproducible deployments: tests, staging, and production can rely on the same content, making failures easier to reproduce and allowing seamless rollbacks by redeploying the same build. It also improves traceability, since you can tie a release, logs, and audit trails to the exact image digest behind that tag. The idea isn’t about editing the image after tagging, it isn’t merely about archival, and it doesn’t affect image size.