cert
cert-1
cert-2

Pass Microsoft GH-100 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-100 Exam - Verified By Experts
GH-100 Premium File

GH-100 Premium File

$69.99
$76.99
  • Premium File 171 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 11 downloads in the last 7 days
block-screenshots
Microsoft GH-100 Practice Test 12

Question 110

GitHub Enterprise administration scenario — Validate team grant consistency across repositories. In an enterprise development environment: An organization adds a new team to a repository but the team unexpectedly receives admin rather than the anticipated read-only permission. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.

  1. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.
  2. Team members have only the intended read capability across all reviewed repositories.
  3. Enterprise and organization governance controls require authorization from accountable higher-scope policy owners.
  4. All users in the policy population meet the documented authentication requirement while approved service integrations still function.
  5. Repository access through a team must be verified at the effective permission level and scoped by the owner.
  6. Correct the team repository permission and document the least-privilege approval for the repository owner.

Explanation

Correct Answers

B:

Team members have only the intended read capability across all reviewed repositories. Correct the team repository permission and document the least-privilege approval for the repository owner. Repository access through a team must be verified at the effective permission level and scoped by the owner.

E:

Repository access through a team must be verified at the effective permission level and scoped by the owner. Correct the team repository permission and document the least-privilege approval for the repository owner. Team members have only the intended read capability across all reviewed repositories.

F:

Correct the team repository permission and document the least-privilege approval for the repository owner. Repository access through a team must be verified at the effective permission level and scoped by the owner. Team members have only the intended read capability across all reviewed repositories.

Incorrect Answers

A:

Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. It does not implement the governing rule for this approval: An organization adds a new team to a repository but the team unexpectedly receives admin rather than the anticipated read-only permission. Correct the team repository permission and document the least-privilege approval for the repository owner. Team members have only the intended read capability across all reviewed repositories.

C:

Enterprise and organization governance controls require authorization from accountable higher-scope policy owners. It is not the rule that supports the proposed change and acceptance test: An organization adds a new team to a repository but the team unexpectedly receives admin rather than the anticipated read-only permission. Repository access through a team must be verified at the effective permission level and scoped by the owner. Correct the team repository permission and document the least-privilege approval for the repository owner.

D:

All users in the policy population meet the documented authentication requirement while approved service integrations still function. It would not independently demonstrate that the control works: An organization adds a new team to a repository but the team unexpectedly receives admin rather than the anticipated read-only permission. Team members have only the intended read capability across all reviewed repositories. Correct the team repository permission and document the least-privilege approval for the repository owner.

Question 111

GitHub Enterprise administration scenario — Control repository custom-role rollout. In an enterprise development environment: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.

  1. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
  2. Custom role design must consider each permission's operational effect, not only the label shown to users.
  3. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.
  4. Managed-account offboarding must revoke the GitHub account lifecycle through the configured IdP provisioning channel.

Explanation

Correct Answer

B:

Custom role design must consider each permission's operational effect, not only the label shown to users. Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Split incompatible audit and modification duties into separate permitted roles with documented owners.

Incorrect Answers

A:

Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. It does not govern the condition described: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Custom role design must consider each permission's operational effect, not only the label shown to users.

C:

Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. It does not govern the condition described: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Custom role design must consider each permission's operational effect, not only the label shown to users.

D:

Managed-account offboarding must revoke the GitHub account lifecycle through the configured IdP provisioning channel. It does not govern the condition described: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Custom role design must consider each permission's operational effect, not only the label shown to users.

Question 112

GitHub Enterprise administration scenario — Control repository custom-role rollout. In an enterprise development environment: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect the proposed permission matrix and test roles against sample repositories and workflow files.
  2. Review the role's proposed permissions, subscription support and which repositories actually require the access.
  3. Compare the incident approval and duration with current repository roles and relevant audit events.
  4. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.

Explanation

Correct Answer

A:

Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Custom role design must consider each permission's operational effect, not only the label shown to users. Split incompatible audit and modification duties into separate permitted roles with documented owners.

