Microsoft GH-900 Practice Test 65
Question 640
A project sponsor requires a clear acceptance check for this scenario: A library repository contains outdated dependencies and the team learns of a vulnerability advisory involving one package version. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible.
- The contributor can perform required tasks without unwanted authority to change sensitive settings.
- Approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges.
- Affected dependencies are evaluated and safely updated or otherwise mitigated with evidence of compatibility.
Explanation
Correct Answer
D:Affected dependencies are evaluated and safely updated or otherwise mitigated with evidence of compatibility. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. An independent review should first inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
Incorrect Answers
A:The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This validates an adjacent control rather than the outcome of dependabot advisories and maintenance.
B:The contributor can perform required tasks without unwanted authority to change sensitive settings. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This validates an adjacent control rather than the outcome of dependabot advisories and maintenance.
C:Approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. Closing an issue without this result would not prove technical resolution because Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This validates an adjacent control rather than the outcome of dependabot advisories and maintenance.
Question 641
A GitHub maintainer must reject an unsound recommendation after this report: A library repository contains outdated dependencies and the team learns of a vulnerability advisory involving one package version. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Blindly merge every dependency update without checking version compatibility or the actual advisory impact.
- Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
- Inspect available organization or enterprise audit-log events for the action, actor and time window.
- Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
Explanation
Correct Answer
A:Blindly merge every dependency update without checking version compatibility or the actual advisory impact. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. That suggestion is specifically risky for the case: A library repository contains outdated dependencies and the team learns of a vulnerability advisory involving one package version.
Incorrect Answers
B:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The reported issue instead calls for rejecting blindly merge every dependency update without checking version compatibility or the actual advisory impact.
C:Inspect available organization or enterprise audit-log events for the action, actor and time window. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The reported issue instead calls for rejecting blindly merge every dependency update without checking version compatibility or the actual advisory impact.
D:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The reported issue instead calls for rejecting blindly merge every dependency update without checking version compatibility or the actual advisory impact.
Question 642
During a repository review, the maintainer finds this condition: A web project receives automated dependency update suggestions but maintainers assume every suggested version must be merged without testing. Which practical next step fits this specific repository situation? Select ONE answer.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
- Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.
- Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
Explanation
Correct Answer
B:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The first useful confirmation step is to inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation. A web project receives automated dependency update suggestions but maintainers assume every suggested version must be merged without testing.
Incorrect Answers
A:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. Applying it first would leave dependabot advisories and maintenance unresolved.
C:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. Applying it first would leave dependabot advisories and maintenance unresolved.
D:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. Applying it first would leave dependabot advisories and maintenance unresolved.
Question 643
A GitHub team reviews how to prevent recurrence after this case: A web project receives automated dependency update suggestions but maintainers assume every suggested version must be merged without testing. Which ongoing practice most reliably prevents this same GitHub issue from recurring? Select ONE answer.
- Enforce applicable organization authentication requirements and review lost-device recovery procedures.
- Review passkey availability, device access and recovery options during security onboarding.
- Keep dependency manifests current and maintain a regular vulnerability review cycle.
- Rotate and revoke tokens when not needed and prefer purpose-limited credentials instead of broad account secrets.
Explanation
Correct Answer
C:Keep dependency manifests current and maintain a regular vulnerability review cycle. The reason it is relevant is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. It complements the initial correction to triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
Incorrect Answers
A:Enforce applicable organization authentication requirements and review lost-device recovery procedures. The reason it is relevant is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This would not prevent the recurrence of the dependabot advisories and maintenance failure.
B:Review passkey availability, device access and recovery options during security onboarding. The reason it is relevant is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This would not prevent the recurrence of the dependabot advisories and maintenance failure.
D:Rotate and revoke tokens when not needed and prefer purpose-limited credentials instead of broad account secrets. The reason it is relevant is that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. This would not prevent the recurrence of the dependabot advisories and maintenance failure.
Question 644
A pull request discussion contains questionable workarounds for this report: A web project receives automated dependency update suggestions but maintainers assume every suggested version must be merged without testing. What is the least defensible workaround for this project? Select ONE answer.
- Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
- Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
- Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
- Blindly merge every dependency update without checking version compatibility or the actual advisory impact.
Explanation
Correct Answer
D:Blindly merge every dependency update without checking version compatibility or the actual advisory impact. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The safer GitHub workflow is to triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing after checking whether the team can inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
Incorrect Answers
A:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The direct risk in the case is dependabot advisories and maintenance, not this other concern.
B:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The direct risk in the case is dependabot advisories and maintenance, not this other concern.
C:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. The shortcut contradicts the principle that Dependabot can surface dependency security and update information, but maintainers must evaluate risk and changes. The direct risk in the case is dependabot advisories and maintenance, not this other concern.
Question 645
A GitHub platform user encounters this scenario: A local developer finds a public library bug but assumes only paid maintainers may contribute improvements. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream.
- Evaluate a suitable Marketplace integration and review its requested permissions, publisher information and policy fit before installation.
- Apply InnerSource practices using organization-appropriate internal visibility, contribution documentation and cross-team reviews.
- Fork the repository under the contributor's account and use a branch and pull request for appropriate upstream suggestions.
Explanation
Correct Answer
A:Follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The first useful confirmation step is to inspect its license, contribution guide and maintained issue tracker before deciding how to participate.
Incorrect Answers
B:Evaluate a suitable Marketplace integration and review its requested permissions, publisher information and policy fit before installation. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The case instead calls for the following: follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream.
C:Apply InnerSource practices using organization-appropriate internal visibility, contribution documentation and cross-team reviews. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The case instead calls for the following: follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream.
D:Fork the repository under the contributor's account and use a branch and pull request for appropriate upstream suggestions. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The case instead calls for the following: follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream.
Question 646
A developer starts an investigation after the following user report: A local developer finds a public library bug but assumes only paid maintainers may contribute improvements. Before changing anything, which detail should a reviewer inspect? Select ONE answer.
- Inspect a maintainer's available sponsor profile and program eligibility before directing support to that account.
- Inspect its license, contribution guide and maintained issue tracker before deciding how to participate.
- Check that the correct public account is followed and distinguish activity feeds from watch subscriptions.
- Inspect the listing and requested scopes or installation targets to confirm it is appropriate for the intended repositories.
Explanation
Correct Answer
B:Inspect its license, contribution guide and maintained issue tracker before deciding how to participate. The principle behind this distinction is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. If the check supports this diagnosis, the next controlled response is to follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream.
Incorrect Answers
A:Inspect a maintainer's available sponsor profile and program eligibility before directing support to that account. The principle behind this distinction is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. It does not isolate the open-source participation benefits shared maintenance issue described.
C:Check that the correct public account is followed and distinguish activity feeds from watch subscriptions. The principle behind this distinction is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. It does not isolate the open-source participation benefits shared maintenance issue described.
D:Inspect the listing and requested scopes or installation targets to confirm it is appropriate for the intended repositories. The principle behind this distinction is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. It does not isolate the open-source participation benefits shared maintenance issue described.
Question 647
A GitHub contributor needs to validate a change affecting this incident: A local developer finds a public library bug but assumes only paid maintainers may contribute improvements. Which observable result would best prove that the issue was resolved? Select ONE answer.
- Visitors can identify the project's purpose and create their own new starter repository without needing upstream write access.
- A new contributor can make a bounded respectful proposal and receive useful review without disrupting the community.
- The proposed improvement has clear scope and is reviewable by project maintainers under the project's existing process.
- Supporters can find a legitimate funding path without treating contributions as purchased code-review approvals.
Explanation
Correct Answer
C:The proposed improvement has clear scope and is reviewable by project maintainers under the project's existing process. Closing an issue without this result would not prove technical resolution because Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. An independent review should first inspect its license, contribution guide and maintained issue tracker before deciding how to participate.
Incorrect Answers
A:Visitors can identify the project's purpose and create their own new starter repository without needing upstream write access. Closing an issue without this result would not prove technical resolution because Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. This validates an adjacent control rather than the outcome of open-source participation benefits shared maintenance.
B:A new contributor can make a bounded respectful proposal and receive useful review without disrupting the community. Closing an issue without this result would not prove technical resolution because Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. This validates an adjacent control rather than the outcome of open-source participation benefits shared maintenance.
D:Supporters can find a legitimate funding path without treating contributions as purchased code-review approvals. Closing an issue without this result would not prove technical resolution because Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. This validates an adjacent control rather than the outcome of open-source participation benefits shared maintenance.
Question 648
During a review, a contributor proposes an emergency bypass for this problem: A local developer finds a public library bug but assumes only paid maintainers may contribute improvements. What is the least defensible workaround for this project? Select ONE answer.
- Apply InnerSource practices using organization-appropriate internal visibility, contribution documentation and cross-team reviews.
- Fork the repository under the contributor's account and use a branch and pull request for appropriate upstream suggestions.
- Maintain clear discoverable repository descriptions and mark an appropriate starter as a repository template.
- Copy public source without reading its license and assume public visibility removes all contribution requirements.
Explanation
Correct Answer
D:Copy public source without reading its license and assume public visibility removes all contribution requirements. The shortcut contradicts the principle that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The safer GitHub workflow is to follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream after checking whether the team can inspect its license, contribution guide and maintained issue tracker before deciding how to participate.
Incorrect Answers
A:Apply InnerSource practices using organization-appropriate internal visibility, contribution documentation and cross-team reviews. The shortcut contradicts the principle that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The reported issue instead calls for rejecting copy public source without reading its license and assume public visibility removes all contribution requirements.
B:Fork the repository under the contributor's account and use a branch and pull request for appropriate upstream suggestions. The shortcut contradicts the principle that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The reported issue instead calls for rejecting copy public source without reading its license and assume public visibility removes all contribution requirements.
C:Maintain clear discoverable repository descriptions and mark an appropriate starter as a repository template. The shortcut contradicts the principle that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The reported issue instead calls for rejecting copy public source without reading its license and assume public visibility removes all contribution requirements.
Question 649
A distributed project team must respond to the following case: A nonprofit wants to publish a reusable tool and asks why a community would review or adapt code openly. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream.
- Maintain clear discoverable repository descriptions and mark an appropriate starter as a repository template.
- Follow the project's code of conduct and contribution guide and select a clearly scoped beginner-friendly issue if appropriate.
- Explore GitHub Sponsors for eligible maintainers and voluntary support with clear expectations about what sponsorship means.
Explanation
Correct Answer
A:Follow the project's contribution rules to report a useful issue or propose a reviewable improvement upstream. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. The first useful confirmation step is to inspect its license, contribution guide and maintained issue tracker before deciding how to participate. A nonprofit wants to publish a reusable tool and asks why a community would review or adapt code openly.
Incorrect Answers
B:Maintain clear discoverable repository descriptions and mark an appropriate starter as a repository template. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. Applying it first would leave open-source participation benefits shared maintenance unresolved.
C:Follow the project's code of conduct and contribution guide and select a clearly scoped beginner-friendly issue if appropriate. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. Applying it first would leave open-source participation benefits shared maintenance unresolved.
D:Explore GitHub Sponsors for eligible maintainers and voluntary support with clear expectations about what sponsorship means. Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. Applying it first would leave open-source participation benefits shared maintenance unresolved.
Question 650
An engineering manager is defining a durable safeguard for this problem: A nonprofit wants to publish a reusable tool and asks why a community would review or adapt code openly. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Promote reusable internal project documentation and review team access when personnel or organizational boundaries change.
- Encourage respectful public collaboration and sustainable attribution and maintenance practices.
- Document upstream synchronization and credit and licensing obligations for long-lived forks.
- Refresh discoverability metadata and starter files as maintained examples change.
Explanation
Correct Answer
B:Encourage respectful public collaboration and sustainable attribution and maintenance practices. The reason it is relevant is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. Check periodically that the proposed improvement has clear scope and is reviewable by project maintainers under the project's existing process.
Incorrect Answers
A:Promote reusable internal project documentation and review team access when personnel or organizational boundaries change. The reason it is relevant is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. This would not prevent the recurrence of the open-source participation benefits shared maintenance failure.
C:Document upstream synchronization and credit and licensing obligations for long-lived forks. The reason it is relevant is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. This would not prevent the recurrence of the open-source participation benefits shared maintenance failure.
D:Refresh discoverability metadata and starter files as maintained examples change. The reason it is relevant is that Open source can enable shared review and reuse under actual license and governance terms rather than merely visibility. This would not prevent the recurrence of the open-source participation benefits shared maintenance failure.