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 60

Question 590

An engineer needs to distinguish root causes for the following workflow problem: A release engineer accidentally pushes directly to the default branch without passing required tests. Which diagnostic review best explains this exact reported behavior? Select ONE answer.

  1. Check account security settings and enrollment status rather than relying solely on a changed password.
  2. Inspect matching protection settings, required reviewers and check results on a sample change proposal.
  3. Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.
  4. Inspect selected repository scope, token permissions, approval requirements and expiration before using the token.

Explanation

Correct Answer

B:

Inspect matching protection settings, required reviewers and check results on a sample change proposal. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. If the check supports this diagnosis, the next controlled response is to configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.

Incorrect Answers

A:

Check account security settings and enrollment status rather than relying solely on a changed password. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. It does not isolate the branch protection requires reviews and checks issue described.

C:

Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. It does not isolate the branch protection requires reviews and checks issue described.

D:

Inspect selected repository scope, token permissions, approval requirements and expiration before using the token. The principle behind this distinction is that Protected branches can restrict direct changes and require approved reviews or checks before integration. It does not isolate the branch protection requires reviews and checks issue described.

Question 591

A repository owner asks for objective proof that this issue is fixed: A release engineer accidentally pushes directly to the default branch without passing required tests. What acceptance evidence should the project owner require before closure? Select ONE answer.

  1. Authorized enterprise users have the expected centrally managed identities and role assignments under the selected model.
  2. Copilot use follows documented organization settings where the organizational offering supports those controls.
  3. Unreviewed or failing changes cannot enter the protected branch through ordinary nonbypass workflows.
  4. The team can attribute the recorded administrative event and determine whether it matched an approved change request.

Explanation

Correct Answer

C:

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 Protected branches can restrict direct changes and require approved reviews or checks before integration. An independent review should first inspect matching protection settings, required reviewers and check results on a sample change proposal.

Incorrect Answers

A:

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 Protected branches can restrict direct changes and require approved reviews or checks before integration. This validates an adjacent control rather than the outcome of branch protection requires reviews and checks.

B:

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 Protected branches can restrict direct changes and require approved reviews or checks before integration. This validates an adjacent control rather than the outcome of branch protection requires reviews and checks.

D:

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 Protected branches can restrict direct changes and require approved reviews or checks before integration. This validates an adjacent control rather than the outcome of branch protection requires reviews and checks.

Question 592

An impatient project team suggests risky shortcuts for this case: A release engineer accidentally pushes directly to the default branch without passing required tests. Which tempting bypass would undermine rather than resolve the case? Select ONE answer.

  1. Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.
  2. Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities.
  3. Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities.
  4. Disable branch protection temporarily for every rushed change and leave it off after the emergency.

Explanation

Correct Answer

D:

Disable branch protection temporarily for every rushed change and leave it off after the emergency. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The safer GitHub workflow is to configure suitable branch protections requiring pull request approval and relevant status checks for the target branch after checking whether the team can inspect matching protection settings, required reviewers and check results on a sample change proposal.

Incorrect Answers

A:

Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The reported issue instead calls for rejecting disable branch protection temporarily for every rushed change and leave it off after the emergency.

B:

Assign an appropriate repository role based on the user's actual review, contribution or administrative responsibilities. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The reported issue instead calls for rejecting disable branch protection temporarily for every rushed change and leave it off after the emergency.

C:

Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The reported issue instead calls for rejecting disable branch protection temporarily for every rushed change and leave it off after the emergency.

Question 593

A GitHub contributor is asked to resolve this report: A company wants sensitive main-branch changes approved by reviewers and CI before merge, regardless of contributor. Which response best meets this GitHub and Git requirement without creating unnecessary risk? Select ONE answer.

  1. Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.
  2. Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure.
  3. Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing.
  4. Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.

Explanation

Correct Answer

A:

Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. Protected branches can restrict direct changes and require approved reviews or checks before integration. The first useful confirmation step is to inspect matching protection settings, required reviewers and check results on a sample change proposal. A company wants sensitive main-branch changes approved by reviewers and CI before merge, regardless of contributor.

Incorrect Answers

B:

