cert
cert-1
cert-2

Pass Microsoft GH-900 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
GH-900 Exam - Verified By Experts
GH-900 Premium Bundle
$14.99

GH-900 Premium Bundle

$74.99
$89.98
  • Premium File 187 Questions & Answers. Last update: Nov 12, 2026
  • Study Guide 470 Pages
 
$89.98
$74.99
accept 16 downloads in last 7 days
block-screenshots
Purchase Microsoft GH-900 Exam Training Products Individually
Microsoft GH-900 Premium File
Premium File 187 Q&A
$76.99$69.99
Microsoft GH-900 PDF Study Guide
Study Guide 470 Pages
$21.99 $19.99
Microsoft GH-900 Practice Test 57

Question 560

A pull request discussion contains questionable workarounds for this report: An organization requires stronger login controls before permitting new engineers to work on sensitive source. Which proposed response would create the clearest avoidable risk here? Select ONE answer.

  1. Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
  2. Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
  3. Inspect available organization or enterprise audit-log events for the action, actor and time window.
  4. Share a second-factor code with teammates in a chat message because the password is already known.

Explanation

Correct Answer

D:

Share a second-factor code with teammates in a chat message because the password is already known. The safer GitHub workflow is to enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors after checking whether the team can check account security settings and enrollment status rather than relying solely on a changed password. An organization requires stronger login controls before permitting new engineers to work on sensitive source.

Incorrect Answers

A:

Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. The safer GitHub workflow is to enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors after checking whether the team can check account security settings and enrollment status rather than relying solely on a changed password. The direct risk in the case is two-factor authentication protects accounts, not this other concern.

B:

Review and set available organization or enterprise Copilot policies and seat assignments for approved users. The safer GitHub workflow is to enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors after checking whether the team can check account security settings and enrollment status rather than relying solely on a changed password. The direct risk in the case is two-factor authentication protects accounts, not this other concern.

C:

Inspect available organization or enterprise audit-log events for the action, actor and time window. The safer GitHub workflow is to enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors after checking whether the team can check account security settings and enrollment status rather than relying solely on a changed password. The direct risk in the case is two-factor authentication protects accounts, not this other concern.

Question 561

A GitHub platform user encounters this scenario: A staff member repeatedly enters GitHub credentials on lookalike sign-in pages and needs stronger authentication. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.

  1. Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
  2. Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.
  3. Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
  4. Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.

Explanation

Correct Answer

A:

Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The first useful confirmation step is to inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.

Incorrect Answers

B:

Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The case instead calls for the following: register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.

C:

Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The case instead calls for the following: register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.

D:

Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The case instead calls for the following: register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.

Question 562

A developer starts an investigation after the following user report: A staff member repeatedly enters GitHub credentials on lookalike sign-in pages and needs stronger authentication. Which check best distinguishes the actual cause from a different GitHub issue? Select ONE answer.

  1. Inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions.
  2. Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.
  3. Filter audit events by relevant action, resource and timestamp and compare them to approved change records.
  4. Inspect the reported secret location, exposure context and current token status without copying secrets into new logs.

Explanation

Correct Answer

B:

Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser. The principle behind this distinction is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. If the check supports this diagnosis, the next controlled response is to register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.

Incorrect Answers

A:

Inspect current policy settings, assigned licenses and product capabilities to determine effective restrictions. The principle behind this distinction is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. It does not isolate the passkeys provide phishing-resistant sign-in issue described.

C:

Filter audit events by relevant action, resource and timestamp and compare them to approved change records. The principle behind this distinction is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. It does not isolate the passkeys provide phishing-resistant sign-in issue described.

D:

Inspect the reported secret location, exposure context and current token status without copying secrets into new logs. The principle behind this distinction is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. It does not isolate the passkeys provide phishing-resistant sign-in issue described.

Question 563

A GitHub contributor needs to validate a change affecting this incident: A staff member repeatedly enters GitHub credentials on lookalike sign-in pages and needs stronger authentication. Which verifiable state directly confirms successful remediation? Select ONE answer.

  1. Approved team members obtain expected repository access while employees outside the team do not inherit unrelated privileges.
  2. Unreviewed or failing changes cannot enter the protected branch through ordinary nonbypass workflows.
  3. The account can authenticate through the supported passkey flow without revealing a reusable password to a phishing page.
  4. The intended repositories and branches enforce the documented constraints without silently exempting unrelated refs.

