Microsoft GH-900 Practice Test 62
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.
Question 611
An internal auditor needs the first meaningful check for this situation: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. Before changing anything, which detail should a reviewer inspect? Select ONE answer.
- 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 the enterprise account type and identity provisioning configuration before proposing an access migration.
- Inspect matching protection settings, required reviewers and check results on a sample change proposal.
Explanation
Correct Answer
C:Inspect the enterprise account type and identity provisioning configuration before proposing an access migration. The principle behind this distinction is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. If the check supports this diagnosis, the next controlled response is to evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
Incorrect Answers
A: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 Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. It does not isolate the enterprise managed users centralize identity issue described.
B:Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions. The principle behind this distinction is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. It does not isolate the enterprise managed users centralize identity issue described.
D:Inspect matching protection settings, required reviewers and check results on a sample change proposal. The principle behind this distinction is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. It does not isolate the enterprise managed users centralize identity issue described.
Question 612
A change-control team asks what result would establish real resolution: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. Which observable result would best prove that the issue was resolved? Select ONE answer.
- 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.
- The account requires an additional permitted authentication factor at sign-in and recovery methods are retained securely.
- Authorized enterprise users have the expected centrally managed identities and role assignments under the selected model.
Explanation
Correct Answer
D: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 Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. An independent review should first inspect the enterprise account type and identity provisioning configuration before proposing an access migration.
Incorrect Answers
A: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 Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. This validates an adjacent control rather than the outcome of enterprise managed users centralize identity.
B: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 Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. This validates an adjacent control rather than the outcome of enterprise managed users centralize identity.
C:The account requires an additional permitted authentication factor at sign-in and recovery methods are retained securely. Closing an issue without this result would not prove technical resolution because Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. This validates an adjacent control rather than the outcome of enterprise managed users centralize identity.
Question 613
An organization wants to identify the least appropriate response to this event: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. What is the least defensible workaround for this project? Select ONE answer.
- Treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning.
- 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.
Explanation
Correct Answer
A:Treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning. That suggestion is specifically risky for the case: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. The safer GitHub workflow is to evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints after checking whether the team can inspect the enterprise account type and identity provisioning configuration before proposing an access migration.
Incorrect Answers
B:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. That suggestion is specifically risky for the case: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. The reported issue instead calls for rejecting treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning.
C:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. That suggestion is specifically risky for the case: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. The reported issue instead calls for rejecting treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning.
D:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. That suggestion is specifically risky for the case: An enterprise wants identity lifecycle tied to its corporate identity provider rather than unmanaged personal GitHub accounts. The reported issue instead calls for rejecting treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning.
Question 614
A contributor receives this specific collaboration request: A regulated company explores a managed-user enterprise model but assumes existing personal accounts automatically become centrally controlled. What should the contributor do to resolve this exact situation correctly? Select ONE answer.
- Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
- Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
- 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: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. A regulated company explores a managed-user enterprise model but assumes existing personal accounts automatically become centrally controlled.
Incorrect Answers
A:Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. Applying it first would leave enterprise managed users centralize identity unresolved.
C:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. Applying it first would leave enterprise managed users centralize identity unresolved.
D:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. Applying it first would leave enterprise managed users centralize identity unresolved.
Question 615
A repository owner is standardizing processes after this earlier failure: A regulated company explores a managed-user enterprise model but assumes existing personal accounts automatically become centrally controlled. What repeatable follow-up control best addresses the root weakness? Select ONE answer.
- 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.
- Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable.
- Educate contributors about safe secret storage and configure scanning or push protection where supported.
Explanation
Correct Answer
C:Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable. The reason it is relevant is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. Check periodically that authorized enterprise users have the expected centrally managed identities and role assignments under the selected model.
Incorrect Answers
A:Recheck platform documentation and policy scope after plan, model or team changes. The reason it is relevant is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. This would not prevent the recurrence of the enterprise managed users centralize identity failure.
B:Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities. The reason it is relevant is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. This would not prevent the recurrence of the enterprise managed users centralize identity failure.
D:Educate contributors about safe secret storage and configure scanning or push protection where supported. The reason it is relevant is that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. This would not prevent the recurrence of the enterprise managed users centralize identity failure.
Question 616
A GitHub maintainer must reject an unsound recommendation after this report: A regulated company explores a managed-user enterprise model but assumes existing personal accounts automatically become centrally controlled. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- 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.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- Treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning.
Explanation
Correct Answer
D:Treat an ordinary personally managed GitHub account as an Enterprise Managed User without enterprise provisioning. The shortcut contradicts the principle that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The safer GitHub workflow is to evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints after checking whether the team can inspect the enterprise account type and identity provisioning configuration before proposing an access migration.
Incorrect Answers
A:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. The shortcut contradicts the principle that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The direct risk in the case is enterprise managed users centralize identity, not this other concern.
B:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. The shortcut contradicts the principle that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The direct risk in the case is enterprise managed users centralize identity, not this other concern.
C:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. The shortcut contradicts the principle that Enterprise Managed Users are provisioned and controlled through an enterprise identity model rather than being ordinary personal accounts. The direct risk in the case is enterprise managed users centralize identity, not this other concern.
Question 617
During a repository review, the maintainer finds this condition: A developer purchases an individual Copilot plan and assumes the employer's data policies are automatically applied to it. What is the most defensible technical action for this case? Select ONE answer.
- 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.
- Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
Explanation
Correct Answer
A:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. The first useful confirmation step is to inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions.
Incorrect Answers
B:Inspect available organization or enterprise audit-log events for the action, actor and time window. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. The case instead calls for the following: review and set available organization or enterprise Copilot policies and seat assignments for approved users.
C:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. The case instead calls for the following: review and set available organization or enterprise Copilot policies and seat assignments for approved users.
D:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. The case instead calls for the following: review and set available organization or enterprise Copilot policies and seat assignments for approved users.
Question 618
A repository maintainer begins diagnosis of the following report: A developer purchases an individual Copilot plan and assumes the employer's data policies are automatically applied to it. Which focused investigation provides the most useful initial evidence? Select ONE answer.
- Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions.
- Inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions.
- Inspect matching protection settings, required reviewers and check results on a sample change proposal.
- Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies.
Explanation
Correct Answer
B:Inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions. Verify the improvement by checking that copilot use follows documented organization settings where the organizational offering supports those controls. If the check supports this diagnosis, the next controlled response is to review and set available organization or enterprise Copilot policies and seat assignments for approved users.
Incorrect Answers
A:Inspect organization team membership, granted repository roles and direct individual access for inconsistent permissions. Verify the improvement by checking that copilot use follows documented organization settings where the organizational offering supports those controls. It does not isolate the organization copilot policy management issue described.
C:Inspect matching protection settings, required reviewers and check results on a sample change proposal. Verify the improvement by checking that copilot use follows documented organization settings where the organizational offering supports those controls. It does not isolate the organization copilot policy management issue described.
D:Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. Verify the improvement by checking that copilot use follows documented organization settings where the organizational offering supports those controls. It does not isolate the organization copilot policy management issue described.
Question 619
An onboarding lead requires measurable closure for this problem: A developer purchases an individual Copilot plan and assumes the employer's data policies are automatically applied to it. How should the team demonstrate that the approved change worked? Select ONE answer.
- Affected dependencies are evaluated and safely updated or otherwise mitigated with evidence of compatibility.
- The account requires an additional permitted authentication factor at sign-in and recovery methods are retained securely.
- Copilot use follows documented organization settings where the organizational offering supports those controls.
- The account can authenticate through the supported passkey flow without revealing a reusable password to a phishing page.
Explanation
Correct Answer
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 Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. An independent review should first inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions.
Incorrect Answers
A: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 Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. This validates an adjacent control rather than the outcome of organization copilot policy management.
B:The account requires an additional permitted authentication factor at sign-in and recovery methods are retained securely. Closing an issue without this result would not prove technical resolution because Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. This validates an adjacent control rather than the outcome of organization copilot policy management.
D:The account can authenticate through the supported passkey flow without revealing a reusable password to a phishing page. Closing an issue without this result would not prove technical resolution because Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. This validates an adjacent control rather than the outcome of organization copilot policy management.
Question 620
A developer evaluates unsafe proposals following this situation: A developer purchases an individual Copilot plan and assumes the employer's data policies are automatically applied to it. Which suggested shortcut should be REJECTED in this situation? Select ONE answer.
- 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.
- Claim a personal Copilot subscription always grants enterprise admins full centralized policy control without organizational setup.
Explanation
Correct Answer
D:Claim a personal Copilot subscription always grants enterprise admins full centralized policy control without organizational setup. Objective closure would show that copilot use follows documented organization settings where the organizational offering supports those controls. The safer GitHub workflow is to review and set available organization or enterprise Copilot policies and seat assignments for approved users after checking whether the team can inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions.
Incorrect Answers
A:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Objective closure would show that copilot use follows documented organization settings where the organizational offering supports those controls. The reported issue instead calls for rejecting claim a personal Copilot subscription always grants enterprise admins full centralized policy control without organizational setup.
B:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Objective closure would show that copilot use follows documented organization settings where the organizational offering supports those controls. The reported issue instead calls for rejecting claim a personal Copilot subscription always grants enterprise admins full centralized policy control without organizational setup.
C:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. Objective closure would show that copilot use follows documented organization settings where the organizational offering supports those controls. The reported issue instead calls for rejecting claim a personal Copilot subscription always grants enterprise admins full centralized policy control without organizational setup.