Revoke or rotate compromised credentials promptly and use available secret scanning or push protection with an appropriate remediation procedure. Protected branches can restrict direct changes and require approved reviews or checks before integration. Applying it first would leave branch protection requires reviews and checks unresolved.

C:

Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. Protected branches can restrict direct changes and require approved reviews or checks before integration. Applying it first would leave branch protection requires reviews and checks unresolved.

D:

Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. Protected branches can restrict direct changes and require approved reviews or checks before integration. Applying it first would leave branch protection requires reviews and checks unresolved.

Question 594

An administrator is building an ongoing checklist for this issue: A company wants sensitive main-branch changes approved by reviewers and CI before merge, regardless of contributor. Which durable workflow change would most reduce similar future mistakes? Select ONE answer.

  1. Periodically audit ruleset scope and bypass actors after repository or team changes.
  2. Reassess protection rules as branch names, CI jobs or team review policies evolve.
  3. Add a visibility and secret scan review to repository creation and every proposed public conversion.
  4. Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable.

Explanation

Correct Answer

B:

Reassess protection rules as branch names, CI jobs or team review policies evolve. The reason it is relevant is that Protected branches can restrict direct changes and require approved reviews or checks before integration. Check periodically that unreviewed or failing changes cannot enter the protected branch through ordinary nonbypass workflows.

Incorrect Answers

A:

Periodically audit ruleset scope and bypass actors after repository or team changes. The reason it is relevant is that Protected branches can restrict direct changes and require approved reviews or checks before integration. This would not prevent the recurrence of the branch protection requires reviews and checks failure.

C:

Add a visibility and secret scan review to repository creation and every proposed public conversion. The reason it is relevant is that Protected branches can restrict direct changes and require approved reviews or checks before integration. This would not prevent the recurrence of the branch protection requires reviews and checks failure.

D:

Plan identity migrations and offboarding with current documentation rather than assuming account types are interchangeable. The reason it is relevant is that Protected branches can restrict direct changes and require approved reviews or checks before integration. This would not prevent the recurrence of the branch protection requires reviews and checks failure.

Question 595

A developer evaluates unsafe proposals following this situation: A company wants sensitive main-branch changes approved by reviewers and CI before merge, regardless of contributor. Which proposed response would create the clearest avoidable risk here? Select ONE answer.

  1. Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors.
  2. Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
  3. Disable branch protection temporarily for every rushed change and leave it off after the emergency.
  4. Create a narrowly scoped fine-grained token with only the repository access and permissions actually required.

Explanation

Correct Answer

C:

Disable branch protection temporarily for every rushed change and leave it off after the emergency. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The safer GitHub workflow is to configure suitable branch protections requiring pull request approval and relevant status checks for the target branch after checking whether the team can inspect matching protection settings, required reviewers and check results on a sample change proposal. A company wants sensitive main-branch changes approved by reviewers and CI before merge, regardless of contributor.

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 Protected branches can restrict direct changes and require approved reviews or checks before integration. The direct risk in the case is branch protection requires reviews and checks, not this other concern.

B:

Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The direct risk in the case is branch protection requires reviews and checks, not this other concern.

D:

Create a narrowly scoped fine-grained token with only the repository access and permissions actually required. The shortcut contradicts the principle that Protected branches can restrict direct changes and require approved reviews or checks before integration. The direct risk in the case is branch protection requires reviews and checks, not this other concern.

Question 596

A project owner is investigating an operational GitHub workflow issue: A company needs consistent branch and tag restrictions across multiple repositories but maintains fragile per-branch exceptions. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.

  1. Set and verify repository visibility to match the actual intended audience and hosting plan capabilities.
  2. Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints.
  3. Review and set available organization or enterprise Copilot policies and seat assignments for approved users.
  4. Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

Explanation

Correct Answer

D:

Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The first useful confirmation step is to inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies.

Incorrect Answers

A:

Set and verify repository visibility to match the actual intended audience and hosting plan capabilities. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The case instead calls for the following: evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

B:

Evaluate Enterprise Managed Users as a separate enterprise identity model with supported provisioning and access constraints. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The case instead calls for the following: evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

C:

