Microsoft GH-900 Practice Test 23
Question 220
A project sponsor requires a clear acceptance check for this scenario: A public example project is visible on GitHub but an external engineer assumes that public visibility grants unrestricted commercial reuse. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- Reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure.
- The new starter repository includes approved scaffolding and can evolve independently from the template source.
- Newly opened pull requests target the correct primary branch and repository guidance references the updated name.
- Visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it.
Explanation
Correct Answer
D:Visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. Closing an issue without this result would not prove technical resolution because Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. An independent review should first check whether the root license file exists and matches the maintainers' intended reuse and distribution terms.
Incorrect Answers
A:Reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure. Closing an issue without this result would not prove technical resolution because Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. This validates an adjacent control rather than the outcome of license communicates reuse permissions.
B:The new starter repository includes approved scaffolding and can evolve independently from the template source. Closing an issue without this result would not prove technical resolution because Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. This validates an adjacent control rather than the outcome of license communicates reuse permissions.
C:Newly opened pull requests target the correct primary branch and repository guidance references the updated name. Closing an issue without this result would not prove technical resolution because Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. This validates an adjacent control rather than the outcome of license communicates reuse permissions.
Question 221
A GitHub maintainer must reject an unsound recommendation after this report: A public example project is visible on GitHub but an external engineer assumes that public visibility grants unrestricted commercial reuse. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Claim everything publicly viewable on GitHub is automatically available under a permissive open-source license.
- Make a deliberate branch-based file edit or move, review the diff and commit the intended content change.
- Check the feature's current availability, account eligibility and documented preview limitations before relying on it.
- Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events.
Explanation
Correct Answer
A:Claim everything publicly viewable on GitHub is automatically available under a permissive open-source license. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The safer GitHub workflow is to add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license after checking whether the team can check whether the root license file exists and matches the maintainers' intended reuse and distribution terms.
Incorrect Answers
B:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The reported issue instead calls for rejecting claim everything publicly viewable on GitHub is automatically available under a permissive open-source license.
C:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The reported issue instead calls for rejecting claim everything publicly viewable on GitHub is automatically available under a permissive open-source license.
D:Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The reported issue instead calls for rejecting claim everything publicly viewable on GitHub is automatically available under a permissive open-source license.
Question 222
During a repository review, the maintainer finds this condition: An open-source contributor cannot determine whether a script can be redistributed because its source repository has no license statement. Which practical next step fits this specific repository situation? Select ONE answer.
- Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships.
- Add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license.
- Make a deliberate branch-based file edit or move, review the diff and commit the intended content change.
- Check the feature's current availability, account eligibility and documented preview limitations before relying on it.
Explanation
Correct Answer
B:Add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license. Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. The first useful confirmation step is to check whether the root license file exists and matches the maintainers' intended reuse and distribution terms. An open-source contributor cannot determine whether a script can be redistributed because its source repository has no license statement.
Incorrect Answers
A:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. Applying it first would leave license communicates reuse permissions unresolved.
C:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. Applying it first would leave license communicates reuse permissions unresolved.
D:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. Public access makes source readable, while an explicit license determines the permissions others receive to use and redistribute it. Applying it first would leave license communicates reuse permissions unresolved.
Question 223
A GitHub team reviews how to prevent recurrence after this case: An open-source contributor cannot determine whether a script can be redistributed because its source repository has no license statement. Which ongoing practice most reliably prevents this same GitHub issue from recurring? Select ONE answer.
- Update the contribution guide when branch policies, CI checks or code-style requirements change.
- Maintain CODEOWNERS entries when teams or directories change and protect the owner file itself.
- Require a license decision during public repository creation and review compliance when accepting third-party code.
- Review security-contact ownership and support windows as releases and responsible staff change.
Explanation
Correct Answer
C:Require a license decision during public repository creation and review compliance when accepting third-party code. It complements the initial correction to add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license. Check periodically that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it.
Incorrect Answers
A:Update the contribution guide when branch policies, CI checks or code-style requirements change. It complements the initial correction to add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license. This would not prevent the recurrence of the license communicates reuse permissions failure.
B:Maintain CODEOWNERS entries when teams or directories change and protect the owner file itself. It complements the initial correction to add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license. This would not prevent the recurrence of the license communicates reuse permissions failure.
D:Review security-contact ownership and support windows as releases and responsible staff change. It complements the initial correction to add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license. This would not prevent the recurrence of the license communicates reuse permissions failure.
Question 224
A pull request discussion contains questionable workarounds for this report: An open-source contributor cannot determine whether a script can be redistributed because its source repository has no license statement. What is the least defensible workaround for this project? Select ONE answer.
- Use relevant repository Insights and traffic metrics while explaining their different definitions and limits.
- Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships.
- Make a deliberate branch-based file edit or move, review the diff and commit the intended content change.
- Claim everything publicly viewable on GitHub is automatically available under a permissive open-source license.
Explanation
Correct Answer
D:Claim everything publicly viewable on GitHub is automatically available under a permissive open-source license. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The safer GitHub workflow is to add an appropriate approved LICENSE file and explain that repository visibility alone is not a software-use license after checking whether the team can check whether the root license file exists and matches the maintainers' intended reuse and distribution terms. An open-source contributor cannot determine whether a script can be redistributed because its source repository has no license statement.
Incorrect Answers
A:Use relevant repository Insights and traffic metrics while explaining their different definitions and limits. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The direct risk in the case is license communicates reuse permissions, not this other concern.
B:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The direct risk in the case is license communicates reuse permissions, not this other concern.
C:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. Objective closure would show that visitors can locate explicit licensing conditions and distinguish viewing source from receiving permission to reuse it. The direct risk in the case is license communicates reuse permissions, not this other concern.
Question 225
A GitHub platform user encounters this scenario: A volunteer project receives patches through unstructured messages because there are no instructions for branches, tests or review. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
- Use a repository template to create a new project with the intended starter files and separately managed history.
- Set the intended default branch and update automation, protection and contributor references that depend on its name.
- Archive the obsolete repository after documenting its replacement and ongoing support expectations.
Explanation
Correct Answer
A:Add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. The first useful confirmation step is to inspect the contribution guide and compare its commands and workflow with the actual repository checks.
Incorrect Answers
B:Use a repository template to create a new project with the intended starter files and separately managed history. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. The case instead calls for the following: add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
C:Set the intended default branch and update automation, protection and contributor references that depend on its name. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. The case instead calls for the following: add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
D:Archive the obsolete repository after documenting its replacement and ongoing support expectations. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. The case instead calls for the following: add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
Question 226
A developer starts an investigation after the following user report: A volunteer project receives patches through unstructured messages because there are no instructions for branches, tests or review. Before changing anything, which detail should a reviewer inspect? Select ONE answer.
- Inspect repository feature settings and official release or preview notes for enablement and support status.
- Inspect the contribution guide and compare its commands and workflow with the actual repository checks.
- Check the repository star status and separate notification subscription settings for the affected account.
- Check merge status, open pull request references and current contribution instructions before deleting or revising items.
Explanation
Correct Answer
B:Inspect the contribution guide and compare its commands and workflow with the actual repository checks. Verify the improvement by checking that a newcomer can follow a documented process and submit a pull request with the required verification evidence. If the check supports this diagnosis, the next controlled response is to add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
Incorrect Answers
A:Inspect repository feature settings and official release or preview notes for enablement and support status. Verify the improvement by checking that a newcomer can follow a documented process and submit a pull request with the required verification evidence. It does not isolate the contributing specifies contribution process issue described.
C:Check the repository star status and separate notification subscription settings for the affected account. Verify the improvement by checking that a newcomer can follow a documented process and submit a pull request with the required verification evidence. It does not isolate the contributing specifies contribution process issue described.
D:Check merge status, open pull request references and current contribution instructions before deleting or revising items. Verify the improvement by checking that a newcomer can follow a documented process and submit a pull request with the required verification evidence. It does not isolate the contributing specifies contribution process issue described.
Question 227
A GitHub contributor needs to validate a change affecting this incident: A volunteer project receives patches through unstructured messages because there are no instructions for branches, tests or review. Which observable result would best prove that the issue was resolved? Select ONE answer.
- Reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure.
- The new starter repository includes approved scaffolding and can evolve independently from the template source.
- A newcomer can follow a documented process and submit a pull request with the required verification evidence.
- Newly opened pull requests target the correct primary branch and repository guidance references the updated name.
Explanation
Correct Answer
C:A newcomer can follow a documented process and submit a pull request with the required verification evidence. Closing an issue without this result would not prove technical resolution because A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. An independent review should first inspect the contribution guide and compare its commands and workflow with the actual repository checks.
Incorrect Answers
A:Reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure. Closing an issue without this result would not prove technical resolution because A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. This validates an adjacent control rather than the outcome of contributing specifies contribution process.
B:The new starter repository includes approved scaffolding and can evolve independently from the template source. Closing an issue without this result would not prove technical resolution because A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. This validates an adjacent control rather than the outcome of contributing specifies contribution process.
D:Newly opened pull requests target the correct primary branch and repository guidance references the updated name. Closing an issue without this result would not prove technical resolution because A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. This validates an adjacent control rather than the outcome of contributing specifies contribution process.
Question 228
During a review, a contributor proposes an emergency bypass for this problem: A volunteer project receives patches through unstructured messages because there are no instructions for branches, tests or review. What is the least defensible workaround for this project? Select ONE answer.
- Make a deliberate branch-based file edit or move, review the diff and commit the intended content change.
- Check the feature's current availability, account eligibility and documented preview limitations before relying on it.
- Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events.
- Expect every contributor to infer undocumented acceptance rules from old closed pull requests.
Explanation
Correct Answer
D:Expect every contributor to infer undocumented acceptance rules from old closed pull requests. Objective closure would show that a newcomer can follow a documented process and submit a pull request with the required verification evidence. That suggestion is specifically risky for the case: A volunteer project receives patches through unstructured messages because there are no instructions for branches, tests or review.
Incorrect Answers
A:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. Objective closure would show that a newcomer can follow a documented process and submit a pull request with the required verification evidence. The reported issue instead calls for rejecting expect every contributor to infer undocumented acceptance rules from old closed pull requests.
B:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. Objective closure would show that a newcomer can follow a documented process and submit a pull request with the required verification evidence. The reported issue instead calls for rejecting expect every contributor to infer undocumented acceptance rules from old closed pull requests.
C:Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events. Objective closure would show that a newcomer can follow a documented process and submit a pull request with the required verification evidence. The reported issue instead calls for rejecting expect every contributor to infer undocumented acceptance rules from old closed pull requests.
Question 229
A distributed project team must respond to the following case: A community repository repeatedly rejects well-meant contributions that omit the required linting and pull request checks. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
- Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships.
- Make a deliberate branch-based file edit or move, review the diff and commit the intended content change.
- Check the feature's current availability, account eligibility and documented preview limitations before relying on it.
Explanation
Correct Answer
A:Add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. The first useful confirmation step is to inspect the contribution guide and compare its commands and workflow with the actual repository checks. A community repository repeatedly rejects well-meant contributions that omit the required linting and pull request checks.
Incorrect Answers
B:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. Applying it first would leave contributing specifies contribution process unresolved.
C:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. Applying it first would leave contributing specifies contribution process unresolved.
D:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. A CONTRIBUTING guide makes project-specific participation requirements discoverable before changes are submitted. Applying it first would leave contributing specifies contribution process unresolved.
Question 230
An engineering manager is defining a durable safeguard for this problem: A community repository repeatedly rejects well-meant contributions that omit the required linting and pull request checks. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Keep templates maintained and periodically refresh approved project scaffolding and guidance.
- Update the contribution guide when branch policies, CI checks or code-style requirements change.
- Include branch names in migration checklists when changing a repository's default line.
- Keep an archive notice that points visitors to the actively maintained replacement or successor project.
Explanation
Correct Answer
B:Update the contribution guide when branch policies, CI checks or code-style requirements change. Check periodically that a newcomer can follow a documented process and submit a pull request with the required verification evidence. It complements the initial correction to add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations.
Incorrect Answers
A:Keep templates maintained and periodically refresh approved project scaffolding and guidance. Check periodically that a newcomer can follow a documented process and submit a pull request with the required verification evidence. This would not prevent the recurrence of the contributing specifies contribution process failure.
C:Include branch names in migration checklists when changing a repository's default line. Check periodically that a newcomer can follow a documented process and submit a pull request with the required verification evidence. This would not prevent the recurrence of the contributing specifies contribution process failure.
D:Keep an archive notice that points visitors to the actively maintained replacement or successor project. Check periodically that a newcomer can follow a documented process and submit a pull request with the required verification evidence. This would not prevent the recurrence of the contributing specifies contribution process failure.