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 58

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.

Question 571

An organization wants to identify the least appropriate response to this event: An automation script needs to read one repository but a maintainer gives it an unrestricted token covering all account projects. What action should the team explicitly avoid in this scenario? Select ONE answer.

  1. Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
  2. Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
  3. Publish a broad long-lived token in source code to avoid configuring individual permissions.
  4. Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.

Explanation

Correct Answer

C:

Publish a broad long-lived token in source code to avoid configuring individual permissions. The shortcut contradicts the principle that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The safer GitHub workflow is to create a narrowly scoped fine-grained token with only the repository access and permissions actually required after checking whether the team can inspect selected repository scope, token permissions, approval requirements and expiration before using the token.

Incorrect Answers

A:

Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. The shortcut contradicts the principle that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The reported issue instead calls for rejecting publish a broad long-lived token in source code to avoid configuring individual permissions.

B:

Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. The shortcut contradicts the principle that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The reported issue instead calls for rejecting publish a broad long-lived token in source code to avoid configuring individual permissions.

D:

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 access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The reported issue instead calls for rejecting publish a broad long-lived token in source code to avoid configuring individual permissions.

Question 572

A contributor receives this specific collaboration request: A team uses a personal access token for a short integration and wants to avoid excessive organization access. Which practical next step fits this specific repository situation? 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. 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. A team uses a personal access token for a short integration and wants to avoid excessive organization access.

Incorrect Answers

A:

Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. Applying it first would leave fine-grained personal access tokens limit scope unresolved.

B:

Review and set available organization or enterprise Copilot policies and seat assignments for approved users. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. Applying it first would leave fine-grained personal access tokens limit scope unresolved.

C:

Inspect available organization or enterprise audit-log events for the action, actor and time window. GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. Applying it first would leave fine-grained personal access tokens limit scope unresolved.

Question 573

A repository owner is standardizing processes after this earlier failure: A team uses a personal access token for a short integration and wants to avoid excessive organization access. Which ongoing practice most reliably prevents this same GitHub issue from recurring? Select ONE answer.

  1. Rotate and revoke tokens when not needed and prefer purpose-limited credentials instead of broad account secrets.
  2. Audit repository access during onboarding, role changes and departure to maintain least privilege.
  3. Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices.
  4. Reassess protection rules as branch names, CI jobs or team review policies evolve.

Explanation

Correct Answer

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 GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. Check periodically that the intended authorized API call succeeds while unrelated repositories and privileged operations remain inaccessible.

Incorrect Answers

B:

Audit repository access during onboarding, role changes and departure to maintain least privilege. The reason it is relevant is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. This would not prevent the recurrence of the fine-grained personal access tokens limit scope failure.

C:

Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices. The reason it is relevant is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. This would not prevent the recurrence of the fine-grained personal access tokens limit scope failure.

D:

Reassess protection rules as branch names, CI jobs or team review policies evolve. The reason it is relevant is that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. This would not prevent the recurrence of the fine-grained personal access tokens limit scope failure.

Question 574

A GitHub maintainer must reject an unsound recommendation after this report: A team uses a personal access token for a short integration and wants to avoid excessive organization access. What is the least defensible workaround for this project? Select ONE answer.

  1. Inspect available organization or enterprise audit-log events for the action, actor and time window.
  2. Publish a broad long-lived token in source code to avoid configuring individual permissions.
  3. Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
  4. Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.

Explanation

Correct Answer

B:

Publish a broad long-lived token in source code to avoid configuring individual permissions. The shortcut contradicts the principle that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The safer GitHub workflow is to create a narrowly scoped fine-grained token with only the repository access and permissions actually required after checking whether the team can inspect selected repository scope, token permissions, approval requirements and expiration before using the token. A team uses a personal access token for a short integration and wants to avoid excessive organization access.

Incorrect Answers

A:

Inspect available organization or enterprise audit-log events for the action, actor and time window. The shortcut contradicts the principle that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The direct risk in the case is fine-grained personal access tokens limit scope, not this other concern.

C:

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 GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The direct risk in the case is fine-grained personal access tokens limit scope, not this other concern.

D:

Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. The shortcut contradicts the principle that GitHub access tokens can grant programmatic permissions and should follow least privilege, expiration and secure handling. The direct risk in the case is fine-grained personal access tokens limit scope, not this other concern.

Question 575

During a repository review, the maintainer finds this condition: A contractor only needs to review documentation but is granted admin control of a sensitive production repository. What should the contributor do to resolve this exact situation correctly? Select ONE answer.

  1. Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
  2. Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
  3. Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
  4. Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

Explanation

Correct Answer

C:

Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The first useful confirmation step is to inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet.

Incorrect Answers

A:

Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The case instead calls for the following: assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.

B:

Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The case instead calls for the following: assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.

D:

Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The case instead calls for the following: assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.

Question 576

