Microsoft GH-900 Practice Test 61
Question 600
During a repository review, the maintainer finds this condition: A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns. Which controlled GitHub workflow action is most appropriate here? Select ONE best 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.
- Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.
Explanation
Correct Answer
D:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The first useful confirmation step is to inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns.
Incorrect Answers
A:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Applying it first would leave repository rulesets apply consistent controls unresolved.
B:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Applying it first would leave repository rulesets apply consistent controls unresolved.
C:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Applying it first would leave repository rulesets apply consistent controls unresolved.
Question 601
A GitHub team reviews how to prevent recurrence after this case: A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns. Which maintenance policy is most appropriate for this specific risk? Select ONE answer.
- Periodically audit ruleset scope and bypass actors after repository or team changes.
- Add a visibility and secret scan review to repository creation and every proposed public conversion.
- Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable.
- Recheck platform documentation and policy scope after plan, model or team changes.
Explanation
Correct Answer
A:Periodically audit ruleset scope and bypass actors after repository or team changes. The reason it is relevant is that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Check periodically that the intended repositories and branches enforce the documented constraints without silently exempting unrelated refs.
Incorrect Answers
B:Add a visibility and secret scan review to repository creation and every proposed public conversion. The reason it is relevant is that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. This would not prevent the recurrence of the repository rulesets apply consistent controls failure.
C:Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable. The reason it is relevant is that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. This would not prevent the recurrence of the repository rulesets apply consistent controls failure.
D:Recheck platform documentation and policy scope after plan, model or team changes. The reason it is relevant is that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. This would not prevent the recurrence of the repository rulesets apply consistent controls failure.
Question 602
A pull request discussion contains questionable workarounds for this report: A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
- Assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch.
- 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
B:Assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The safer GitHub workflow is to evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements after checking whether the team can inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns.
Incorrect Answers
A:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The direct risk in the case is repository rulesets apply consistent controls, not this other concern.
C:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The direct risk in the case is repository rulesets apply consistent controls, not this other concern.
D:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The direct risk in the case is repository rulesets apply consistent controls, not this other concern.
Question 603
A GitHub platform user encounters this scenario: A startup places proprietary service code in a public repository after assuming that organization membership hides its contents. Which practical next step fits this specific repository situation? Select ONE answer.
- 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.
- Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
- Inspect available organization or enterprise audit-log events for the action, actor and time window.
Explanation
Correct Answer
C:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The first useful confirmation step is to inspect current visibility and effective account permissions before publishing sensitive content.
Incorrect Answers
A:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The case instead calls for the following: set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
B:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The case instead calls for the following: set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
D:Inspect available organization or enterprise audit-log events for the action, actor and time window. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The case instead calls for the following: set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
Question 604
A developer starts an investigation after the following user report: A startup places proprietary service code in a public repository after assuming that organization membership hides its contents. What should the team verify first to isolate the problem correctly? Select ONE answer.
- Inspect selected repository scope, token permissions, approval requirements and expiration before using the token.
- Inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet.
- Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions.
- Inspect current visibility and effective account permissions before publishing sensitive content.
Explanation
Correct Answer
D:Inspect current visibility and effective account permissions before publishing sensitive content. The principle behind this distinction is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. If the check supports this diagnosis, the next controlled response is to set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
Incorrect Answers
A:Inspect selected repository scope, token permissions, approval requirements and expiration before using the token. The principle behind this distinction is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. It does not isolate the public private and internal visibility choices issue described.
B:Inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet. The principle behind this distinction is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. It does not isolate the public private and internal visibility choices issue described.
C:Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions. The principle behind this distinction is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. It does not isolate the public private and internal visibility choices issue described.
Question 605
A GitHub contributor needs to validate a change affecting this incident: A startup places proprietary service code in a public repository after assuming that organization membership hides its contents. Which measured or visible outcome most reliably establishes success? Select ONE answer.
- Authorized users can access private content while intentionally public materials are visible to their intended audience.
- The team can attribute the recorded administrative event and determine whether it matched an approved change request.
- The compromised credential is no longer usable and relevant repository protection alerts are addressed.
- Affected dependencies are evaluated and safely updated or otherwise mitigated with evidence of compatibility.
Explanation
Correct Answer
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 Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. An independent review should first inspect current visibility and effective account permissions before publishing sensitive content.
Incorrect Answers
B:The team can attribute the recorded administrative event and determine whether it matched an approved change request. Closing an issue without this result would not prove technical resolution because Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. This validates an adjacent control rather than the outcome of public private and internal visibility choices.
C:The compromised credential is no longer usable and relevant repository protection alerts are addressed. Closing an issue without this result would not prove technical resolution because Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. This validates an adjacent control rather than the outcome of public private and internal visibility choices.
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 Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. This validates an adjacent control rather than the outcome of public private and internal visibility choices.
Question 606
During a review, a contributor proposes an emergency bypass for this problem: A startup places proprietary service code in a public repository after assuming that organization membership hides its contents. What action should the team explicitly avoid in this scenario? Select ONE answer.
- Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
- Assume repositories under an organization namespace are automatically private regardless of the selected visibility setting.
- 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.
Explanation
Correct Answer
B:Assume repositories under an organization namespace are automatically private regardless of the selected visibility setting. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The safer GitHub workflow is to set and verify repository visibility to match the actual intended audience and hosting plan capabilities after checking whether the team can inspect current visibility and effective account permissions before publishing sensitive content.
Incorrect Answers
A:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The reported issue instead calls for rejecting assume repositories under an organization namespace are automatically private regardless of the selected visibility setting.
C:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The reported issue instead calls for rejecting assume repositories under an organization namespace are automatically private regardless of the selected visibility setting.
D:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The reported issue instead calls for rejecting assume repositories under an organization namespace are automatically private regardless of the selected visibility setting.
Question 607
A distributed project team must respond to the following case: A training organization wants a public reference implementation but also owns internal materials that must not be exposed. Which practical next step fits this specific repository situation? Select ONE answer.
- 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.
- Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
- Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.
Explanation
Correct Answer
C:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The first useful confirmation step is to inspect current visibility and effective account permissions before publishing sensitive content. A training organization wants a public reference implementation but also owns internal materials that must not be exposed.
Incorrect Answers
A:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. Applying it first would leave public private and internal visibility choices unresolved.
B:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. Applying it first would leave public private and internal visibility choices unresolved.
D:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. Applying it first would leave public private and internal visibility choices unresolved.
Question 608
An engineering manager is defining a durable safeguard for this problem: A training organization wants a public reference implementation but also owns internal materials that must not be exposed. Which ongoing practice most reliably prevents this same GitHub issue from recurring? Select ONE answer.
- Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable.
- Recheck platform documentation and policy scope after plan, model or team changes.
- Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities.
- Add a visibility and secret scan review to repository creation and every proposed public conversion.
Explanation
Correct Answer
D:Add a visibility and secret scan review to repository creation and every proposed public conversion. The reason it is relevant is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. It complements the initial correction to set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
Incorrect Answers
A:Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable. The reason it is relevant is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. This would not prevent the recurrence of the public private and internal visibility choices failure.
B:Recheck platform documentation and policy scope after plan, model or team changes. The reason it is relevant is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. This would not prevent the recurrence of the public private and internal visibility choices failure.
C:Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities. The reason it is relevant is that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. This would not prevent the recurrence of the public private and internal visibility choices failure.
Question 609
An impatient project team suggests risky shortcuts for this case: A training organization wants a public reference implementation but also owns internal materials that must not be exposed. What is the least defensible workaround for this project? Select ONE answer.
- Assume repositories under an organization namespace are automatically private regardless of the selected visibility setting.
- 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.
- Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
Explanation
Correct Answer
A:Assume repositories under an organization namespace are automatically private regardless of the selected visibility setting. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The safer GitHub workflow is to set and verify repository visibility to match the actual intended audience and hosting plan capabilities after checking whether the team can inspect current visibility and effective account permissions before publishing sensitive content. A training organization wants a public reference implementation but also owns internal materials that must not be exposed.
Incorrect Answers
B:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The direct risk in the case is public private and internal visibility choices, not this other concern.
C:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The direct risk in the case is public private and internal visibility choices, not this other concern.
D:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. The shortcut contradicts the principle that Repository visibility controls who can browse content and must be explicitly checked for sensitive projects. The direct risk in the case is public private and internal visibility choices, not this other concern.
Question 610
A GitHub contributor is asked to resolve this report: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
- Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
- 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
B:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The first useful confirmation step is to inspect the enterprise account type and identity provisioning configuration before proposing an access migration.
Incorrect Answers
A:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The case instead calls for the following: evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
C:Inspect available organization or enterprise audit-log events for the action, actor and time window. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The case instead calls for the following: evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
D:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The case instead calls for the following: evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.