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 3

Question 20

GitHub Enterprise administration scenario — Enforce SAML SSO for personal account enterprise. In an enterprise development environment: An organization still uses developers' personal GitHub accounts and wishes to require corporate authentication before access to private repositories. 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. SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU.
  2. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
  3. All users in the policy population meet the documented authentication requirement while approved service integrations still function.
  4. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
  5. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
  6. A personal account reaches protected repositories only after the required linked SSO authentication flow.

Explanation

Correct Answers

A:

SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. A personal account reaches protected repositories only after the required linked SSO authentication flow.

D:

Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU. A personal account reaches protected repositories only after the required linked SSO authentication flow.

F:

A personal account reaches protected repositories only after the required linked SSO authentication flow. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU.

Incorrect Answers

B:

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: An organization still uses developers' personal GitHub accounts and wishes to require corporate authentication before access to private repositories. SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.

C:

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 still uses developers' personal GitHub accounts and wishes to require corporate authentication before access to private repositories. A personal account reaches protected repositories only after the required linked SSO authentication flow. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.

E:

Correct the upstream team permission or membership while preserving unrelated authorized developer access. It does not implement the governing rule for this approval: An organization still uses developers' personal GitHub accounts and wishes to require corporate authentication before access to private repositories. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. A personal account reaches protected repositories only after the required linked SSO authentication flow.

Question 21

GitHub Enterprise administration scenario — Preserve identity recovery during IdP outage. In an enterprise development environment: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. 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. Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.
  3. GitHub repository role selection should grant the narrowest permissions that support the documented work.
  4. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

Explanation

Correct Answer

D:

A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

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: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

B:

Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. It does not govern the condition described: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

C:

GitHub repository role selection should grant the narrowest permissions that support the documented work. It does not govern the condition described: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

Question 22

GitHub Enterprise administration scenario — Preserve identity recovery during IdP outage. In an enterprise development environment: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Review the role's proposed permissions, subscription support and which repositories actually require the access.
  2. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
  3. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
  4. Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions.

Explanation

Correct Answer

C:

Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

Incorrect Answers

A:

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: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.

B:

Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. That check would not establish the decisive facts for this condition: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.

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: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.

Question 23

GitHub Enterprise administration scenario — Preserve identity recovery during IdP outage. In an enterprise development environment: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. 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. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
  2. Split incompatible audit and modification duties into separate permitted roles with documented owners.
  3. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
  4. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

Explanation

Correct Answer

D:

Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.

Incorrect Answers

A:

Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. That change would leave the reported problem unresolved: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

B:

Split incompatible audit and modification duties into separate permitted roles with documented owners. That change would leave the reported problem unresolved: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

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: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

Question 24

GitHub Enterprise administration scenario — Preserve identity recovery during IdP outage. In an enterprise development environment: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. 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. Identify the contributor's real operations and compare them with the available organization and repository roles.
  2. The vendor accesses the specified repository only and is excluded from unrelated source code.
  3. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.
  4. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
  5. Check the target policy's controlling scope, the maintainer's role and the proposed integration's functional need.

Explanation

Correct Answers

C:

Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

D:

Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

Incorrect Answers

A:

Identify the contributor's real operations and compare them with the available organization and repository roles. It would not provide the evidence needed for the paired diagnosis and follow-up: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.

B:

The vendor accesses the specified repository only and is excluded from unrelated source code. It would not verify whether the proposed change works: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

E:

Check the target policy's controlling scope, the maintainer's role and the proposed integration's functional need. It would not provide the evidence needed for the paired diagnosis and follow-up: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.

Question 25

GitHub Enterprise administration scenario — Preserve identity recovery during IdP outage. In an enterprise development environment: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. 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. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.
  2. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.
  3. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.
  4. Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
  5. Internal repository visibility may expose content to a broader permitted enterprise member population than a private repository.
  6. The user returns to their base role and the elevated permission is visible only within approved incident windows.

Explanation

Correct Answers

A:

Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.

B:

A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.

C:

Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.

Incorrect Answers

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: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.

E:

Internal repository visibility may expose content to a broader permitted enterprise member population than a private repository. It is not the rule that supports the proposed change and acceptance test: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

F:

The user returns to their base role and the elevated permission is visible only within approved incident windows. It would not independently demonstrate that the control works: The identity provider becomes unavailable during a companywide SSO rollout and all GitHub enterprise owners use only that same login route. Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions. Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.

Question 26

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. 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 role design must consider each permission's operational effect, not only the label shown to users.
  2. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk.
  3. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
  4. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.

Explanation

Correct Answer

B:

Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.

Incorrect Answers

A:

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 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.

C:

Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. It does not govern the condition described: 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.

D:

Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems. It does not govern the condition described: 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.

Question 27

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. 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. Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions.
  3. Inspect enterprise-versus-organization SAML scope, the affected account's linked identity and active authenticated session.
  4. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.

Explanation

Correct Answer

D:

Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. 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.

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: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.

B:

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: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.

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: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.

Question 28

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. 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. Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.
  2. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
  3. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
  4. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.

Explanation

Correct Answer

A:

Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

Incorrect Answers

B:

Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. That change would leave the reported problem unresolved: 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.

C:

Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. That change would leave the reported problem unresolved: 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.

D:

Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. That change would leave the reported problem unresolved: 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.

Question 29

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. 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 app no longer has unnecessary access and supported remaining integrations continue to function.
  2. Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
  3. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.
  4. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
  5. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

Explanation

Correct Answers

C:

Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. 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.

E:

All users in the policy population meet the documented authentication requirement while approved service integrations still function. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. Enterprise authentication policy and user-level multifactor protection address different portions of account compromise risk.

Incorrect Answers

A:

The app no longer has unnecessary access and supported remaining integrations continue to function. It would not verify whether the proposed change 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.

B:

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 large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

D:

Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. It would not provide the evidence needed for the paired diagnosis and follow-up: A large organization has SAML integration but some permitted GitHub users have no second factor enrolled for account access. Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. All users in the policy population meet the documented authentication requirement while approved service integrations still function.

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.

GitHub Administration (GH-100) Practice Tests