Microsoft GH-900 Practice Test 38
Question 370
A contributor asks how to keep this workflow problem from happening again: A project wants a place for announcements and ideas while keeping its issue tracker focused on actionable work. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Require concise pull request descriptions, focused diffs and successful required checks where applicable.
- Document whether questions, bugs and feature proposals belong in Discussions or Issues for the project.
- Set team guidance for moving a draft to ready when technical and review prerequisites are met.
- Encourage issue references in pull request descriptions and verify issue closure during release review.
Explanation
Correct Answer
B:Document whether questions, bugs and feature proposals belong in Discussions or Issues for the project. It complements the initial correction to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. Check periodically that general questions receive a suitable community thread while actionable defects still enter the issue tracker.
Incorrect Answers
A:Require concise pull request descriptions, focused diffs and successful required checks where applicable. It complements the initial correction to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. This would not prevent the recurrence of the discussions support open-ended community questions failure.
C:Set team guidance for moving a draft to ready when technical and review prerequisites are met. It complements the initial correction to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. This would not prevent the recurrence of the discussions support open-ended community questions failure.
D:Encourage issue references in pull request descriptions and verify issue closure during release review. It complements the initial correction to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. This would not prevent the recurrence of the discussions support open-ended community questions failure.
Question 371
During a review, a contributor proposes an emergency bypass for this problem: A project wants a place for announcements and ideas while keeping its issue tracker focused on actionable work. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
- Open a misleading defect issue for every general request and assign engineers to nonexistent bugs.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
Explanation
Correct Answer
C:Open a misleading defect issue for every general request and assign engineers to nonexistent bugs. The safer GitHub workflow is to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks after checking whether the team can inspect the post purpose and whether repository Discussions is enabled before choosing its category. A project wants a place for announcements and ideas while keeping its issue tracker focused on actionable work.
Incorrect Answers
A:Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow. The safer GitHub workflow is to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks after checking whether the team can inspect the post purpose and whether repository Discussions is enabled before choosing its category. The direct risk in the case is discussions support open-ended community questions, not this other concern.
B:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. The safer GitHub workflow is to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks after checking whether the team can inspect the post purpose and whether repository Discussions is enabled before choosing its category. The direct risk in the case is discussions support open-ended community questions, not this other concern.
D:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. The safer GitHub workflow is to use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks after checking whether the team can inspect the post purpose and whether repository Discussions is enabled before choosing its category. The direct risk in the case is discussions support open-ended community questions, not this other concern.
Question 372
A distributed project team must respond to the following case: A maintainer watches a popular project and receives far more GitHub emails than are useful for their assigned work. What is the most defensible technical action for this case? Select ONE answer.
- Configure appropriate repository issue templates or issue forms with the essential context fields for each report type.
- Add an appropriate pull request template with summary, testing evidence and relevant impact prompts.
- Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
Explanation
Correct Answer
D:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. The first useful confirmation step is to inspect notification subscription settings and inbox reason filters to locate the origin of noisy or missing alerts.
Incorrect Answers
A:Configure appropriate repository issue templates or issue forms with the essential context fields for each report type. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. The case instead calls for the following: configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
B:Add an appropriate pull request template with summary, testing evidence and relevant impact prompts. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. The case instead calls for the following: configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
C:Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. The case instead calls for the following: configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
Question 373
Before changing GitHub settings, a project reviewer examines this case: A maintainer watches a popular project and receives far more GitHub emails than are useful for their assigned work. Which focused investigation provides the most useful initial evidence? Select ONE answer.
- Inspect notification subscription settings and inbox reason filters to locate the origin of noisy or missing alerts.
- Inspect the snippet content and visibility before sharing its link, checking it contains no credentials or private customer data.
- Verify that wiki is enabled and compare the documented pages with current code and support procedures.
- Inspect Pages repository settings, deployed source branch or workflow and resulting public site URL.
Explanation
Correct Answer
A:Inspect notification subscription settings and inbox reason filters to locate the origin of noisy or missing alerts. Verify the improvement by checking that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. If the check supports this diagnosis, the next controlled response is to configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
Incorrect Answers
B:Inspect the snippet content and visibility before sharing its link, checking it contains no credentials or private customer data. Verify the improvement by checking that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. It does not isolate the watch settings control notification volume issue described.
C:Verify that wiki is enabled and compare the documented pages with current code and support procedures. Verify the improvement by checking that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. It does not isolate the watch settings control notification volume issue described.
D:Inspect Pages repository settings, deployed source branch or workflow and resulting public site URL. Verify the improvement by checking that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. It does not isolate the watch settings control notification volume issue described.
Question 374
Following a proposed correction, a reviewer revisits the following case: A maintainer watches a popular project and receives far more GitHub emails than are useful for their assigned work. How should the team demonstrate that the approved change worked? Select ONE answer.
- Reviewers can navigate from the issue to its fixing change and the issue status reflects the actual merged resolution.
- The contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise.
- New bug reports consistently include useful environment and reproduction data while enhancements have separate requirements.
- Each new proposal prompts authors for the change purpose, test observations and relevant issue references.
Explanation
Correct Answer
B:The contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. Closing an issue without this result would not prove technical resolution because GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. An independent review should first inspect notification subscription settings and inbox reason filters to locate the origin of noisy or missing alerts.
Incorrect Answers
A:Reviewers can navigate from the issue to its fixing change and the issue status reflects the actual merged resolution. Closing an issue without this result would not prove technical resolution because GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. This validates an adjacent control rather than the outcome of watch settings control notification volume.
C:New bug reports consistently include useful environment and reproduction data while enhancements have separate requirements. Closing an issue without this result would not prove technical resolution because GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. This validates an adjacent control rather than the outcome of watch settings control notification volume.
D:Each new proposal prompts authors for the change purpose, test observations and relevant issue references. Closing an issue without this result would not prove technical resolution because GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. This validates an adjacent control rather than the outcome of watch settings control notification volume.
Question 375
A pull request discussion contains questionable workarounds for this report: A maintainer watches a popular project and receives far more GitHub emails than are useful for their assigned work. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
- Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately.
- Disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox.
- Organize supplementary project documentation in the repository wiki when that surface suits maintainers' needs.
Explanation
Correct Answer
C:Disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The unsafe proposal is to disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox.
Incorrect Answers
A:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The reported issue instead calls for rejecting disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox.
B:Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The reported issue instead calls for rejecting disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox.
D:Organize supplementary project documentation in the repository wiki when that surface suits maintainers' needs. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The reported issue instead calls for rejecting disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox.
Question 376
A GitHub platform user encounters this scenario: A contributor stops seeing requested review notifications after indiscriminately disabling all repository activity subscriptions. What is the most defensible technical action for this case? Select ONE answer.
- Organize supplementary project documentation in the repository wiki when that surface suits maintainers' needs.
- Configure a supported GitHub Pages deployment source and publish reviewed static site content with the intended visibility.
- Open an actionable GitHub issue containing reproducible behavior, expected outcome, context and an appropriate assignee.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
Explanation
Correct Answer
D:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. The first useful confirmation step is to inspect notification subscription settings and inbox reason filters to locate the origin of noisy or missing alerts. A contributor stops seeing requested review notifications after indiscriminately disabling all repository activity subscriptions.
Incorrect Answers
A:Organize supplementary project documentation in the repository wiki when that surface suits maintainers' needs. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. Applying it first would leave watch settings control notification volume unresolved.
B:Configure a supported GitHub Pages deployment source and publish reviewed static site content with the intended visibility. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. Applying it first would leave watch settings control notification volume unresolved.
C:Open an actionable GitHub issue containing reproducible behavior, expected outcome, context and an appropriate assignee. GitHub notifications depend on watch choices, participation, mentions and inbox filtering, not solely on starring repositories. Applying it first would leave watch settings control notification volume unresolved.
Question 377
A project retrospective considers the long-term control for this situation: A contributor stops seeing requested review notifications after indiscriminately disabling all repository activity subscriptions. What operational safeguard should remain after the immediate fix? Select ONE answer.
- Review notification preferences periodically and keep responsibility-related notifications enabled.
- Require concise pull request descriptions, focused diffs and successful required checks where applicable.
- Set team guidance for moving a draft to ready when technical and review prerequisites are met.
- Encourage issue references in pull request descriptions and verify issue closure during release review.
Explanation
Correct Answer
A:Review notification preferences periodically and keep responsibility-related notifications enabled. Check periodically that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise.
Incorrect Answers
B:Require concise pull request descriptions, focused diffs and successful required checks where applicable. Check periodically that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. This would not prevent the recurrence of the watch settings control notification volume failure.
C:Set team guidance for moving a draft to ready when technical and review prerequisites are met. Check periodically that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. This would not prevent the recurrence of the watch settings control notification volume failure.
D:Encourage issue references in pull request descriptions and verify issue closure during release review. Check periodically that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. This would not prevent the recurrence of the watch settings control notification volume failure.
Question 378
An organization wants to identify the least appropriate response to this event: A contributor stops seeing requested review notifications after indiscriminately disabling all repository activity subscriptions. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.
- Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow.
- Disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox.
- Use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
Explanation
Correct Answer
B:Disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The unsafe proposal is to disable all GitHub notifications permanently and assume required code review requests will still reach the same inbox. A contributor stops seeing requested review notifications after indiscriminately disabling all repository activity subscriptions.
Incorrect Answers
A:Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The direct risk in the case is watch settings control notification volume, not this other concern.
C:Use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The direct risk in the case is watch settings control notification volume, not this other concern.
D:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. Objective closure would show that the contributor receives relevant mentions or subscribed activity without unnecessary repository-wide noise. The direct risk in the case is watch settings control notification volume, not this other concern.
Question 379
A contributor receives this specific collaboration request: A contributor sees a crowded notifications inbox but cannot distinguish a direct mention from a generic repository update. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.
- Configure appropriate repository issue templates or issue forms with the essential context fields for each report type.
- Add an appropriate pull request template with summary, testing evidence and relevant impact prompts.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
- Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action.
Explanation
Correct Answer
C:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. Notification metadata and mentions help users triage collaboration activity while the underlying issue or pull request retains context. The first useful confirmation step is to inspect the notification reason, originating repository and thread context before choosing whether to respond.
Incorrect Answers
A:Configure appropriate repository issue templates or issue forms with the essential context fields for each report type. Notification metadata and mentions help users triage collaboration activity while the underlying issue or pull request retains context. The case instead calls for the following: filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
B:Add an appropriate pull request template with summary, testing evidence and relevant impact prompts. Notification metadata and mentions help users triage collaboration activity while the underlying issue or pull request retains context. The case instead calls for the following: filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
D:Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action. Notification metadata and mentions help users triage collaboration activity while the underlying issue or pull request retains context. The case instead calls for the following: filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
Question 380
An engineer needs to distinguish root causes for the following workflow problem: A contributor sees a crowded notifications inbox but cannot distinguish a direct mention from a generic repository update. Which diagnostic review best explains this exact reported behavior? Select ONE answer.
- Inspect the snippet content and visibility before sharing its link, checking it contains no credentials or private customer data.
- Verify that wiki is enabled and compare the documented pages with current code and support procedures.
- Inspect Pages repository settings, deployed source branch or workflow and resulting public site URL.
- Inspect the notification reason, originating repository and thread context before choosing whether to respond.
Explanation
Correct Answer
D:Inspect the notification reason, originating repository and thread context before choosing whether to respond. Verify the improvement by checking that the reviewer can identify which threads require an action and leaves low-priority subscriptions for later reading. If the check supports this diagnosis, the next controlled response is to filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
Incorrect Answers
A:Inspect the snippet content and visibility before sharing its link, checking it contains no credentials or private customer data. Verify the improvement by checking that the reviewer can identify which threads require an action and leaves low-priority subscriptions for later reading. It does not isolate the mention and notification reason clarify action issue described.
B:Verify that wiki is enabled and compare the documented pages with current code and support procedures. Verify the improvement by checking that the reviewer can identify which threads require an action and leaves low-priority subscriptions for later reading. It does not isolate the mention and notification reason clarify action issue described.
C:Inspect Pages repository settings, deployed source branch or workflow and resulting public site URL. Verify the improvement by checking that the reviewer can identify which threads require an action and leaves low-priority subscriptions for later reading. It does not isolate the mention and notification reason clarify action issue described.