AZ-400 Question 87
Select 2Your team wants to systematically identify stable commits in a Git repository for quick reference during release cycles. You also want to include additional metadata, such as release notes, directly in the tags themselves. Because this is a distributed environment, you need these tags to be visible to everyone on the team. Which two actions should you perform to accomplish this? (Choose two.)
- A
A. Create a new branch from the stable commit, then push that branch to the remote repository
- B
B. Create an annotated tag at the stable commit that includes the release notes in the tag message
- C
C. Immediately run 'git push origin --all' to share all branches and tags with the remote repository
- D
D. Push the newly created tag to the remote repository using 'git push origin <tag_name>' or 'git push origin --tags'
- E
E. Use a separate repository to store release versions and metadata
Show answer and explanation
Correct answers: B, D
Explanation
To organize releases and important commit milestones with descriptive metadata, you should use annotated tags (not lightweight tags or branches). Once created, these tags must be pushed to the remote so they�re visible to other team members. Refer to Git documentation (https://git-scm.com/book/en/v2/Git-Basics-Tagging) and Microsoft DevOps best practices for managing tags in distributed repositories for more details.
- A. Incorrect.
A. INCORRECT. Creating a branch can mark a commit, but it doesn�t embed release metadata in the commit and can clutter your branch structure if you only need a reference point. Tags are a more direct way to mark stable commits for releases.
- B. Correct.
B. CORRECT. Annotated tags allow you to include additional data, such as release notes or descriptions, stored in the tag� metadata. This is the best practice for marking release commits with relevant information.
- C. Incorrect.
C. INCORRECT. 'git push origin --all' pushes all branches but does not automatically push new tags (unless they already exist on the remote or you�ve configured Git differently). You must explicitly push tags if you want them available to others.
- D. Correct.
D. CORRECT. After creating an annotated tag locally, you need to push it to the remote repository so the entire team can see and use it. You can either push specific tags or use 'git push origin --tags' to push all new tags.
- E. Incorrect.
E. INCORRECT. While storing metadata in a secondary system is possible, it� not required. Annotated tags are designed to hold this information directly within the Git repository itself.