Free Microsoft GH-200 Actual Exam Questions - Question 6 Discussion

Maybe C? Patch release tags usually indicate stable, tested versions and rarely get moved, so they offer a pretty safe reference without jumping straight to a commit hash.

A/C? Commit hashes (A) definitely point to a fixed state and can’t be altered, which seems safest. Patch release tags (C) also usually mark stable, minor updates without breaking changes, so they’re less likely to be modified once published. But tags can technically be moved, while commit hashes cannot. So overall, A still feels more solid if you want zero risk of code changes.

Makes sense to avoid branch names since they’re mutable and can shift over time. That leaves A as the safest pick because commit hashes lock you to a fixed point. So, I’m going with A.

Maybe A, since commit hashes are immutable and unique to a specific code snapshot.

It’s A for sure. A commit hash points to an exact state of the code, so no one can change what it references afterwards. Branch names and tags like in C or D can move or be reassigned, which makes them less reliable if you want to lock in a specific version. Even if the question is vague, a commit hash is the only option that guarantees zero modification once it’s created.

C imo, patch release tags usually indicate small, stable updates and are less likely to be changed retroactively compared to branches or major tags. Safer than B or D but not as exact as a commit hash.

A vs D? Using a major release tag (D) might include more than one change over time, so it’s less precise. Commit hash (A) is a fixed snapshot, which is safer to avoid code changes.

Option A