A municipal CD pipeline promotes a civic API that talks to Meraki and DNA Center. Operators need reliable rollback to the last known-good build. Which image naming practice gives CD a stable release identity?
Select an answer to reveal the explanation.
Short Explanation
Think of a version tag like a stamped permit number on a blueprint—you can always pull that exact set. latest is a moving nickname, so rollback becomes guesswork when last week’s build vanished under a new latest.
Full Explanation
Continuous delivery needs an immutable release identity so promotion, audit, and rollback target the same artifact. Tags such as myapp:1.4.2 or a git-sha pin what ran; floating latest alone does not. Overwriting a single tag or chasing dangling IDs breaks reproducible deploys for Cisco API consumers just as it would for any containerized service.