DevOps Interview DropAdvanced TierScenario+50 XP on read

Someone moved a production Git tag to a different commit. Why is that dangerous?

Core Summary

A release tag is a promise that a version name means one exact, unchanging set of code. Moving it breaks that promise everywhere at once: rollbacks, audits, incident timelines, and any pipeline that deploys by tag now point somewhere different from what people believe, and some clones won't even notice the change.

Hints

Hint 1: A tag is a movable pointer; people treat it as a fixed identity

Hint 2: Different clones can disagree about what v2.0 means

Hint 3: Digests and SHAs cannot be moved

Reported in interviews at Cloudflare, GitLab