Explanation

Correct Answer

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 Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. An independent review should first inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.

Incorrect Answers

A:

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 Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. This validates an adjacent control rather than the outcome of passkeys provide phishing-resistant sign-in.

B:

Unreviewed or failing changes cannot enter the protected branch through ordinary nonbypass workflows. Closing an issue without this result would not prove technical resolution because Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. This validates an adjacent control rather than the outcome of passkeys provide phishing-resistant sign-in.

D:

The intended repositories and branches enforce the documented constraints without silently exempting unrelated refs. Closing an issue without this result would not prove technical resolution because Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. This validates an adjacent control rather than the outcome of passkeys provide phishing-resistant sign-in.

Question 564

During a review, a contributor proposes an emergency bypass for this problem: A staff member repeatedly enters GitHub credentials on lookalike sign-in pages and needs stronger authentication. Which proposed response would create the clearest avoidable risk here? Select ONE answer.

  1. Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
  2. Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
  3. Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
  4. Send a reusable credential or passkey secret through email so every teammate can authenticate as the same person.

Explanation

Correct Answer

D:

Send a reusable credential or passkey secret through email so every teammate can authenticate as the same person. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The safer GitHub workflow is to register and use a supported passkey through the GitHub account's security settings with an approved recovery plan after checking whether the team can inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.

Incorrect Answers

A:

Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The reported issue instead calls for rejecting send a reusable credential or passkey secret through email so every teammate can authenticate as the same person.

B:

Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The reported issue instead calls for rejecting send a reusable credential or passkey secret through email so every teammate can authenticate as the same person.

C:

Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The reported issue instead calls for rejecting send a reusable credential or passkey secret through email so every teammate can authenticate as the same person.

Question 565

A distributed project team must respond to the following case: A developer wants to use supported device-based credential technology instead of only typed reusable passwords. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.

  1. Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
  2. Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
  3. Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
  4. Review and set available organization or enterprise Copilot policies and seat assignments for approved users.

Explanation

Correct Answer

A:

Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The first useful confirmation step is to inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser. A developer wants to use supported device-based credential technology instead of only typed reusable passwords.

Incorrect Answers

B:

Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. Applying it first would leave passkeys provide phishing-resistant sign-in unresolved.

C:

Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. Applying it first would leave passkeys provide phishing-resistant sign-in unresolved.

D:

Review and set available organization or enterprise Copilot policies and seat assignments for approved users. Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. Applying it first would leave passkeys provide phishing-resistant sign-in unresolved.

Question 566

An engineering manager is defining a durable safeguard for this problem: A developer wants to use supported device-based credential technology instead of only typed reusable passwords. Which maintenance policy is most appropriate for this specific risk? Select ONE answer.

  1. Rotate and revoke tokens when not needed and prefer purpose-limited credentials instead of broad account secrets.
  2. Review passkey availability, device access and recovery options during security onboarding.
  3. Audit repository access during onboarding, role changes and departure to maintain least privilege.
  4. Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices.

Explanation

Correct Answer

B:

Review passkey availability, device access and recovery options during security onboarding. The reason it is relevant is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. It complements the initial correction to register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.

Incorrect Answers

A:

Rotate and revoke tokens when not needed and prefer purpose-limited credentials instead of broad account secrets. The reason it is relevant is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. This would not prevent the recurrence of the passkeys provide phishing-resistant sign-in failure.

C:

Audit repository access during onboarding, role changes and departure to maintain least privilege. The reason it is relevant is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. This would not prevent the recurrence of the passkeys provide phishing-resistant sign-in failure.

D:

Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices. The reason it is relevant is that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. This would not prevent the recurrence of the passkeys provide phishing-resistant sign-in failure.

Question 567

An impatient project team suggests risky shortcuts for this case: A developer wants to use supported device-based credential technology instead of only typed reusable passwords. What action should the team explicitly avoid in this scenario? Select ONE answer.

  1. Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
  2. Inspect available organization or enterprise audit-log events for the action, actor and time window.
  3. Send a reusable credential or passkey secret through email so every teammate can authenticate as the same person.
  4. Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.

