Microsoft GH-900 Practice Test 10
Question 90
An administrator is building an ongoing checklist for this issue: A maintainer wants to describe a documentation change, collect review and verify CI before exposing it on main. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Use descriptive branch naming and routine branch cleanup after changes are merged safely.
- Maintain short-lived branches and consistent pull request reviews for repeated contributions.
- Teach the team to inspect clean working-tree status and label temporary stashes for interrupted work.
- Require successful checks and review before integration and remove obsolete short-lived branches afterward.
Explanation
Correct Answer
B:Maintain short-lived branches and consistent pull request reviews for repeated contributions. Check periodically that the approved change reaches the protected default branch with review context and successful required checks recorded. It complements the initial correction to follow GitHub flow: create a branch, commit changes, open a pull request, review and test, then merge approved work.
Incorrect Answers
A:Use descriptive branch naming and routine branch cleanup after changes are merged safely. Check periodically that the approved change reaches the protected default branch with review context and successful required checks recorded. This would not prevent the recurrence of the github flow from change to merge failure.
C:Teach the team to inspect clean working-tree status and label temporary stashes for interrupted work. Check periodically that the approved change reaches the protected default branch with review context and successful required checks recorded. This would not prevent the recurrence of the github flow from change to merge failure.
D:Require successful checks and review before integration and remove obsolete short-lived branches afterward. Check periodically that the approved change reaches the protected default branch with review context and successful required checks recorded. This would not prevent the recurrence of the github flow from change to merge failure.
Question 91
A developer evaluates unsafe proposals following this situation: A maintainer wants to describe a documentation change, collect review and verify CI before exposing it on main. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Use GitHub Mobile for supported issue, notification and pull request triage, escalating complex code changes to a suitable review environment.
- Place shared organization-owned work in an appropriate organization repository with managed team access.
- Skip branching and review because Github Flow consists only of changing files on the default branch.
- Identify whether the requirement calls for GitHub Enterprise Cloud or a managed GitHub Enterprise Server deployment.
Explanation
Correct Answer
C:Skip branching and review because Github Flow consists only of changing files on the default branch. Objective closure would show that the approved change reaches the protected default branch with review context and successful required checks recorded. The unsafe proposal is to skip branching and review because Github Flow consists only of changing files on the default branch. A maintainer wants to describe a documentation change, collect review and verify CI before exposing it on main.
Incorrect Answers
A:Use GitHub Mobile for supported issue, notification and pull request triage, escalating complex code changes to a suitable review environment. Objective closure would show that the approved change reaches the protected default branch with review context and successful required checks recorded. The direct risk in the case is github flow from change to merge, not this other concern.
B:Place shared organization-owned work in an appropriate organization repository with managed team access. Objective closure would show that the approved change reaches the protected default branch with review context and successful required checks recorded. The direct risk in the case is github flow from change to merge, not this other concern.
D:Identify whether the requirement calls for GitHub Enterprise Cloud or a managed GitHub Enterprise Server deployment. Objective closure would show that the approved change reaches the protected default branch with review context and successful required checks recorded. The direct risk in the case is github flow from change to merge, not this other concern.
Question 92
A project owner is investigating an operational GitHub workflow issue: A teammate questions what changed between two documentation releases but another engineer offers only screenshots of both pages. What is the most defensible technical action for this case? Select ONE answer.
- Follow GitHub flow: create a branch, commit changes, open a pull request, review and test, then merge approved work.
- Fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
- Configure an appropriate Git author name and email before new work and distinguish commit attribution from authenticated pushing.
- Use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions.
Explanation
Correct Answer
D:Use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. The first useful confirmation step is to review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps.
Incorrect Answers
A:Follow GitHub flow: create a branch, commit changes, open a pull request, review and test, then merge approved work. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. The case instead calls for the following: use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions.
B:Fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. The case instead calls for the following: use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions.
C:Configure an appropriate Git author name and email before new work and distinguish commit attribution from authenticated pushing. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. The case instead calls for the following: use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions.
Question 93
An administrator requests evidence about this repository behavior: A teammate questions what changed between two documentation releases but another engineer offers only screenshots of both pages. Which focused investigation provides the most useful initial evidence? Select ONE answer.
- Review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps.
- Locate the repository root and inspect tracked paths and commit history to see whether the project is divided accidentally.
- Check whether the local directory has a remote URL and commit graph matching the team's intended upstream repository.
- Compare git status and staged versus unstaged diffs before creating the commit to confirm exactly which changes are included.
Explanation
Correct Answer
A:Review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. If the check supports this diagnosis, the next controlled response is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. Verify the improvement by checking that reviewers can enumerate the exact changed files and point to the specific commit that introduced each intended modification.
Incorrect Answers
B:Locate the repository root and inspect tracked paths and commit history to see whether the project is divided accidentally. If the check supports this diagnosis, the next controlled response is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. It does not isolate the keep branch history traceable through diffs issue described.
C:Check whether the local directory has a remote URL and commit graph matching the team's intended upstream repository. If the check supports this diagnosis, the next controlled response is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. It does not isolate the keep branch history traceable through diffs issue described.
D:Compare git status and staged versus unstaged diffs before creating the commit to confirm exactly which changes are included. If the check supports this diagnosis, the next controlled response is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. It does not isolate the keep branch history traceable through diffs issue described.
Question 94
A project sponsor requires a clear acceptance check for this scenario: A teammate questions what changed between two documentation releases but another engineer offers only screenshots of both pages. How should the team demonstrate that the approved change worked? Select ONE answer.
- The feature integrates correctly with an understandable graph, and no teammate is forced to repair unexpected published history.
- Reviewers can enumerate the exact changed files and point to the specific commit that introduced each intended modification.
- Readers can identify the steps, quoted code and supporting references without misunderstanding the message.
- The issue visibly separates completed tasks from remaining ones, and checks correspond to real reviewed work.
Explanation
Correct Answer
B:Reviewers can enumerate the exact changed files and point to the specific commit that introduced each intended modification. An independent review should first review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. Closing an issue without this result would not prove technical resolution because A diff compares tracked content between revisions and exposes additions, deletions and context needed for review.
Incorrect Answers
A:The feature integrates correctly with an understandable graph, and no teammate is forced to repair unexpected published history. An independent review should first review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. This validates an adjacent control rather than the outcome of keep branch history traceable through diffs.
C:Readers can identify the steps, quoted code and supporting references without misunderstanding the message. An independent review should first review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. This validates an adjacent control rather than the outcome of keep branch history traceable through diffs.
D:The issue visibly separates completed tasks from remaining ones, and checks correspond to real reviewed work. An independent review should first review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. This validates an adjacent control rather than the outcome of keep branch history traceable through diffs.
Question 95
A GitHub maintainer must reject an unsound recommendation after this report: A teammate questions what changed between two documentation releases but another engineer offers only screenshots of both pages. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Push the intended local feature branch to the authorized GitHub remote so collaborators can review the new commits.
- Follow GitHub flow: create a branch, commit changes, open a pull request, review and test, then merge approved work.
- Infer precise modifications from file modification dates without inspecting versioned diffs.
- Fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
Explanation
Correct Answer
C:Infer precise modifications from file modification dates without inspecting versioned diffs. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps.
Incorrect Answers
A:Push the intended local feature branch to the authorized GitHub remote so collaborators can review the new commits. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. The reported issue instead calls for rejecting infer precise modifications from file modification dates without inspecting versioned diffs.
B:Follow GitHub flow: create a branch, commit changes, open a pull request, review and test, then merge approved work. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. The reported issue instead calls for rejecting infer precise modifications from file modification dates without inspecting versioned diffs.
D:Fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. The reported issue instead calls for rejecting infer precise modifications from file modification dates without inspecting versioned diffs.
Question 96
During a repository review, the maintainer finds this condition: A project coordinator receives two feature branches and cannot tell which exact lines differ from the main revision. What is the most defensible technical action for this case? Select ONE answer.
- Put the source under Git version control and record focused changes as commits with meaningful descriptions.
- Explain that Git manages local distributed history and explicitly push the intended branch to a GitHub remote for sharing.
- Define a sensible repository boundary encompassing the related files and their coherent Git revision history.
- Use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions.
Explanation
Correct Answer
D:Use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. The first useful confirmation step is to review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. A project coordinator receives two feature branches and cannot tell which exact lines differ from the main revision.
Incorrect Answers
A:Put the source under Git version control and record focused changes as commits with meaningful descriptions. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. Applying it first would leave keep branch history traceable through diffs unresolved.
B:Explain that Git manages local distributed history and explicitly push the intended branch to a GitHub remote for sharing. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. Applying it first would leave keep branch history traceable through diffs unresolved.
C:Define a sensible repository boundary encompassing the related files and their coherent Git revision history. A diff compares tracked content between revisions and exposes additions, deletions and context needed for review. Applying it first would leave keep branch history traceable through diffs unresolved.
Question 97
A GitHub team reviews how to prevent recurrence after this case: A project coordinator receives two feature branches and cannot tell which exact lines differ from the main revision. What operational safeguard should remain after the immediate fix? Select ONE answer.
- Require a link to the relevant commit or pull request diff for future change reviews.
- Use a consistent release tag naming policy and verify artifact provenance against the tagged commit.
- Prevent committing secrets in the first place and use an approved history-remediation process if confidential data was exposed.
- Set branch integration guidance that distinguishes safe local cleanup from hazardous history rewriting.
Explanation
Correct Answer
A:Require a link to the relevant commit or pull request diff for future change reviews. It complements the initial correction to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. Check periodically that reviewers can enumerate the exact changed files and point to the specific commit that introduced each intended modification.
Incorrect Answers
B:Use a consistent release tag naming policy and verify artifact provenance against the tagged commit. It complements the initial correction to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. This would not prevent the recurrence of the keep branch history traceable through diffs failure.
C:Prevent committing secrets in the first place and use an approved history-remediation process if confidential data was exposed. It complements the initial correction to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. This would not prevent the recurrence of the keep branch history traceable through diffs failure.
D:Set branch integration guidance that distinguishes safe local cleanup from hazardous history rewriting. It complements the initial correction to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions. This would not prevent the recurrence of the keep branch history traceable through diffs failure.
Question 98
A pull request discussion contains questionable workarounds for this report: A project coordinator receives two feature branches and cannot tell which exact lines differ from the main revision. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.
- Reconcile the competing edits manually against the intended behavior and complete the merge with verified resolved content.
- Infer precise modifications from file modification dates without inspecting versioned diffs.
- Use git fetch to update remote-tracking references without automatically merging those updates into the current work.
- Push the intended local feature branch to the authorized GitHub remote so collaborators can review the new commits.
Explanation
Correct Answer
B:Infer precise modifications from file modification dates without inspecting versioned diffs. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. A project coordinator receives two feature branches and cannot tell which exact lines differ from the main revision.
Incorrect Answers
A:Reconcile the competing edits manually against the intended behavior and complete the merge with verified resolved content. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. The direct risk in the case is keep branch history traceable through diffs, not this other concern.
C:Use git fetch to update remote-tracking references without automatically merging those updates into the current work. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. The direct risk in the case is keep branch history traceable through diffs, not this other concern.
D:Push the intended local feature branch to the authorized GitHub remote so collaborators can review the new commits. The safer GitHub workflow is to use GitHub's compare view or Git diff to inspect file-level and line-level changes between the relevant revisions after checking whether the team can review the changed-file list and added/deleted lines against the intended commit range rather than comparing folder timestamps. The direct risk in the case is keep branch history traceable through diffs, not this other concern.
Question 99
A GitHub platform user encounters this scenario: A GitHub pull request shows updated files but a teammate's local branch still points at a week-old commit. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.
- Use GitHub Mobile for supported issue, notification and pull request triage, escalating complex code changes to a suitable review environment.
- Place shared organization-owned work in an appropriate organization repository with managed team access.
- Fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
- Identify whether the requirement calls for GitHub Enterprise Cloud or a managed GitHub Enterprise Server deployment.
Explanation
Correct Answer
C:Fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work. Branch references can differ between distributed repositories until explicit network synchronization occurs. The first useful confirmation step is to check local and remote-tracking commit IDs and compare their graph to see how far the local checkout lags.
Incorrect Answers
A:Use GitHub Mobile for supported issue, notification and pull request triage, escalating complex code changes to a suitable review environment. Branch references can differ between distributed repositories until explicit network synchronization occurs. The case instead calls for the following: fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
B:Place shared organization-owned work in an appropriate organization repository with managed team access. Branch references can differ between distributed repositories until explicit network synchronization occurs. The case instead calls for the following: fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
D:Identify whether the requirement calls for GitHub Enterprise Cloud or a managed GitHub Enterprise Server deployment. Branch references can differ between distributed repositories until explicit network synchronization occurs. The case instead calls for the following: fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
Question 100
A developer starts an investigation after the following user report: A GitHub pull request shows updated files but a teammate's local branch still points at a week-old commit. Which diagnostic review best explains this exact reported behavior? Select ONE answer.
- Inspect the faulty commit's diff and ancestry before preparing and reviewing its inverse patch.
- Review git status and the exact file diff to avoid discarding unrelated work during the restore.
- Examine git remote -v and the branch's upstream tracking configuration to establish destination and expected permissions.
- Check local and remote-tracking commit IDs and compare their graph to see how far the local checkout lags.
Explanation
Correct Answer
D:Check local and remote-tracking commit IDs and compare their graph to see how far the local checkout lags. The principle behind this distinction is that Branch references can differ between distributed repositories until explicit network synchronization occurs. If the check supports this diagnosis, the next controlled response is to fetch the current remote state and intentionally update the appropriate local branch before relying on it for new work.
Incorrect Answers
A:Inspect the faulty commit's diff and ancestry before preparing and reviewing its inverse patch. The principle behind this distinction is that Branch references can differ between distributed repositories until explicit network synchronization occurs. It does not isolate the local and remote branches have different state issue described.
B:Review git status and the exact file diff to avoid discarding unrelated work during the restore. The principle behind this distinction is that Branch references can differ between distributed repositories until explicit network synchronization occurs. It does not isolate the local and remote branches have different state issue described.
C:Examine git remote -v and the branch's upstream tracking configuration to establish destination and expected permissions. The principle behind this distinction is that Branch references can differ between distributed repositories until explicit network synchronization occurs. It does not isolate the local and remote branches have different state issue described.