Review and set available organization or enterprise Copilot policies and seat assignments for approved users. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The case instead calls for the following: evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

Question 597

An administrator requests evidence about this repository behavior: A company needs consistent branch and tag restrictions across multiple repositories but maintains fragile per-branch exceptions. Which check best distinguishes the actual cause from a different GitHub issue? Select ONE answer.

  1. Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies.
  2. Inspect the account's passkey enrollment and eligible sign-in methods for the current device and browser.
  3. Inspect selected repository scope, token permissions, approval requirements and expiration before using the token.
  4. Inspect effective access and repository permissions rather than relying only on a role label in an onboarding spreadsheet.

Explanation

Correct Answer

A:

Inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. The principle behind this distinction is that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. If the check supports this diagnosis, the next controlled response is to evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

Incorrect Answers

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 GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. It does not isolate the repository rulesets apply consistent controls issue described.

C:

Inspect selected repository scope, token permissions, approval requirements and expiration before using the token. The principle behind this distinction is that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. It does not isolate the repository rulesets apply consistent controls issue described.

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 GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. It does not isolate the repository rulesets apply consistent controls issue described.

Question 598

A project sponsor requires a clear acceptance check for this scenario: A company needs consistent branch and tag restrictions across multiple repositories but maintains fragile per-branch exceptions. Which verifiable state directly confirms successful remediation? Select ONE answer.

  1. Copilot use follows documented organization settings where the organizational offering supports those controls.
  2. The intended repositories and branches enforce the documented constraints without silently exempting unrelated refs.
  3. The team can attribute the recorded administrative event and determine whether it matched an approved change request.
  4. The compromised credential is no longer usable and relevant repository protection alerts are addressed.

Explanation

Correct Answer

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 GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. An independent review should first inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies.

Incorrect Answers

A:

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 GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. This validates an adjacent control rather than the outcome of repository rulesets apply consistent controls.

C:

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 rulesets can express ref-level policy and require careful targeting and enforcement configuration. This validates an adjacent control rather than the outcome of repository rulesets apply consistent controls.

D:

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 GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. This validates an adjacent control rather than the outcome of repository rulesets apply consistent controls.

Question 599

A GitHub maintainer must reject an unsound recommendation after this report: A company needs consistent branch and tag restrictions across multiple repositories but maintains fragile per-branch exceptions. Which proposed response would create the clearest avoidable risk here? 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. Assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch.
  4. Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch.

Explanation

Correct Answer

C:

Assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The safer GitHub workflow is to evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements after checking whether the team can inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies.

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 GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The reported issue instead calls for rejecting assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch.

B:

Manage membership through appropriate GitHub organization teams and assign repository access according to team responsibilities. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The reported issue instead calls for rejecting assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch.

D:

Configure suitable branch protections requiring pull request approval and relevant status checks for the target branch. The shortcut contradicts the principle that GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The reported issue instead calls for rejecting assume merely creating an inactive ruleset guarantees its restrictions are enforced for every repository branch.

Question 600

During a repository review, the maintainer finds this condition: A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns. Which controlled GitHub workflow action is most appropriate here? Select ONE best answer.

  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. Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan.
  4. Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements.

Explanation

Correct Answer

D:

Evaluate and configure supported repository or organization rulesets that match intended refs and enforcement requirements. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. The first useful confirmation step is to inspect effective ruleset targets, enforcement state and bypass permissions before assuming a rule applies. A platform team wants to restrict risky pushes and enforce documented organization-level branch naming patterns.

Incorrect Answers

A:

Triage detected vulnerable dependencies and review supported Dependabot alerts or updates with normal compatibility testing. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Applying it first would leave repository rulesets apply consistent controls unresolved.

B:

Enable supported two-factor authentication on the GitHub account and use secure recovery procedures and approved factors. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Applying it first would leave repository rulesets apply consistent controls unresolved.

C:

Register and use a supported passkey through the GitHub account's security settings with an approved recovery plan. GitHub rulesets can express ref-level policy and require careful targeting and enforcement configuration. Applying it first would leave repository rulesets apply consistent controls unresolved.

GitHub Foundations (GH-900) Practice Tests