Incorrect Answers

B:

Review the role's proposed permissions, subscription support and which repositories actually require the access. That check would not establish the decisive facts for this condition: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Inspect the proposed permission matrix and test roles against sample repositories and workflow files.

C:

Compare the incident approval and duration with current repository roles and relevant audit events. That check would not establish the decisive facts for this condition: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Inspect the proposed permission matrix and test roles against sample repositories and workflow files.

D:

Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. That check would not establish the decisive facts for this condition: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Inspect the proposed permission matrix and test roles against sample repositories and workflow files.

Question 113

GitHub Enterprise administration scenario — Control repository custom-role rollout. In an enterprise development environment: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.

  1. Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval.
  2. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
  3. Use private visibility for restricted proprietary code and grant exact teams explicit repository access.
  4. Split incompatible audit and modification duties into separate permitted roles with documented owners.

Explanation

Correct Answer

D:

Split incompatible audit and modification duties into separate permitted roles with documented owners. Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

Incorrect Answers

A:

Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval. That change would leave the reported problem unresolved: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Split incompatible audit and modification duties into separate permitted roles with documented owners.

B:

Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. That change would leave the reported problem unresolved: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Split incompatible audit and modification duties into separate permitted roles with documented owners.

C:

Use private visibility for restricted proprietary code and grant exact teams explicit repository access. That change would leave the reported problem unresolved: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Split incompatible audit and modification duties into separate permitted roles with documented owners.

Question 114

GitHub Enterprise administration scenario — Control repository custom-role rollout. In an enterprise development environment: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.

  1. Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
  2. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
  3. Inspect the proposed permission matrix and test roles against sample repositories and workflow files.
  4. The vendor accesses the specified repository only and is excluded from unrelated source code.
  5. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

Explanation

Correct Answers

C:

Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. Split incompatible audit and modification duties into separate permitted roles with documented owners.

E:

Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Custom role design must consider each permission's operational effect, not only the label shown to users.

Incorrect Answers

A:

Review branch protections, the available bypass actors and the historical reasons for requested exceptions. It would not provide the evidence needed for the paired diagnosis and follow-up: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

B:

Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. It would not provide the evidence needed for the paired diagnosis and follow-up: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Inspect the proposed permission matrix and test roles against sample repositories and workflow files. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

D:

The vendor accesses the specified repository only and is excluded from unrelated source code. It would not verify whether the proposed change works: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. Split incompatible audit and modification duties into separate permitted roles with documented owners.

Question 115

GitHub Enterprise administration scenario — Control repository custom-role rollout. In an enterprise development environment: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.

  1. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.
  2. A personal account reaches protected repositories only after the required linked SSO authentication flow.
  3. Repository access through a team must be verified at the effective permission level and scoped by the owner.
  4. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.
  5. Custom role design must consider each permission's operational effect, not only the label shown to users.
  6. Split incompatible audit and modification duties into separate permitted roles with documented owners.

Explanation

Correct Answers

A:

Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. Split incompatible audit and modification duties into separate permitted roles with documented owners. Custom role design must consider each permission's operational effect, not only the label shown to users.

E:

Custom role design must consider each permission's operational effect, not only the label shown to users. Split incompatible audit and modification duties into separate permitted roles with documented owners. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

F:

Split incompatible audit and modification duties into separate permitted roles with documented owners. Custom role design must consider each permission's operational effect, not only the label shown to users. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

Incorrect Answers

B:

A personal account reaches protected repositories only after the required linked SSO authentication flow. It would not independently demonstrate that the control works: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. Split incompatible audit and modification duties into separate permitted roles with documented owners.

C:

Repository access through a team must be verified at the effective permission level and scoped by the owner. It is not the rule that supports the proposed change and acceptance test: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Custom role design must consider each permission's operational effect, not only the label shown to users. Split incompatible audit and modification duties into separate permitted roles with documented owners.

D:

Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. It does not implement the governing rule for this approval: An enterprise administrator proposes a reusable custom role that combines repository security visibility with workflow modification capabilities for auditors. Split incompatible audit and modification duties into separate permitted roles with documented owners. Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.

