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 4

Question 30

GitHub Enterprise administration scenario — Require strong two-factor authentication. In an enterprise development environment: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. 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. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.
  2. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk.
  3. All users in the policy population meet the documented authentication requirement while approved service integrations still function.
  4. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.
  5. Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.
  6. A permissions inventory confirms no payments administrative path while analytics work remains available.

Explanation

Correct Answers

A:

Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

B:

Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

C:

All users in the policy population meet the documented authentication requirement while approved service integrations still function. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk.

Incorrect Answers

D:

Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. It is not the rule that supports the proposed change and acceptance test: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.

E:

Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. It does not implement the governing rule for this approval: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

F:

A permissions inventory confirms no payments administrative path while analytics work remains available. It would not independently demonstrate that the control works: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. All users in the policy population meet the documented authentication requirement while approved service integrations still function. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.

Question 31

GitHub Enterprise administration scenario — Evaluate OIDC versus SAML for managed-user SSO. In an enterprise development environment: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. 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 team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
  2. Application permissions must be inventoried and periodically reduced or revoked to their current business purpose.
  3. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
  4. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.

Explanation

Correct Answer

D:

Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

Incorrect Answers

A:

GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. It does not govern the condition described: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.

B:

Application permissions must be inventoried and periodically reduced or revoked to their current business purpose. It does not govern the condition described: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.

C:

Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. It does not govern the condition described: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.

Question 32

GitHub Enterprise administration scenario — Evaluate OIDC versus SAML for managed-user SSO. In an enterprise development environment: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
  2. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.
  3. Inspect enterprise-versus-organization SAML scope, the affected account's linked identity and active authenticated session.
  4. Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions.

Explanation

Correct Answer

B:

Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

Incorrect Answers

A:

Review branch protections, the available bypass actors and the historical reasons for requested exceptions. That check would not establish the decisive facts for this condition: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.

C:

Inspect enterprise-versus-organization SAML scope, the affected account's linked identity and active authenticated session. That check would not establish the decisive facts for this condition: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.

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: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.

Question 33

GitHub Enterprise administration scenario — Evaluate OIDC versus SAML for managed-user SSO. In an enterprise development environment: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. 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 approved provisioning mapping or assignment before testing the managed account sign-in route.
  2. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.
  3. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.
  4. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly.

Explanation

Correct Answer

C:

Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.

Incorrect Answers

A:

Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. That change would leave the reported problem unresolved: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

B:

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: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

D:

Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly. That change would leave the reported problem unresolved: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

Question 34

GitHub Enterprise administration scenario — Evaluate OIDC versus SAML for managed-user SSO. In an enterprise development environment: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. 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 enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.
  2. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.
  3. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.
  4. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.
  5. Review the role's proposed permissions, subscription support and which repositories actually require the access.

Explanation

Correct Answers

B:

Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

C:

Test managed accounts authenticate and access protected repositories under the intended conditional-access controls. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.

Incorrect Answers

A:

Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. It would not provide the evidence needed for the paired diagnosis and follow-up: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.

D:

Removing the user from the IdP group removes the matching GitHub team-granted repository permission. It would not verify whether the proposed change works: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

E:

Review the role's proposed permissions, subscription support and which repositories actually require the access. It would not provide the evidence needed for the paired diagnosis and follow-up: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.

Question 35

GitHub Enterprise administration scenario — Evaluate OIDC versus SAML for managed-user SSO. In an enterprise development environment: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. 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. GitHub repository role selection should grant the narrowest permissions that support the documented work.
  3. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.
  4. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.
  5. Repair the IdP-to-GitHub deprovisioning workflow and test revocation without deleting unrelated accounts.
  6. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.

Explanation

Correct Answers

A:

Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.

C:

Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.

D:

Test managed accounts authenticate and access protected repositories under the intended conditional-access controls. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.

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: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

E:

Repair the IdP-to-GitHub deprovisioning workflow and test revocation without deleting unrelated accounts. It does not implement the governing rule for this approval: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls.

