Microsoft GH-900 Practice Test 24
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.
Question 231
An impatient project team suggests risky shortcuts for this case: A community repository repeatedly rejects well-meant contributions that omit the required linting and pull request checks. Which suggested shortcut should be REJECTED in this situation? 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.
- Expect every contributor to infer undocumented acceptance rules from old closed pull requests.
- Make a deliberate branch-based file edit or move, review the diff and commit the intended content change.
Explanation
Correct Answer
C: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. The safer GitHub workflow is to add CONTRIBUTING.md with the team's issue, branch, test, review and pull request expectations after checking whether the team can inspect the contribution guide and compare its commands and workflow with the actual repository checks.
Incorrect Answers
A:Use relevant repository Insights and traffic metrics while explaining their different definitions and limits. Objective closure would show that a newcomer can follow a documented process and submit a pull request with the required verification evidence. The direct risk in the case is contributing specifies contribution process, 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 a newcomer can follow a documented process and submit a pull request with the required verification evidence. The direct risk in the case is contributing specifies contribution process, not this other concern.
D: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 direct risk in the case is contributing specifies contribution process, not this other concern.
Question 232
A GitHub contributor is asked to resolve this report: A security-sensitive configuration folder is repeatedly changed without the infrastructure maintainers noticing the pull requests. What is the most defensible technical action for this case? Select ONE answer.
- 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.
- Define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
Explanation
Correct Answer
D:Define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. The first useful confirmation step is to inspect the CODEOWNERS path placement, pattern precedence and branch protection or ruleset review requirements.
Incorrect Answers
A:Use a repository template to create a new project with the intended starter files and separately managed history. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. The case instead calls for the following: define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
B:Set the intended default branch and update automation, protection and contributor references that depend on its name. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. The case instead calls for the following: define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
C:Archive the obsolete repository after documenting its replacement and ongoing support expectations. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. The case instead calls for the following: define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
Question 233
An internal auditor needs the first meaningful check for this situation: A security-sensitive configuration folder is repeatedly changed without the infrastructure maintainers noticing the pull requests. Which focused investigation provides the most useful initial evidence? Select ONE answer.
- Inspect the CODEOWNERS path placement, pattern precedence and branch protection or ruleset review requirements.
- Inspect repository feature settings and official release or preview notes for enablement and support status.
- 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
A:Inspect the CODEOWNERS path placement, pattern precedence and branch protection or ruleset review requirements. Verify the improvement by checking that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. If the check supports this diagnosis, the next controlled response is to define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
Incorrect Answers
B:Inspect repository feature settings and official release or preview notes for enablement and support status. Verify the improvement by checking that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. It does not isolate the codeowners routes reviews issue described.
C:Check the repository star status and separate notification subscription settings for the affected account. Verify the improvement by checking that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. It does not isolate the codeowners routes reviews 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 pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. It does not isolate the codeowners routes reviews issue described.
Question 234
A change-control team asks what result would establish real resolution: A security-sensitive configuration folder is repeatedly changed without the infrastructure maintainers noticing the pull requests. How should the team demonstrate that the approved change worked? Select ONE answer.
- Reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure.
- Pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval.
- 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.
Explanation
Correct Answer
B:Pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. Closing an issue without this result would not prove technical resolution because CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. An independent review should first inspect the CODEOWNERS path placement, pattern precedence and branch protection or ruleset review requirements.
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 CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. This validates an adjacent control rather than the outcome of codeowners routes reviews.
C: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 CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. This validates an adjacent control rather than the outcome of codeowners routes reviews.
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 CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. This validates an adjacent control rather than the outcome of codeowners routes reviews.
Question 235
An organization wants to identify the least appropriate response to this event: A security-sensitive configuration folder is repeatedly changed without the infrastructure maintainers noticing the pull requests. Which suggested shortcut should be REJECTED in this situation? 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.
- Add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths.
- Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events.
Explanation
Correct Answer
C:Add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The unsafe proposal is to add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths.
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 pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The reported issue instead calls for rejecting add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths.
B:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The reported issue instead calls for rejecting add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths.
D:Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The reported issue instead calls for rejecting add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths.
Question 236
A contributor receives this specific collaboration request: A repository needs designated maintainers for documentation and deployment files but reviewers are assigned arbitrarily. What is the most defensible technical action for this case? Select ONE answer.
- 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.
- Define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
Explanation
Correct Answer
D:Define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. The first useful confirmation step is to inspect the CODEOWNERS path placement, pattern precedence and branch protection or ruleset review requirements. A repository needs designated maintainers for documentation and deployment files but reviewers are assigned arbitrarily.
Incorrect Answers
A:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. Applying it first would leave codeowners routes reviews unresolved.
B:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. Applying it first would leave codeowners routes reviews unresolved.
C:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. CODEOWNERS maps repository file patterns to designated owners; enforcement requires the relevant review protection setting. Applying it first would leave codeowners routes reviews unresolved.
Question 237
A repository owner is standardizing processes after this earlier failure: A repository needs designated maintainers for documentation and deployment files but reviewers are assigned arbitrarily. What operational safeguard should remain after the immediate fix? Select ONE answer.
- Maintain CODEOWNERS entries when teams or directories change and protect the owner file itself.
- Keep templates maintained and periodically refresh approved project scaffolding and guidance.
- 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
A:Maintain CODEOWNERS entries when teams or directories change and protect the owner file itself. Check periodically that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. It complements the initial correction to define appropriate path patterns and maintainers in a CODEOWNERS file and enforce code-owner review where required.
Incorrect Answers
B:Keep templates maintained and periodically refresh approved project scaffolding and guidance. Check periodically that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. This would not prevent the recurrence of the codeowners routes reviews failure.
C:Include branch names in migration checklists when changing a repository's default line. Check periodically that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. This would not prevent the recurrence of the codeowners routes reviews failure.
D:Keep an archive notice that points visitors to the actively maintained replacement or successor project. Check periodically that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. This would not prevent the recurrence of the codeowners routes reviews failure.
Question 238
A GitHub maintainer must reject an unsound recommendation after this report: A repository needs designated maintainers for documentation and deployment files but reviewers are assigned arbitrarily. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.
- Use relevant repository Insights and traffic metrics while explaining their different definitions and limits.
- Add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths.
- 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.
Explanation
Correct Answer
B:Add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The unsafe proposal is to add arbitrary owner text to the README and assume it automatically enforces review approval for protected paths. A repository needs designated maintainers for documentation and deployment files but reviewers are assigned arbitrarily.
Incorrect Answers
A:Use relevant repository Insights and traffic metrics while explaining their different definitions and limits. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The direct risk in the case is codeowners routes reviews, not this other concern.
C:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The direct risk in the case is codeowners routes reviews, not this other concern.
D:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. Objective closure would show that pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval. The direct risk in the case is codeowners routes reviews, not this other concern.
Question 239
During a repository review, the maintainer finds this condition: A researcher discovers a flaw in a public library but opens a detailed public issue containing the exploit steps. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.
- 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.
- Publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel.
- Archive the obsolete repository after documenting its replacement and ongoing support expectations.
Explanation
Correct Answer
C:Publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel. Repository security policy files help contributors choose a responsible disclosure process distinct from general issue tracking. The first useful confirmation step is to find the repository's security policy and inspect whether it provides a valid nonpublic reporting procedure.
Incorrect Answers
A:Use a repository template to create a new project with the intended starter files and separately managed history. Repository security policy files help contributors choose a responsible disclosure process distinct from general issue tracking. The case instead calls for the following: publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel.
B:Set the intended default branch and update automation, protection and contributor references that depend on its name. Repository security policy files help contributors choose a responsible disclosure process distinct from general issue tracking. The case instead calls for the following: publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel.
D:Archive the obsolete repository after documenting its replacement and ongoing support expectations. Repository security policy files help contributors choose a responsible disclosure process distinct from general issue tracking. The case instead calls for the following: publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel.
Question 240
A repository maintainer begins diagnosis of the following report: A researcher discovers a flaw in a public library but opens a detailed public issue containing the exploit steps. Which diagnostic review best explains this exact reported behavior? Select ONE answer.
- Inspect repository feature settings and official release or preview notes for enablement and support status.
- 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.
- Find the repository's security policy and inspect whether it provides a valid nonpublic reporting procedure.
Explanation
Correct Answer
D:Find the repository's security policy and inspect whether it provides a valid nonpublic reporting procedure. Verify the improvement by checking that reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure. If the check supports this diagnosis, the next controlled response is to publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel.
Incorrect Answers
A:Inspect repository feature settings and official release or preview notes for enablement and support status. Verify the improvement by checking that reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure. It does not isolate the security policy guides vulnerability reports issue described.
B:Check the repository star status and separate notification subscription settings for the affected account. Verify the improvement by checking that reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure. It does not isolate the security policy guides vulnerability reports issue described.
C:Check merge status, open pull request references and current contribution instructions before deleting or revising items. Verify the improvement by checking that reporters can follow a documented confidential route and maintainers receive actionable issues without public exploit disclosure. It does not isolate the security policy guides vulnerability reports issue described.