Question 116

GitHub Enterprise administration scenario — Investigate anomalous team invitations. In an enterprise development environment: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.

  1. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.
  2. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk.
  3. SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU.
  4. Custom role design must consider each permission's operational effect, not only the label shown to users.

Explanation

Correct Answer

A:

Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

Incorrect Answers

B:

Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk. It does not govern the condition described: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.

C:

SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU. It does not govern the condition described: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.

D:

Custom role design must consider each permission's operational effect, not only the label shown to users. It does not govern the condition described: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.

Question 117

GitHub Enterprise administration scenario — Investigate anomalous team invitations. In an enterprise development environment: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
  2. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.
  3. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.
  4. Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions.

Explanation

Correct Answer

C:

Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

Incorrect Answers

A:

Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. That check would not establish the decisive facts for this condition: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.

B:

Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. That check would not establish the decisive facts for this condition: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.

D:

Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions. That check would not establish the decisive facts for this condition: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.

Question 118

GitHub Enterprise administration scenario — Investigate anomalous team invitations. In an enterprise development environment: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.

  1. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.
  2. Split incompatible audit and modification duties into separate permitted roles with documented owners.
  3. Limit bypass to formally approved release or emergency actors and preserve review and audit requirements elsewhere.
  4. Escalate a minimal reviewed exception to the proper policy owner rather than granting enterprise admin rights.

Explanation

Correct Answer

A:

Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Every external invitation maps to an approved business request and unauthorized access is removed.

Incorrect Answers

B:

Split incompatible audit and modification duties into separate permitted roles with documented owners. That change would leave the reported problem unresolved: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

C:

Limit bypass to formally approved release or emergency actors and preserve review and audit requirements elsewhere. That change would leave the reported problem unresolved: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

D:

Escalate a minimal reviewed exception to the proper policy owner rather than granting enterprise admin rights. That change would leave the reported problem unresolved: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

Question 119

GitHub Enterprise administration scenario — Investigate anomalous team invitations. In an enterprise development environment: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.

  1. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.
  2. Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
  3. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.
  4. Every external invitation maps to an approved business request and unauthorized access is removed.
  5. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.

Explanation

Correct Answers

C:

Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Every external invitation maps to an approved business request and unauthorized access is removed. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

D:

Every external invitation maps to an approved business request and unauthorized access is removed. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.

Incorrect Answers

A:

The maintainer can perform assigned edits but cannot alter privileged security or repository settings. It would not verify whether the proposed change works: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Every external invitation maps to an approved business request and unauthorized access is removed. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

B:

Check the organization's token policy, the token's authorization status, scope and associated user's permissions. It would not provide the evidence needed for the paired diagnosis and follow-up: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Every external invitation maps to an approved business request and unauthorized access is removed.

E:

Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. It would not provide the evidence needed for the paired diagnosis and follow-up: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. Every external invitation maps to an approved business request and unauthorized access is removed.

Question 120

GitHub Enterprise administration scenario — Investigate anomalous team invitations. In an enterprise development environment: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.

  1. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
  2. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.
  3. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
  4. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.
  5. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.
  6. Every external invitation maps to an approved business request and unauthorized access is removed.

Explanation

Correct Answers

D:

Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. Every external invitation maps to an approved business request and unauthorized access is removed.

E:

Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. Every external invitation maps to an approved business request and unauthorized access is removed.

F:

Every external invitation maps to an approved business request and unauthorized access is removed. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.

Incorrect Answers

A:

The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership. It would not independently demonstrate that the control works: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Every external invitation maps to an approved business request and unauthorized access is removed. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

B:

Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. It does not implement the governing rule for this approval: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. Every external invitation maps to an approved business request and unauthorized access is removed.

C:

Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. It is not the rule that supports the proposed change and acceptance test: Audit events show unexpected external invitations to a confidential repository just after a newly granted team maintainer role was activated. Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.

GitHub Administration (GH-100) Practice Tests