The use of a "latest" tag in deploying images can lead to issues, especially for high-velocity teams that build and deploy multiple times a day, as it can turn the "latest" tag into a random, unreliable reference with no history. This approach risks unexpected results and complicates the rollback process in case of production failures, as there is no clear record of previous deployments. Multi-tagging offers a solution by maintaining versioned releases, allowing teams to track and manage image versions effectively. For example, Codefresh automatically adds tags that correspond to Git branch names, ensuring that both feature and master branches are represented, and includes production version numbers which simplify rollbacks by providing a clear history of deployments.