Microsoft GH-900 Practice Test 27
Question 260
A project owner is investigating an operational GitHub workflow issue: An obsolete demo service stays writable and contributors keep opening changes to code the team no longer maintains. What should the contributor do to resolve this exact situation correctly? 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.
- Archive the obsolete repository after documenting its replacement and ongoing support expectations.
Explanation
Correct Answer
D:Archive the obsolete repository after documenting its replacement and ongoing support expectations. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. The first useful confirmation step is to check repository settings and current maintenance status to confirm archiving is intentional and the replacement link is correct.
Incorrect Answers
A:Use relevant repository Insights and traffic metrics while explaining their different definitions and limits. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. The case instead calls for the following: archive the obsolete repository after documenting its replacement and ongoing support expectations.
B:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. The case instead calls for the following: archive the obsolete repository after documenting its replacement and ongoing support expectations.
C:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. The case instead calls for the following: archive the obsolete repository after documenting its replacement and ongoing support expectations.
Question 261
An administrator requests evidence about this repository behavior: An obsolete demo service stays writable and contributors keep opening changes to code the team no longer maintains. Before changing anything, which detail should a reviewer inspect? Select ONE answer.
- Check repository settings and current maintenance status to confirm archiving is intentional and the replacement link is correct.
- 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:Check repository settings and current maintenance status to confirm archiving is intentional and the replacement link is correct. Verify the improvement by checking that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. If the check supports this diagnosis, the next controlled response is to archive the obsolete repository after documenting its replacement and ongoing support expectations.
Incorrect Answers
B:Inspect repository feature settings and official release or preview notes for enablement and support status. Verify the improvement by checking that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. It does not isolate the archive a read-only historical repository issue described.
C:Check the repository star status and separate notification subscription settings for the affected account. Verify the improvement by checking that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. It does not isolate the archive a read-only historical repository 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 visitors can browse preserved history while the repository is marked archived and routine changes are restricted. It does not isolate the archive a read-only historical repository issue described.
Question 262
A project sponsor requires a clear acceptance check for this scenario: An obsolete demo service stays writable and contributors keep opening changes to code the team no longer maintains. Which observable result would best prove that the issue was resolved? Select ONE answer.
- Pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval.
- Visitors can browse preserved history while the repository is marked archived and routine changes are restricted.
- 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.
Explanation
Correct Answer
B:Visitors can browse preserved history while the repository is marked archived and routine changes are restricted. Closing an issue without this result would not prove technical resolution because GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. An independent review should first check repository settings and current maintenance status to confirm archiving is intentional and the replacement link is correct.
Incorrect Answers
A: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 GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. This validates an adjacent control rather than the outcome of archive a read-only historical repository.
C: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 GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. This validates an adjacent control rather than the outcome of archive a read-only historical repository.
D: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 GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. This validates an adjacent control rather than the outcome of archive a read-only historical repository.
Question 263
A GitHub maintainer must reject an unsound recommendation after this report: An obsolete demo service stays writable and contributors keep opening changes to code the team no longer maintains. 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.
- Delete all historical source and references immediately merely because the project is no longer under active development.
- Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events.
Explanation
Correct Answer
C:Delete all historical source and references immediately merely because the project is no longer under active development. Objective closure would show that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. That suggestion is specifically risky for the case: An obsolete demo service stays writable and contributors keep opening changes to code the team no longer maintains.
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 visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The reported issue instead calls for rejecting delete all historical source and references immediately merely because the project is no longer under active development.
B:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. Objective closure would show that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The reported issue instead calls for rejecting delete all historical source and references immediately merely because the project is no longer under active development.
D:Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events. Objective closure would show that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The reported issue instead calls for rejecting delete all historical source and references immediately merely because the project is no longer under active development.
Question 264
During a repository review, the maintainer finds this condition: A laboratory needs to preserve a completed research repository for reference without inviting routine new development. What should the contributor do to resolve this exact situation correctly? 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.
- Archive the obsolete repository after documenting its replacement and ongoing support expectations.
Explanation
Correct Answer
D:Archive the obsolete repository after documenting its replacement and ongoing support expectations. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. The first useful confirmation step is to check repository settings and current maintenance status to confirm archiving is intentional and the replacement link is correct. A laboratory needs to preserve a completed research repository for reference without inviting routine new development.
Incorrect Answers
A:Enable or inspect GitHub dependency insights and verify manifest data to identify declared or detected package relationships. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. Applying it first would leave archive a read-only historical repository unresolved.
B:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. Applying it first would leave archive a read-only historical repository unresolved.
C:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. GitHub repository archiving communicates a read-only maintenance state while preserving a discoverable historical record. Applying it first would leave archive a read-only historical repository unresolved.
Question 265
A GitHub team reviews how to prevent recurrence after this case: A laboratory needs to preserve a completed research repository for reference without inviting routine new development. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Keep an archive notice that points visitors to the actively maintained replacement or successor project.
- Require a license decision during public repository creation and review compliance when accepting third-party code.
- 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.
Explanation
Correct Answer
A:Keep an archive notice that points visitors to the actively maintained replacement or successor project. Check periodically that visitors can browse preserved history while the repository is marked archived and routine changes are restricted.
Incorrect Answers
B:Require a license decision during public repository creation and review compliance when accepting third-party code. Check periodically that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. This would not prevent the recurrence of the archive a read-only historical repository failure.
C:Update the contribution guide when branch policies, CI checks or code-style requirements change. Check periodically that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. This would not prevent the recurrence of the archive a read-only historical repository failure.
D:Maintain CODEOWNERS entries when teams or directories change and protect the owner file itself. Check periodically that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. This would not prevent the recurrence of the archive a read-only historical repository failure.
Question 266
A pull request discussion contains questionable workarounds for this report: A laboratory needs to preserve a completed research repository for reference without inviting routine new development. 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.
- Delete all historical source and references immediately merely because the project is no longer under active development.
- 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:Delete all historical source and references immediately merely because the project is no longer under active development. Objective closure would show that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The safer GitHub workflow is to archive the obsolete repository after documenting its replacement and ongoing support expectations after checking whether the team can check repository settings and current maintenance status to confirm archiving is intentional and the replacement link is correct.
Incorrect Answers
A:Use relevant repository Insights and traffic metrics while explaining their different definitions and limits. Objective closure would show that visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The direct risk in the case is archive a read-only historical repository, 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 visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The direct risk in the case is archive a read-only historical repository, 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 visitors can browse preserved history while the repository is marked archived and routine changes are restricted. The direct risk in the case is archive a read-only historical repository, not this other concern.
Question 267
A GitHub platform user encounters this scenario: A project manager interprets GitHub stars as proof that every visitor deployed the software in production. What is the most defensible technical action for this case? Select ONE answer.
- Publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel.
- Use a repository template to create a new project with the intended starter files and separately managed history.
- Use relevant repository Insights and traffic metrics while explaining their different definitions and limits.
- Set the intended default branch and update automation, protection and contributor references that depend on its name.
Explanation
Correct Answer
C:Use relevant repository Insights and traffic metrics while explaining their different definitions and limits. GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. The first useful confirmation step is to inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions.
Incorrect Answers
A:Publish a SECURITY.md policy with supported versions and an appropriate private vulnerability reporting channel. GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. The case instead calls for the following: use relevant repository Insights and traffic metrics while explaining their different definitions and limits.
B:Use a repository template to create a new project with the intended starter files and separately managed history. GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. The case instead calls for the following: use relevant repository Insights and traffic metrics while explaining their different definitions and limits.
D:Set the intended default branch and update automation, protection and contributor references that depend on its name. GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. The case instead calls for the following: use relevant repository Insights and traffic metrics while explaining their different definitions and limits.
Question 268
A developer starts an investigation after the following user report: A project manager interprets GitHub stars as proof that every visitor deployed the software in production. Which focused investigation provides the most useful initial evidence? 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.
- Inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions.
Explanation
Correct Answer
D:Inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions. If the check supports this diagnosis, the next controlled response is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits. Verify the improvement by checking that the report labels which figures are views, clones, contributors or stars and does not infer unsupported user adoption.
Incorrect Answers
A:Inspect repository feature settings and official release or preview notes for enablement and support status. If the check supports this diagnosis, the next controlled response is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits. It does not isolate the repository insights and traffic distinguish signals issue described.
B:Check the repository star status and separate notification subscription settings for the affected account. If the check supports this diagnosis, the next controlled response is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits. It does not isolate the repository insights and traffic distinguish signals issue described.
C:Check merge status, open pull request references and current contribution instructions before deleting or revising items. If the check supports this diagnosis, the next controlled response is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits. It does not isolate the repository insights and traffic distinguish signals issue described.
Question 269
A GitHub contributor needs to validate a change affecting this incident: A project manager interprets GitHub stars as proof that every visitor deployed the software in production. How should the team demonstrate that the approved change worked? Select ONE answer.
- The report labels which figures are views, clones, contributors or stars and does not infer unsupported user adoption.
- Pull requests touching the protected paths request suitable owner reviews and cannot bypass required owner approval.
- 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.
Explanation
Correct Answer
A:The report labels which figures are views, clones, contributors or stars and does not infer unsupported user adoption. Closing an issue without this result would not prove technical resolution because GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. An independent review should first inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions.
Incorrect Answers
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 GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. This validates an adjacent control rather than the outcome of repository insights and traffic distinguish signals.
C: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 GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. This validates an adjacent control rather than the outcome of repository insights and traffic distinguish signals.
D: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 GitHub exposes different repository activity and engagement signals, none of which alone proves real-world deployment. This validates an adjacent control rather than the outcome of repository insights and traffic distinguish signals.
Question 270
During a review, a contributor proposes an emergency bypass for this problem: A project manager interprets GitHub stars as proof that every visitor deployed the software in production. 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.
- Present the total stars as a definitive count of unique active production installations with no further evidence.
- 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
B:Present the total stars as a definitive count of unique active production installations with no further evidence. The safer GitHub workflow is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits after checking whether the team can inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions.
Incorrect Answers
A:Make a deliberate branch-based file edit or move, review the diff and commit the intended content change. The safer GitHub workflow is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits after checking whether the team can inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions. The reported issue instead calls for rejecting present the total stars as a definitive count of unique active production installations with no further evidence.
C:Check the feature's current availability, account eligibility and documented preview limitations before relying on it. The safer GitHub workflow is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits after checking whether the team can inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions. The reported issue instead calls for rejecting present the total stars as a definitive count of unique active production installations with no further evidence.
D:Distinguish starring for discovery from watching or custom notification subscriptions for ongoing repository events. The safer GitHub workflow is to use relevant repository Insights and traffic metrics while explaining their different definitions and limits after checking whether the team can inspect available traffic views, contributors and activity insights separately from star counts before drawing conclusions. The reported issue instead calls for rejecting present the total stars as a definitive count of unique active production installations with no further evidence.