Microsoft GH-900 Practice Test 63
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.
Question 621
A project owner is investigating an operational GitHub workflow issue: A governance team needs to determine which organizational Copilot features and models are permitted before rolling out seats. 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.
- 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: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. A governance team needs to determine which organizational Copilot features and models are permitted before rolling out seats.
Incorrect Answers
B:Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. Applying it first would leave organization copilot policy management unresolved.
C:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. Applying it first would leave organization copilot policy management unresolved.
D:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Copilot Business and Enterprise governance controls depend on organizational configuration and current service entitlements. Applying it first would leave organization copilot policy management unresolved.
Question 622
A contributor asks how to keep this workflow problem from happening again: A governance team needs to determine which organizational Copilot features and models are permitted before rolling out seats. What operational safeguard should remain after the immediate fix? Select ONE answer.
- Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities.
- Recheck platform documentation and policy scope after plan, model or team changes.
- Educate contributors about safe secret storage and configure scanning or push protection where supported.
- Keep dependency manifests current and maintain a regular vulnerability review cycle.
Explanation
Correct Answer
B:Recheck platform documentation and policy scope after plan, model or team changes. Check periodically that copilot use follows documented organization settings where the organizational offering supports those controls. It complements the initial correction to review and set available organization or enterprise Copilot policies and seat assignments for approved users.
Incorrect Answers
A:Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities. Check periodically that copilot use follows documented organization settings where the organizational offering supports those controls. This would not prevent the recurrence of the organization copilot policy management failure.
C:Educate contributors about safe secret storage and configure scanning or push protection where supported. Check periodically that copilot use follows documented organization settings where the organizational offering supports those controls. This would not prevent the recurrence of the organization copilot policy management failure.
D:Keep dependency manifests current and maintain a regular vulnerability review cycle. Check periodically that copilot use follows documented organization settings where the organizational offering supports those controls. This would not prevent the recurrence of the organization copilot policy management failure.
Question 623
During a review, a contributor proposes an emergency bypass for this problem: A governance team needs to determine which organizational Copilot features and models are permitted before rolling out seats. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.
- 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.
- Claim a personal Copilot subscription always grants enterprise admins full centralized policy control without organizational setup.
- Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.
Explanation
Correct Answer
C: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. A governance team needs to determine which organizational Copilot features and models are permitted before rolling out seats.
Incorrect Answers
A:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Objective closure would show that copilot use follows documented organization settings where the organizational offering supports those controls. The direct risk in the case is organization copilot policy management, not this other concern.
B:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Objective closure would show that copilot use follows documented organization settings where the organizational offering supports those controls. The direct risk in the case is organization copilot policy management, not this other concern.
D: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 direct risk in the case is organization copilot policy management, not this other concern.
Question 624
A distributed project team must respond to the following case: An organization sees an unexpected permission change and needs to determine which authorized actor modified repository settings. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.
- 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.
- Inspect available organization or enterprise audit-log events for the action, actor and time window.
Explanation
Correct Answer
D:Inspect available organization or enterprise audit-log events for the action, actor and time window. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. The first useful confirmation step is to filter audit events by relevant action, resource and timestamp and compare them to approved change records.
Incorrect Answers
A:Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. The case instead calls for the following: inspect available organization or enterprise audit-log events for the action, actor and time window.
B:Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. The case instead calls for the following: inspect available organization or enterprise audit-log events for the action, actor and time window.
C:Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. The case instead calls for the following: inspect available organization or enterprise audit-log events for the action, actor and time window.
Question 625
Before changing GitHub settings, a project reviewer examines this case: An organization sees an unexpected permission change and needs to determine which authorized actor modified repository settings. Which diagnostic review best explains this exact reported behavior? Select ONE answer.
- Filter audit events by relevant action, resource and timestamp and compare them to approved change records.
- 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.
- Inspect current visibility and effective account permissions before publishing sensitive content.
Explanation
Correct Answer
A:Filter audit events by relevant action, resource and timestamp and compare them to approved change records. Verify the improvement by checking that the team can attribute the recorded administrative event and determine whether it matched an approved change request. If the check supports this diagnosis, the next controlled response is to inspect available organization or enterprise audit-log events for the action, actor and time window.
Incorrect Answers
B:Inspect matching protection settings, required reviewers and check results on a sample change proposal. Verify the improvement by checking that the team can attribute the recorded administrative event and determine whether it matched an approved change request. It does not isolate the audit logs support administrative investigation issue described.
C:Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. Verify the improvement by checking that the team can attribute the recorded administrative event and determine whether it matched an approved change request. It does not isolate the audit logs support administrative investigation issue described.
D:Inspect current visibility and effective account permissions before publishing sensitive content. Verify the improvement by checking that the team can attribute the recorded administrative event and determine whether it matched an approved change request. It does not isolate the audit logs support administrative investigation issue described.
Question 626
Following a proposed correction, a reviewer revisits the following case: An organization sees an unexpected permission change and needs to determine which authorized actor modified repository settings. What acceptance evidence should the project owner require before closure? Select ONE answer.
- The account requires an additional permitted authentication factor at sign-in and recovery methods are retained securely.
- The team can attribute the recorded administrative event and determine whether it matched an approved change request.
- The account can authenticate through the supported passkey flow without revealing a reusable password to a phishing page.
- The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible.
Explanation
Correct Answer
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 GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. An independent review should first filter audit events by relevant action, resource and timestamp and compare them to approved change records.
Incorrect Answers
A: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 GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. This validates an adjacent control rather than the outcome of audit logs support administrative investigation.
C: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 GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. This validates an adjacent control rather than the outcome of audit logs support administrative investigation.
D: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 GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. This validates an adjacent control rather than the outcome of audit logs support administrative investigation.
Question 627
A pull request discussion contains questionable workarounds for this report: An organization sees an unexpected permission change and needs to determine which authorized actor modified repository settings. Which tempting bypass would undermine rather than resolve the case? 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.
- Delete review records and assume repository commit history captures every organization security-setting change.
- Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
Explanation
Correct Answer
C:Delete review records and assume repository commit history captures every organization security-setting change. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The unsafe proposal is to delete review records and assume repository commit history captures every organization security-setting change.
Incorrect Answers
A:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The reported issue instead calls for rejecting delete review records and assume repository commit history captures every organization security-setting change.
B:Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The reported issue instead calls for rejecting delete review records and assume repository commit history captures every organization security-setting change.
D:Review and set available organization or enterprise Copilot policies and seat assignments for approved users. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The reported issue instead calls for rejecting delete review records and assume repository commit history captures every organization security-setting change.
Question 628
A GitHub platform user encounters this scenario: A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat. Which response best meets this GitHub and Git requirement without creating unnecessary risk? 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.
- Inspect available organization or enterprise audit-log events for the action, actor and time window.
Explanation
Correct Answer
D:Inspect available organization or enterprise audit-log events for the action, actor and time window. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. The first useful confirmation step is to filter audit events by relevant action, resource and timestamp and compare them to approved change records. A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat.
Incorrect Answers
A:Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. Applying it first would leave audit logs support administrative investigation unresolved.
B:Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. Applying it first would leave audit logs support administrative investigation unresolved.
C:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. GitHub administrative audit events and Git commits record different kinds of activity and should not be conflated. Applying it first would leave audit logs support administrative investigation unresolved.
Question 629
A project retrospective considers the long-term control for this situation: A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat. Which durable workflow change would most reduce similar future mistakes? Select ONE answer.
- Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities.
- Educate contributors about safe secret storage and configure scanning or push protection where supported.
- Keep dependency manifests current and maintain a regular vulnerability review cycle.
- Enforce applicable organization authentication requirements and review lost-device recovery procedures.
Explanation
Correct Answer
A:Monitor high-risk administrative events and retain records according to applicable policy and plan capabilities. Check periodically that the team can attribute the recorded administrative event and determine whether it matched an approved change request. It complements the initial correction to inspect available organization or enterprise audit-log events for the action, actor and time window.
Incorrect Answers
B:Educate contributors about safe secret storage and configure scanning or push protection where supported. Check periodically that the team can attribute the recorded administrative event and determine whether it matched an approved change request. This would not prevent the recurrence of the audit logs support administrative investigation failure.
C:Keep dependency manifests current and maintain a regular vulnerability review cycle. Check periodically that the team can attribute the recorded administrative event and determine whether it matched an approved change request. This would not prevent the recurrence of the audit logs support administrative investigation failure.
D:Enforce applicable organization authentication requirements and review lost-device recovery procedures. Check periodically that the team can attribute the recorded administrative event and determine whether it matched an approved change request. This would not prevent the recurrence of the audit logs support administrative investigation failure.
Question 630
An organization wants to identify the least appropriate response to this event: A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat. Which proposed response would create the clearest avoidable risk here? Select ONE answer.
- Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
- Delete review records and assume repository commit history captures every organization security-setting change.
- 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:Delete review records and assume repository commit history captures every organization security-setting change. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The unsafe proposal is to delete review records and assume repository commit history captures every organization security-setting change. A security analyst investigates a recent organization role adjustment but relies on vague recollections from team chat.
Incorrect Answers
A:Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The direct risk in the case is audit logs support administrative investigation, not this other concern.
C:Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The direct risk in the case is audit logs support administrative investigation, not this other concern.
D:Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Objective closure would show that the team can attribute the recorded administrative event and determine whether it matched an approved change request. The direct risk in the case is audit logs support administrative investigation, not this other concern.