Explanation

Correct Answer

C:

Send a reusable credential or passkey secret through email so every teammate can authenticate as the same person. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The safer GitHub workflow is to register and use a supported passkey through the GitHub account's security settings with an approved recovery plan after checking whether the team can inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser. A developer wants to use supported device-based credential technology instead of only typed reusable passwords.

Incorrect Answers

A:

Review and set available organization or enterprise Copilot policies and seat assignments for approved users. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The direct risk in the case is passkeys provide phishing-resistant sign-in, not this other concern.

B:

Inspect available organization or enterprise audit-log events for the action, actor and time window. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The direct risk in the case is passkeys provide phishing-resistant sign-in, not this other concern.

D:

Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. The shortcut contradicts the principle that Passkeys rely on cryptographic authentication bound to a service identity and can reduce phishing exposure when properly configured. The direct risk in the case is passkeys provide phishing-resistant sign-in, not this other concern.

Question 568

A GitHub contributor is asked to resolve this report: An automation script needs to read one repository but a maintainer gives it an unrestricted token covering all account projects. Which practical next step fits this specific repository situation? Select ONE answer.

  1. Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
  2. Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
  3. Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
  4. Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

Explanation

Correct Answer

D:

Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The first useful confirmation step is to inspect selected repository scope, token permissions, approval requirements and expiration before using the token.

Incorrect Answers

A:

Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The case instead calls for the following: create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

B:

Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The case instead calls for the following: create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

C:

Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The case instead calls for the following: create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

Question 569

An internal auditor needs the first meaningful check for this situation: An automation script needs to read one repository but a maintainer gives it an unrestricted token covering all account projects. What should the team verify first to isolate the problem correctly? Select ONE answer.

  1. Inspect selected repository scope, token permissions, approval requirements and expiration before using the token.
  2. Filter audit events by relevant action, resource and timestamp and compare them to approved change records.
  3. Inspect the reported secret location, exposure context and current token status without copying secrets into new logs.
  4. Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.

Explanation

Correct Answer

A:

Inspect selected repository scope, token permissions, approval requirements and expiration before using the token. The principle behind this distinction is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. If the check supports this diagnosis, the next controlled response is to create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

Incorrect Answers

B:

Filter audit events by relevant action, resource and timestamp and compare them to approved change records. The principle behind this distinction is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. It does not isolate the fine-grained personal access tokens limit scope issue described.

C:

Inspect the reported secret location, exposure context and current token status without copying secrets into new logs. The principle behind this distinction is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. It does not isolate the fine-grained personal access tokens limit scope issue described.

D:

Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation. The principle behind this distinction is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. It does not isolate the fine-grained personal access tokens limit scope issue described.

Question 570

A change-control team asks what result would establish real resolution: An automation script needs to read one repository but a maintainer gives it an unrestricted token covering all account projects. Which measured or visible outcome most reliably establishes success? Select ONE answer.

  1. Unreviewed or failing changes cannot enter the protected branch through ordinary nonbypass workflows.
  2. The intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible.
  3. The intended repositories and branches enforce the documented constraints without silently exempting unrelated refs.
  4. Authorized users can access private content while intentionally public materials are visible to their intended audience.

Explanation

Correct Answer

B:

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 access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. An independent review should first inspect selected repository scope, token permissions, approval requirements and expiration before using the token.

Incorrect Answers

A:

Unreviewed or failing changes cannot enter the protected branch through ordinary nonbypass workflows. Closing an issue without this result would not prove technical resolution because GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. This validates an adjacent control rather than the outcome of fine-grained personal access tokens limit scope.

C:

The intended repositories and branches enforce the documented constraints without silently exempting unrelated refs. Closing an issue without this result would not prove technical resolution because GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. This validates an adjacent control rather than the outcome of fine-grained personal access tokens limit scope.

D:

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 GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. This validates an adjacent control rather than the outcome of fine-grained personal access tokens limit scope.

GitHub Foundations (GH-900) Practice Tests