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 6

Question 50

GitHub Enterprise administration scenario — Authorize personal-access tokens for SAML-protected resources. In an enterprise development environment: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. 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. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.
  2. An interactive SAML session does not automatically authorize all token-based API access to protected organizations.
  3. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.
  4. GitHub repository role selection should grant the narrowest permissions that support the documented work.
  5. All users in the policy population meet the documented authentication requirement while approved service integrations still function.
  6. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

Explanation

Correct Answers

A:

Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. An interactive SAML session does not automatically authorize all token-based API access to protected organizations. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.

B:

An interactive SAML session does not automatically authorize all token-based API access to protected organizations. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.

C:

The integration can read only its intended repositories while unauthenticated or excessive token requests fail. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. An interactive SAML session does not automatically authorize all token-based API access to protected organizations.

Incorrect Answers

D:

GitHub repository role selection should grant the narrowest permissions that support the documented work. It is not the rule that supports the proposed change and acceptance test: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. An interactive SAML session does not automatically authorize all token-based API access to protected organizations. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.

E:

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: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. The integration can read only its intended repositories while unauthenticated or excessive token requests fail. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.

F:

Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. It does not implement the governing rule for this approval: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.

Question 51

GitHub Enterprise administration scenario — Assign repository roles using least privilege. In an enterprise development environment: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. 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. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
  2. External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
  3. Custom role design must consider each permission's operational effect, not only the label shown to users.
  4. GitHub repository role selection should grant the narrowest permissions that support the documented work.

Explanation

Correct Answer

D:

GitHub repository role selection should grant the narrowest permissions that support the documented work. Identify the contributor's real operations and compare them with the available organization and repository roles. Replace admin access with the lowest suitable role and confirm that required content changes still work.

Incorrect Answers

A:

A transfer requires reviewing both team-based grants and direct repository or organization role assignments. It does not govern the condition described: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. GitHub repository role selection should grant the narrowest permissions that support the documented work.

B:

External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. It does not govern the condition described: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. GitHub repository role selection should grant the narrowest permissions that support the documented work.

C:

Custom role design must consider each permission's operational effect, not only the label shown to users. It does not govern the condition described: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. GitHub repository role selection should grant the narrowest permissions that support the documented work.

Question 52

GitHub Enterprise administration scenario — Assign repository roles using least privilege. In an enterprise development environment: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect the intended reader population and the enterprise's repository visibility and access policies.
  2. Identify the contributor's real operations and compare them with the available organization and repository roles.
  3. Compare the team's requested permission with the resulting repository grant and any inherited role or organization default.
  4. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.

Explanation

Correct Answer

B:

Identify the contributor's real operations and compare them with the available organization and repository roles. GitHub repository role selection should grant the narrowest permissions that support the documented work. Replace admin access with the lowest suitable role and confirm that required content changes still work.

Incorrect Answers

A:

Inspect the intended reader population and the enterprise's repository visibility and access policies. That check would not establish the decisive facts for this condition: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Identify the contributor's real operations and compare them with the available organization and repository roles.

C:

Compare the team's requested permission with the resulting repository grant and any inherited role or organization default. That check would not establish the decisive facts for this condition: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Identify the contributor's real operations and compare them with the available organization and repository roles.

D:

Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. That check would not establish the decisive facts for this condition: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Identify the contributor's real operations and compare them with the available organization and repository roles.

Question 53

GitHub Enterprise administration scenario — Assign repository roles using least privilege. In an enterprise development environment: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. 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. Correct the team repository permission and document the least-privilege approval for the repository owner.
  2. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
  3. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
  4. Replace admin access with the lowest suitable role and confirm that required content changes still work.

Explanation

Correct Answer

D:

Replace admin access with the lowest suitable role and confirm that required content changes still work. Identify the contributor's real operations and compare them with the available organization and repository roles. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.

Incorrect Answers

A:

Correct the team repository permission and document the least-privilege approval for the repository owner. That change would leave the reported problem unresolved: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Replace admin access with the lowest suitable role and confirm that required content changes still work.

B:

Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. That change would leave the reported problem unresolved: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Replace admin access with the lowest suitable role and confirm that required content changes still work.

C:

Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. That change would leave the reported problem unresolved: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Replace admin access with the lowest suitable role and confirm that required content changes still work.

Question 54

GitHub Enterprise administration scenario — Assign repository roles using least privilege. In an enterprise development environment: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. 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. Inspect direct repository grants, parent and child team membership and inherited permission levels.
  2. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
  3. Identify the contributor's real operations and compare them with the available organization and repository roles.
  4. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.
  5. Inspect the intended reader population and the enterprise's repository visibility and access policies.

Explanation

Correct Answers

C:

Identify the contributor's real operations and compare them with the available organization and repository roles. The maintainer can perform assigned edits but cannot alter privileged security or repository settings. Replace admin access with the lowest suitable role and confirm that required content changes still work.

D:

The maintainer can perform assigned edits but cannot alter privileged security or repository settings. Identify the contributor's real operations and compare them with the available organization and repository roles. GitHub repository role selection should grant the narrowest permissions that support the documented work.

Incorrect Answers

A:

Inspect direct repository grants, parent and child team membership and inherited permission levels. It would not provide the evidence needed for the paired diagnosis and follow-up: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Identify the contributor's real operations and compare them with the available organization and repository roles. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.

B:

A test user gets the correct rights in the correct organization without accidental cross-subsidiary access. It would not verify whether the proposed change works: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. The maintainer can perform assigned edits but cannot alter privileged security or repository settings. Replace admin access with the lowest suitable role and confirm that required content changes still work.

E:

Inspect the intended reader population and the enterprise's repository visibility and access policies. It would not provide the evidence needed for the paired diagnosis and follow-up: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Identify the contributor's real operations and compare them with the available organization and repository roles. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.