A repository maintainer begins diagnosis of the following report: A contractor only needs to review documentation but is granted admin control of a sensitive production repository. Before changing anything, which detail should a reviewer inspect? Select ONE answer.

  1. Inspect the reported secret location, exposure context and current token status without copying secrets into new logs.
  2. Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation.
  3. Check account security settings and enrollment status rather than relying solely on a changed password.
  4. Inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet.

Explanation

Correct Answer

D:

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 roles carry different capabilities, so access should match actual responsibility rather than convenience. If the check supports this diagnosis, the next controlled response is to assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.

Incorrect Answers

A:

Inspect the reported secret location, exposure context and current token status without copying secrets into new logs. The principle behind this distinction is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. It does not isolate the repository roles separate read and administration issue described.

B:

Inspect dependency graph version information, advisory scope and update pull request test results before deciding on remediation. The principle behind this distinction is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. It does not isolate the repository roles separate read and administration issue described.

C:

Check account security settings and enrollment status rather than relying solely on a changed password. The principle behind this distinction is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. It does not isolate the repository roles separate read and administration issue described.

Question 577

An onboarding lead requires measurable closure for this problem: A contractor only needs to review documentation but is granted admin control of a sensitive production repository. Which observable result would best prove that the issue was resolved? Select ONE answer.

  1. The contributor can perform required tasks without unwanted authority to change sensitive settings.
  2. The intended repositories and branches enforce the documented constraints without silently exempting unrelated refs.
  3. Authorized users can access private content while intentionally public materials are visible to their intended audience.
  4. Authorized enterprise users have the expected centrally managed identities and role assignments under the selected model.

Explanation

Correct Answer

A:

The contributor can perform required tasks without unwanted authority to change sensitive settings. Closing an issue without this result would not prove technical resolution because Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. An independent review should first inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet.

Incorrect Answers

B:

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 Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This validates an adjacent control rather than the outcome of repository roles separate read and administration.

C:

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 roles carry different capabilities, so access should match actual responsibility rather than convenience. This validates an adjacent control rather than the outcome of repository roles separate read and administration.

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 Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This validates an adjacent control rather than the outcome of repository roles separate read and administration.

Question 578

A developer evaluates unsafe proposals following this situation: A contractor only needs to review documentation but is granted admin control of a sensitive production repository. What is the least defensible workaround for this project? Select ONE answer.

  1. Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
  2. Grant every collaborator repository admin rights because permission differences are inconvenient to understand.
  3. Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
  4. Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

Explanation

Correct Answer

B:

Grant every collaborator repository admin rights because permission differences are inconvenient to understand. The shortcut contradicts the principle that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. That suggestion is specifically risky for the case: A contractor only needs to review documentation but is granted admin control of a sensitive production repository.

Incorrect Answers

A:

Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. The shortcut contradicts the principle that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The reported issue instead calls for rejecting grant every collaborator repository admin rights because permission differences are inconvenient to understand.

C:

Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. The shortcut contradicts the principle that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The reported issue instead calls for rejecting grant every collaborator repository admin rights because permission differences are inconvenient to understand.

D:

Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. The shortcut contradicts the principle that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The reported issue instead calls for rejecting grant every collaborator repository admin rights because permission differences are inconvenient to understand.

Question 579

A project owner is investigating an operational GitHub workflow issue: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. What should the contributor do to resolve this exact situation correctly? 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. Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
  4. Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.

Explanation

Correct Answer

C:

Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. The first useful confirmation step is to inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet. A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage.

Incorrect Answers

A:

Review and set available organization or enterprise Copilot policies and seat assignments for approved users. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. Applying it first would leave repository roles separate read and administration unresolved.

B:

Inspect available organization or enterprise audit-log events for the action, actor and time window. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. Applying it first would leave repository roles separate read and administration unresolved.

D:

Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. Applying it first would leave repository roles separate read and administration unresolved.

Question 580

A contributor asks how to keep this workflow problem from happening again: A team leader cannot determine why a contributor can edit repository settings even though their task involves only issue triage. What repeatable follow-up control best addresses the root weakness? Select ONE answer.

  1. Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices.
  2. Reassess protection rules as branch names, CI jobs or team review policies evolve.
  3. Periodically audit ruleset scope and bypass actors after repository or team changes.
  4. Audit repository access during onboarding, role changes and departure to maintain least privilege.

Explanation

Correct Answer

D:

Audit repository access during onboarding, role changes and departure to maintain least privilege. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. It complements the initial correction to assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.

Incorrect Answers

A:

Review organization teams and owners regularly and remove unnecessary direct grants when team-based access suffices. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This would not prevent the recurrence of the repository roles separate read and administration failure.

B:

Reassess protection rules as branch names, CI jobs or team review policies evolve. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This would not prevent the recurrence of the repository roles separate read and administration failure.

C:

Periodically audit ruleset scope and bypass actors after repository or team changes. The reason it is relevant is that Repository roles carry different capabilities, so access should match actual responsibility rather than convenience. This would not prevent the recurrence of the repository roles separate read and administration failure.

GitHub Foundations (GH-900) Practice Tests