Microsoft DevOps Engineer Expert AZ-400 Practice Question

Your team's Azure Repos Git repository has a shared branch named feature-alpha. A teammate accidentally executed git reset --hard HEAD~3 followed by git push --force, removing the last three commits from the remote branch. You have an existing local clone of the repository and just ran git fetch. You must now restore feature-alpha on the server. Which Git command should you run first in your local repository to locate the lost commit IDs?

git fetch --force origin feature-alpha
git revert HEAD~3..HEAD
git cherry-pick origin/feature-alpha@{1}
git reflog origin/feature-alpha

Report Issue

Answer Description

After a force-push rewrites a remote branch's history, the lost commit objects still exist on the server for a time but are no longer referenced by the branch tip. When you run git fetch in your local repository, your remote-tracking branch (origin/feature-alpha) is updated to match the new, incorrect tip. Critically, Git records this change in your local reflog for that remote-tracking branch. By running git reflog origin/feature-alpha, you can inspect the recent history of that reference and find the commit SHA it pointed to just before the fetch updated it. Once you have the correct SHA, you can restore the branch on the remote (e.g., git push origin <sha>:refs/heads/feature-alpha). The other commands are incorrect; git revert creates new commits instead of restoring old ones, git cherry-pick requires you to already know the commit SHA, and git fetch --force is not the correct command for discovering lost commit hashes.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.