Microsoft GH-900 Practice Test 33
Question 320
A contributor receives this specific collaboration request: A contributor has a completed feature branch but a maintainer needs line comments, checks and approvals before merge. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
- 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.
- Open a pull request from the intended feature branch to the correct base branch with a clear change summary.
Explanation
Correct Answer
D:Open a pull request from the intended feature branch to the correct base branch with a clear change summary. Pull requests provide a collaborative proposal and review surface for changes between branches or repositories. The first useful confirmation step is to compare head/base branch selection and changed-file diff, then inspect requested reviews and checks. A contributor has a completed feature branch but a maintainer needs line comments, checks and approvals before merge.
Incorrect Answers
A:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. Pull requests provide a collaborative proposal and review surface for changes between branches or repositories. Applying it first would leave pull requests propose reviewable changes unresolved.
B:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. Pull requests provide a collaborative proposal and review surface for changes between branches or repositories. Applying it first would leave pull requests propose reviewable changes unresolved.
C:Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately. Pull requests provide a collaborative proposal and review surface for changes between branches or repositories. Applying it first would leave pull requests propose reviewable changes unresolved.
Question 321
A repository owner is standardizing processes after this earlier failure: A contributor has a completed feature branch but a maintainer needs line comments, checks and approvals before merge. Which maintenance policy is most appropriate for this specific risk? Select ONE answer.
- 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.
- Revisit issue templates whenever common clarification requests reveal missing intake fields.
Explanation
Correct Answer
A:Require concise pull request descriptions, focused diffs and successful required checks where applicable. Check periodically that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. The reason it is relevant is that Pull requests provide a collaborative proposal and review surface for changes between branches or repositories.
Incorrect Answers
B:Set team guidance for moving a draft to ready when technical and review prerequisites are met. Check periodically that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. This would not prevent the recurrence of the pull requests propose reviewable changes failure.
C:Encourage issue references in pull request descriptions and verify issue closure during release review. Check periodically that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. This would not prevent the recurrence of the pull requests propose reviewable changes failure.
D:Revisit issue templates whenever common clarification requests reveal missing intake fields. Check periodically that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. This would not prevent the recurrence of the pull requests propose reviewable changes failure.
Question 322
A GitHub maintainer must reject an unsound recommendation after this report: A contributor has a completed feature branch but a maintainer needs line comments, checks and approvals before merge. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks.
- Merge a folder of pasted code directly into production and assume the pull request review record will appear afterward.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
Explanation
Correct Answer
B:Merge a folder of pasted code directly into production and assume the pull request review record will appear afterward. Objective closure would show that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. The unsafe proposal is to merge a folder of pasted code directly into production and assume the pull request review record will appear afterward. A contributor has a completed feature branch but a maintainer needs line comments, checks and approvals before merge.
Incorrect Answers
A:Use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. Objective closure would show that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. The direct risk in the case is pull requests propose reviewable changes, not this other concern.
C:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. Objective closure would show that reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. The direct risk in the case is pull requests propose reviewable changes, 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 reviewers can discuss exact changed lines, see validation status and approve or request changes before merging. The direct risk in the case is pull requests propose reviewable changes, not this other concern.
Question 323
During a repository review, the maintainer finds this condition: A developer wants early feedback on a large refactor without signaling that the branch is ready to merge. Which practical next step fits this specific repository situation? Select ONE answer.
- 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.
- Mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
- Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow.
Explanation
Correct Answer
C:Mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. The first useful confirmation step is to inspect the pull request's draft state, checklist and check results before attempting formal approval or merge.
Incorrect Answers
A:Add an appropriate pull request template with summary, testing evidence and relevant impact prompts. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. The case instead calls for the following: mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
B:Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. The case instead calls for the following: mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
D:Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. The case instead calls for the following: mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
Question 324
A repository maintainer begins diagnosis of the following report: A developer wants early feedback on a large refactor without signaling that the branch is ready to merge. What should the team verify first to isolate the problem correctly? 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 pull request's draft state, checklist and check results before attempting formal approval or merge.
Explanation
Correct Answer
D:Inspect the pull request's draft state, checklist and check results before attempting formal approval or merge. Verify the improvement by checking that collaborators can provide preliminary comments without treating unfinished work as approved for integration. If the check supports this diagnosis, the next controlled response is to mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
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 collaborators can provide preliminary comments without treating unfinished work as approved for integration. It does not isolate the draft pull requests signal unfinished work 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 collaborators can provide preliminary comments without treating unfinished work as approved for integration. It does not isolate the draft pull requests signal unfinished work issue described.
C:Inspect Pages repository settings, deployed source branch or workflow and resulting public site URL. Verify the improvement by checking that collaborators can provide preliminary comments without treating unfinished work as approved for integration. It does not isolate the draft pull requests signal unfinished work issue described.
Question 325
An onboarding lead requires measurable closure for this problem: A developer wants early feedback on a large refactor without signaling that the branch is ready to merge. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- Collaborators can provide preliminary comments without treating unfinished work as approved for integration.
- 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.
- The work item shows a specific responsible participant and an agreed next action without duplicate parallel effort.
Explanation
Correct Answer
A:Collaborators can provide preliminary comments without treating unfinished work as approved for integration. An independent review should first inspect the pull request's draft state, checklist and check results before attempting formal approval or merge. Closing an issue without this result would not prove technical resolution because Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff.
Incorrect Answers
B:New bug reports consistently include useful environment and reproduction data while enhancements have separate requirements. An independent review should first inspect the pull request's draft state, checklist and check results before attempting formal approval or merge. This validates an adjacent control rather than the outcome of draft pull requests signal unfinished work.
C:Each new proposal prompts authors for the change purpose, test observations and relevant issue references. An independent review should first inspect the pull request's draft state, checklist and check results before attempting formal approval or merge. This validates an adjacent control rather than the outcome of draft pull requests signal unfinished work.
D:The work item shows a specific responsible participant and an agreed next action without duplicate parallel effort. An independent review should first inspect the pull request's draft state, checklist and check results before attempting formal approval or merge. This validates an adjacent control rather than the outcome of draft pull requests signal unfinished work.
Question 326
A developer evaluates unsafe proposals following this situation: A developer wants early feedback on a large refactor without signaling that the branch is ready to merge. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
- Claim that a draft pull request means the code is merged and all branch protections have been satisfied.
- Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately.
- Organize supplementary project documentation in the repository wiki when that surface suits maintainers' needs.
Explanation
Correct Answer
B:Claim that a draft pull request means the code is merged and all branch protections have been satisfied. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. The safer GitHub workflow is to mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review after checking whether the team can inspect the pull request's draft state, checklist and check results before attempting formal approval or merge.
Incorrect Answers
A:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. The reported issue instead calls for rejecting claim that a draft pull request means the code is merged and all branch protections have been satisfied.
C:Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. The reported issue instead calls for rejecting claim that a draft pull request means the code is merged and all branch protections have been satisfied.
D:Organize supplementary project documentation in the repository wiki when that surface suits maintainers' needs. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. The reported issue instead calls for rejecting claim that a draft pull request means the code is merged and all branch protections have been satisfied.
Question 327
A project owner is investigating an operational GitHub workflow issue: A security review team keeps receiving fully ready pull requests that are actually still works in progress. Which practical next step fits this specific repository situation? Select ONE answer.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
- Mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
- Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately.
Explanation
Correct Answer
C:Mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. The first useful confirmation step is to inspect the pull request's draft state, checklist and check results before attempting formal approval or merge. A security review team keeps receiving fully ready pull requests that are actually still works in progress.
Incorrect Answers
A:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. Applying it first would leave draft pull requests signal unfinished work unresolved.
B:Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. Applying it first would leave draft pull requests signal unfinished work unresolved.
D:Create a GitHub Gist for the small code or text snippet and control its visibility and shared secrets appropriately. Draft pull requests communicate review readiness separately from the existence of a branch or proposed diff. Applying it first would leave draft pull requests signal unfinished work unresolved.
Question 328
A contributor asks how to keep this workflow problem from happening again: A security review team keeps receiving fully ready pull requests that are actually still works in progress. Which ongoing practice most reliably prevents this same GitHub issue from recurring? Select ONE answer.
- Refresh the template with evolving quality gates without making unnecessary unhelpful form fields mandatory.
- Review unassigned issues during triage and update ownership when contributors are unavailable.
- Review label naming consistency and remove confusing or unused triage categories periodically.
- Set team guidance for moving a draft to ready when technical and review prerequisites are met.
Explanation
Correct Answer
D:Set team guidance for moving a draft to ready when technical and review prerequisites are met. Check periodically that collaborators can provide preliminary comments without treating unfinished work as approved for integration. It complements the initial correction to mark the proposed pull request as draft until its author completes required work and explicitly marks it ready for review.
Incorrect Answers
A:Refresh the template with evolving quality gates without making unnecessary unhelpful form fields mandatory. Check periodically that collaborators can provide preliminary comments without treating unfinished work as approved for integration. This would not prevent the recurrence of the draft pull requests signal unfinished work failure.
B:Review unassigned issues during triage and update ownership when contributors are unavailable. Check periodically that collaborators can provide preliminary comments without treating unfinished work as approved for integration. This would not prevent the recurrence of the draft pull requests signal unfinished work failure.
C:Review label naming consistency and remove confusing or unused triage categories periodically. Check periodically that collaborators can provide preliminary comments without treating unfinished work as approved for integration. This would not prevent the recurrence of the draft pull requests signal unfinished work failure.
Question 329
During a review, a contributor proposes an emergency bypass for this problem: A security review team keeps receiving fully ready pull requests that are actually still works in progress. What is the least defensible workaround for this project? Select ONE answer.
- Claim that a draft pull request means the code is merged and all branch protections have been satisfied.
- Use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks.
- Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor.
- Filter notifications by reason or conversation and prioritize direct mentions and assigned review requests appropriately.
Explanation
Correct Answer
A:Claim that a draft pull request means the code is merged and all branch protections have been satisfied. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. That suggestion is specifically risky for the case: A security review team keeps receiving fully ready pull requests that are actually still works in progress.
Incorrect Answers
B:Use GitHub Discussions for Q&A and open-ended community conversation and reserve issues for trackable tasks. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. The direct risk in the case is draft pull requests signal unfinished work, not this other concern.
C:Configure repository watch preferences and notification filters for the activity the contributor actually needs to monitor. Objective closure would show that collaborators can provide preliminary comments without treating unfinished work as approved for integration. The direct risk in the case is draft pull requests signal unfinished work, 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 collaborators can provide preliminary comments without treating unfinished work as approved for integration. The direct risk in the case is draft pull requests signal unfinished work, not this other concern.
Question 330
A distributed project team must respond to the following case: A bug fix was merged but its original issue remains open and maintainers do not know the related implementation. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Add an appropriate pull request template with summary, testing evidence and relevant impact prompts.
- Link the proposed fix to its issue using the supported pull request relationship or closing keyword.
- Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action.
- Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow.
Explanation
Correct Answer
B:Link the proposed fix to its issue using the supported pull request relationship or closing keyword. GitHub supports explicit issue-and-pull-request relationships, including closing references whose behavior depends on integration context. The first useful confirmation step is to check the issue and pull request cross-references and the intended target branch before relying on automatic closing behavior.
Incorrect Answers
A:Add an appropriate pull request template with summary, testing evidence and relevant impact prompts. GitHub supports explicit issue-and-pull-request relationships, including closing references whose behavior depends on integration context. The case instead calls for the following: link the proposed fix to its issue using the supported pull request relationship or closing keyword.
C:Assign the appropriate authorized contributor to the issue or pull request and clarify expected next action. GitHub supports explicit issue-and-pull-request relationships, including closing references whose behavior depends on integration context. The case instead calls for the following: link the proposed fix to its issue using the supported pull request relationship or closing keyword.
D:Apply useful labels and filters that distinguish issue type, priority or area for the team's triage workflow. GitHub supports explicit issue-and-pull-request relationships, including closing references whose behavior depends on integration context. The case instead calls for the following: link the proposed fix to its issue using the supported pull request relationship or closing keyword.