Microsoft GH-900 Practice Test 59
Question 580
A contributor asks how to keep this workflow problem from happening again: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices.
- Reassess protection rules as branch names, CI jobs or team review policies evolve.
- Periodically audit ruleset scope and bypass actors after repository or team changes.
- Audit repository access during onboarding, role changes and departure to maintain least privilege.
Explanation
Correct Answer
D:Audit repository access during onboarding, role changes and departure to maintain least privilege. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. It complements the initial correction to assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
Incorrect Answers
A:Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This would not prevent the recurrence of the repository roles separate read and administration failure.
B:Reassess protection rules as branch names, CI jobs or team review policies evolve. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This would not prevent the recurrence of the repository roles separate read and administration failure.
C:Periodically audit ruleset scope and bypass actors after repository or team changes. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This would not prevent the recurrence of the repository roles separate read and administration failure.
Question 581
During a review, a contributor proposes an emergency bypass for this problem: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Grant every collaborator repository admin rights because permission differences are inconvenient to understand.
- Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
- Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
Explanation
Correct Answer
A:Grant every collaborator repository admin rights because permission differences are inconvenient to understand. That suggestion is specifically risky for the case: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. The safer GitHub workflow is to assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities after checking whether the team can inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet.
Incorrect Answers
B:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. That suggestion is specifically risky for the case: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. The direct risk in the case is repository roles separate read and administration, not this other concern.
C:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. That suggestion is specifically risky for the case: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. The direct risk in the case is repository roles separate read and administration, not this other concern.
D:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. That suggestion is specifically risky for the case: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. The direct risk in the case is repository roles separate read and administration, not this other concern.
Question 582
A distributed project team must respond to the following case: A software division invites each developer separately to dozens of repositories and loses track of shared access when staff transfer teams. What is the most defensible technical action for this case? Select ONE answer.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
- 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:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. The first useful confirmation step is to inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions.
Incorrect Answers
A:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. The case instead calls for the following: manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
C:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. The case instead calls for the following: manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
D:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. The case instead calls for the following: manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
Question 583
Before changing GitHub settings, a project reviewer examines this case: A software division invites each developer separately to dozens of repositories and loses track of shared access when staff transfer teams. Which focused investigation provides the most useful initial evidence? Select ONE answer.
- Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
- Check account security settings and enrollment status rather than relying solely on a changed password.
- Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions.
- Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.
Explanation
Correct Answer
C:Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions. Verify the improvement by checking that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. If the check supports this diagnosis, the next controlled response is to manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
Incorrect Answers
A:Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation. Verify the improvement by checking that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. It does not isolate the organization roles and team governance issue described.
B:Check account security settings and enrollment status rather than relying solely on a changed password. Verify the improvement by checking that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. It does not isolate the organization roles and team governance issue described.
D:Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser. Verify the improvement by checking that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. It does not isolate the organization roles and team governance issue described.
Question 584
Following a proposed correction, a reviewer revisits the following case: A software division invites each developer separately to dozens of repositories and loses track of shared access when staff transfer teams. How should the team demonstrate that the approved change worked? Select ONE answer.
- Authorized users can access private content while intentionally public materials are visible to their intended audience.
- Authorized enterprise users have the expected centrally managed identities and role assignments under the selected model.
- Copilot use follows documented organization settings where the organizational offering supports those controls.
- Approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges.
Explanation
Correct Answer
D: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 Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. An independent review should first inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions.
Incorrect Answers
A:Authorized users can access private content while intentionally public materials are visible to their intended audience. Closing an issue without this result would not prove technical resolution because Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. This validates an adjacent control rather than the outcome of organization roles and team governance.
B:Authorized enterprise users have the expected centrally managed identities and role assignments under the selected model. Closing an issue without this result would not prove technical resolution because Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. This validates an adjacent control rather than the outcome of organization roles and team governance.
C:Copilot use follows documented organization settings where the organizational offering supports those controls. Closing an issue without this result would not prove technical resolution because Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. This validates an adjacent control rather than the outcome of organization roles and team governance.
Question 585
A pull request discussion contains questionable workarounds for this report: A software division invites each developer separately to dozens of repositories and loses track of shared access when staff transfer teams. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- Share an organization owner account among all staff instead of assigning individual roles and teams.
- Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
- Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.
- Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
Explanation
Correct Answer
A:Share an organization owner account among all staff instead of assigning individual roles and teams. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The safer GitHub workflow is to manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities after checking whether the team can inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions.
Incorrect Answers
B:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The reported issue instead calls for rejecting share an organization owner account among all staff instead of assigning individual roles and teams.
C:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The reported issue instead calls for rejecting share an organization owner account among all staff instead of assigning individual roles and teams.
D:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The reported issue instead calls for rejecting share an organization owner account among all staff instead of assigning individual roles and teams.
Question 586
A GitHub platform user encounters this scenario: An engineering director needs consistent ownership and maintainer permissions across a set of organizational repositories. What is the most defensible technical action for this case? Select ONE answer.
- Inspect available organization or enterprise audit-log events for the action, actor and time window.
- Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
- Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
Explanation
Correct Answer
B:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. The first useful confirmation step is to inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions. An engineering director needs consistent ownership and maintainer permissions across a set of organizational repositories.
Incorrect Answers
A:Inspect available organization or enterprise audit-log events for the action, actor and time window. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. Applying it first would leave organization roles and team governance unresolved.
C:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. Applying it first would leave organization roles and team governance unresolved.
D:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Organizations and teams provide centralized group-based repository access distinct from ad hoc personal account sharing. Applying it first would leave organization roles and team governance unresolved.
Question 587
A project retrospective considers the long-term control for this situation: An engineering director needs consistent ownership and maintainer permissions across a set of organizational repositories. What operational safeguard should remain after the immediate fix? Select ONE answer.
- Reassess protection rules as branch names, CI jobs or team review policies evolve.
- Periodically audit ruleset scope and bypass actors after repository or team changes.
- Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices.
- Add a visibility and secret scan review to repository creation and every proposed public conversion.
Explanation
Correct Answer
C:Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices. Check periodically that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges.
Incorrect Answers
A:Reassess protection rules as branch names, CI jobs or team review policies evolve. Check periodically that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. This would not prevent the recurrence of the organization roles and team governance failure.
B:Periodically audit ruleset scope and bypass actors after repository or team changes. Check periodically that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. This would not prevent the recurrence of the organization roles and team governance failure.
D:Add a visibility and secret scan review to repository creation and every proposed public conversion. Check periodically that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. This would not prevent the recurrence of the organization roles and team governance failure.
Question 588
An organization wants to identify the least appropriate response to this event: An engineering director needs consistent ownership and maintainer permissions across a set of organizational repositories. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
- Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
- Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
- Share an organization owner account among all staff instead of assigning individual roles and teams.
Explanation
Correct Answer
D:Share an organization owner account among all staff instead of assigning individual roles and teams. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The safer GitHub workflow is to manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities after checking whether the team can inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions. An engineering director needs consistent ownership and maintainer permissions across a set of organizational repositories.
Incorrect Answers
A:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The direct risk in the case is organization roles and team governance, not this other concern.
B:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The direct risk in the case is organization roles and team governance, not this other concern.
C:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Objective closure would show that approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges. The direct risk in the case is organization roles and team governance, not this other concern.
Question 589
A contributor receives this specific collaboration request: A release engineer accidentally pushes directly to the default branch without passing required tests. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- 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.
- Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
Explanation
Correct Answer
A:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Protected branches can restrict direct changes and require approved reviews or checks before integration. The first useful confirmation step is to inspect matching protection settings, required reviewers and check results on a sample change proposal.
Incorrect Answers
B:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Protected branches can restrict direct changes and require approved reviews or checks before integration. The case instead calls for the following: configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
C:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Protected branches can restrict direct changes and require approved reviews or checks before integration. The case instead calls for the following: configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
D:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. Protected branches can restrict direct changes and require approved reviews or checks before integration. The case instead calls for the following: configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
Question 590
An engineer needs to distinguish root causes for the following workflow problem: A release engineer accidentally pushes directly to the default branch without passing required tests. Which diagnostic review best explains this exact reported behavior? Select ONE answer.
- Check account security settings and enrollment status rather than relying solely on a changed password.
- Inspect matching protection settings, required reviewers and check results on a sample change proposal.
- Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.
- Inspect selected repository scope, token permissions, approval requirements and expiration before using the token.
Explanation
Correct Answer
B:Inspect matching protection settings, required reviewers and check results on a sample change proposal. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. If the check supports this diagnosis, the next controlled response is to configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
Incorrect Answers
A:Check account security settings and enrollment status rather than relying solely on a changed password. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. It does not isolate the branch protection requires reviews and checks issue described.
C:Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. It does not isolate the branch protection requires reviews and checks issue described.
D:Inspect selected repository scope, token permissions, approval requirements and expiration before using the token. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. It does not isolate the branch protection requires reviews and checks issue described.