Question 55

GitHub Enterprise administration scenario — Assign repository roles using least privilege. In an enterprise development environment: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. 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 maintainer can perform assigned edits but cannot alter privileged security or repository settings.
  2. Replace admin access with the lowest suitable role and confirm that required content changes still work.
  3. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
  4. GitHub repository role selection should grant the narrowest permissions that support the documented work.
  5. SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU.
  6. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

Explanation

Correct Answers

A:

The maintainer can perform assigned edits but cannot alter privileged security or repository settings. Replace admin access with the lowest suitable role and confirm that required content changes still work. GitHub repository role selection should grant the narrowest permissions that support the documented work.

B:

Replace admin access with the lowest suitable role and confirm that required content changes still work. GitHub repository role selection should grant the narrowest permissions that support the documented work. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.

D:

GitHub repository role selection should grant the narrowest permissions that support the documented work. Replace admin access with the lowest suitable role and confirm that required content changes still work. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.

Incorrect Answers

C:

Correct the upstream team permission or membership while preserving unrelated authorized developer access. It does not implement the governing rule for this approval: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. Replace admin access with the lowest suitable role and confirm that required content changes still work. The maintainer can perform assigned edits but cannot alter privileged security or repository settings.

E:

SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU. It is not the rule that supports the proposed change and acceptance test: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. GitHub repository role selection should grant the narrowest permissions that support the documented work. Replace admin access with the lowest suitable role and confirm that required content changes still work.

F:

Removing the user from the IdP group removes the matching GitHub team-granted repository permission. It would not independently demonstrate that the control works: A documentation maintainer is granted repository admin rights merely to edit Markdown files and request reviews. The maintainer can perform assigned edits but cannot alter privileged security or repository settings. Replace admin access with the lowest suitable role and confirm that required content changes still work.

Question 56

GitHub Enterprise administration scenario — Use custom organization repository roles appropriately. In an enterprise development environment: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. 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. GitHub repository role selection should grant the narrowest permissions that support the documented work.
  2. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
  3. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
  4. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

Explanation

Correct Answer

B:

Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. Review the role's proposed permissions, subscription support and which repositories actually require the access. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

Incorrect Answers

A:

GitHub repository role selection should grant the narrowest permissions that support the documented work. It does not govern the condition described: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.

C:

A transfer requires reviewing both team-based grants and direct repository or organization role assignments. It does not govern the condition described: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.

D:

A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. It does not govern the condition described: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.

Question 57

GitHub Enterprise administration scenario — Use custom organization repository roles appropriately. In an enterprise development environment: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
  2. Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
  3. Review the role's proposed permissions, subscription support and which repositories actually require the access.
  4. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.

Explanation

Correct Answer

C:

Review the role's proposed permissions, subscription support and which repositories actually require the access. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

Incorrect Answers

A:

Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. That check would not establish the decisive facts for this condition: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Review the role's proposed permissions, subscription support and which repositories actually require the access.

B:

Check the organization's token policy, the token's authorization status, scope and associated user's permissions. That check would not establish the decisive facts for this condition: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Review the role's proposed permissions, subscription support and which repositories actually require the access.

D:

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: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Review the role's proposed permissions, subscription support and which repositories actually require the access.

Question 58

GitHub Enterprise administration scenario — Use custom organization repository roles appropriately. In an enterprise development environment: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. 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. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
  3. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
  4. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.

Explanation

Correct Answer

C:

Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. Review the role's proposed permissions, subscription support and which repositories actually require the access. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

Incorrect Answers

A:

Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. That change would leave the reported problem unresolved: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

B:

Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. That change would leave the reported problem unresolved: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

D:

Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. That change would leave the reported problem unresolved: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

Question 59

GitHub Enterprise administration scenario — Use custom organization repository roles appropriately. In an enterprise development environment: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. 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. Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
  2. Review the role's proposed permissions, subscription support and which repositories actually require the access.
  3. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.
  4. Compare the incident approval and duration with current repository roles and relevant audit events.
  5. The build obtains only necessary approved functionality while mandatory enterprise policy remains enforced.

Explanation

Correct Answers

B:

Review the role's proposed permissions, subscription support and which repositories actually require the access. The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

C:

The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Review the role's proposed permissions, subscription support and which repositories actually require the access. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.

Incorrect Answers

A:

Compare the contract scope, invitation type, repository permissions and external collaborator inventory. It would not provide the evidence needed for the paired diagnosis and follow-up: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Review the role's proposed permissions, subscription support and which repositories actually require the access. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

D:

Compare the incident approval and duration with current repository roles and relevant audit events. It would not provide the evidence needed for the paired diagnosis and follow-up: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Review the role's proposed permissions, subscription support and which repositories actually require the access. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

E:

The build obtains only necessary approved functionality while mandatory enterprise policy remains enforced. It would not verify whether the proposed change works: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

Question 60

GitHub Enterprise administration scenario — Use custom organization repository roles appropriately. In an enterprise development environment: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. 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 reviewer can inspect required security settings while write and administrator capabilities remain restricted.
  2. GitHub repository role selection should grant the narrowest permissions that support the documented work.
  3. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
  4. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
  5. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
  6. The terminated user cannot access any in-scope enterprise repository and audit records show the accountable disablement.

Explanation

Correct Answers

A:

The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.

C:

Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

E:

Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

Incorrect Answers

B:

GitHub repository role selection should grant the narrowest permissions that support the documented work. It is not the rule that supports the proposed change and acceptance test: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

D:

Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. It does not implement the governing rule for this approval: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

F:

The terminated user cannot access any in-scope enterprise repository and audit records show the accountable disablement. It would not independently demonstrate that the control works: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

GitHub Administration (GH-100) Practice Tests