F:

The reviewer can inspect required security settings while write and administrator capabilities remain restricted. It would not independently demonstrate that the control works: An architecture team proposes an OIDC-enabled EMU configuration without assessing the identity provider's capabilities and enterprise migration constraints. Test managed accounts authenticate and access protected repositories under the intended conditional-access controls. Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.

Question 36

GitHub Enterprise administration scenario — Bind team membership to directory groups. In an enterprise development environment: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. 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. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.
  2. External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
  3. Repository access through a team must be verified at the effective permission level and scoped by the owner.
  4. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.

Explanation

Correct Answer

A:

Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

Incorrect Answers

B:

External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. It does not govern the condition described: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.

C:

Repository access through a team must be verified at the effective permission level and scoped by the owner. It does not govern the condition described: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.

D:

Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. It does not govern the condition described: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.

Question 37

GitHub Enterprise administration scenario — Bind team membership to directory groups. In an enterprise development environment: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect direct repository grants, parent and child team membership and inherited permission levels.
  2. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.
  3. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.
  4. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.

Explanation

Correct Answer

B:

Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

Incorrect Answers

A:

Inspect direct repository grants, parent and child team membership and inherited permission levels. That check would not establish the decisive facts for this condition: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.

C:

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: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.

D:

Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. That check would not establish the decisive facts for this condition: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.

Question 38

GitHub Enterprise administration scenario — Bind team membership to directory groups. In an enterprise development environment: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. 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. Repair the IdP-to-GitHub deprovisioning workflow and test revocation without deleting unrelated accounts.
  2. Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval.
  3. Limit bypass to formally approved release or emergency actors and preserve review and audit requirements elsewhere.
  4. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

Explanation

Correct Answer

D:

Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

Incorrect Answers

A:

Repair the IdP-to-GitHub deprovisioning workflow and test revocation without deleting unrelated accounts. That change would leave the reported problem unresolved: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

B:

Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval. That change would leave the reported problem unresolved: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

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: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

Question 39

GitHub Enterprise administration scenario — Bind team membership to directory groups. In an enterprise development environment: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. 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. Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path.
  2. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.
  3. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.
  4. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
  5. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.

Explanation

Correct Answers

B:

Removing the user from the IdP group removes the matching GitHub team-granted repository permission. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.

E:

Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Removing the user from the IdP group removes the matching GitHub team-granted repository permission. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

Incorrect Answers

A:

Check the supported enterprise type, IdP protocol capability, conditional access needs and GitHub's currently supported setup path. It would not provide the evidence needed for the paired diagnosis and follow-up: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

C:

The integration can read only its intended repositories while unauthenticated or excessive token requests fail. It would not verify whether the proposed change works: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Removing the user from the IdP group removes the matching GitHub team-granted repository permission. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

D:

Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. It would not provide the evidence needed for the paired diagnosis and follow-up: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

Question 40

GitHub Enterprise administration scenario — Bind team membership to directory groups. In an enterprise development environment: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. 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. Split incompatible audit and modification duties into separate permitted roles with documented owners.
  2. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
  3. The app no longer has unnecessary access and supported remaining integrations continue to function.
  4. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.
  5. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.
  6. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

Explanation

Correct Answers

B:

Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

E:

Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

F:

Removing the user from the IdP group removes the matching GitHub team-granted repository permission. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.

Incorrect Answers

A:

Split incompatible audit and modification duties into separate permitted roles with documented owners. It does not implement the governing rule for this approval: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. Removing the user from the IdP group removes the matching GitHub team-granted repository permission.

C:

The app no longer has unnecessary access and supported remaining integrations continue to function. It would not independently demonstrate that the control works: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Removing the user from the IdP group removes the matching GitHub team-granted repository permission. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

D:

Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. It is not the rule that supports the proposed change and acceptance test: Directory administrators remove a developer from an engineering group but the corresponding GitHub team still grants production repository write access. Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.

GitHub Administration (GH-100) Practice Tests