Microsoft GH-100 Practice Test 5
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.
- Split incompatible audit and modification duties into separate permitted roles with documented owners.
- Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
- The app no longer has unnecessary access and supported remaining integrations continue to function.
- Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.
- 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.
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.
Question 41
GitHub Enterprise administration scenario — Differentiate SCIM provisioning from team synchronization. In an enterprise development environment: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. 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.
- Custom role design must consider each permission's operational effect, not only the label shown to users.
- Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
- Internal repository visibility may expose content to a broader permitted enterprise member population than a private repository.
- Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
Explanation
Correct Answer
D:Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
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 GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
B:Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. It does not govern the condition described: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
C:Internal repository visibility may expose content to a broader permitted enterprise member population than a private repository. It does not govern the condition described: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
Question 42
GitHub Enterprise administration scenario — Differentiate SCIM provisioning from team synchronization. In an enterprise development environment: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
- Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
- Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
- Review the role's proposed permissions, subscription support and which repositories actually require the access.
Explanation
Correct Answer
B:Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
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: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
C:Compare the contract scope, invitation type, repository permissions and external collaborator inventory. That check would not establish the decisive facts for this condition: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
D: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: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
Question 43
GitHub Enterprise administration scenario — Differentiate SCIM provisioning from team synchronization. In an enterprise development environment: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. 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.
- Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
- Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
- Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
- Limit bypass to formally approved release or emergency actors and preserve review and audit requirements elsewhere.
Explanation
Correct Answer
C:Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. A new employee receives an account and approved team access, while termination removes both without manual intervention.
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: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
B:Revoke the expired elevation and use a documented temporary access workflow for later emergencies. That change would leave the reported problem unresolved: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
D:Limit bypass to formally approved release or emergency actors and preserve review and audit requirements elsewhere. That change would leave the reported problem unresolved: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
Question 44
GitHub Enterprise administration scenario — Differentiate SCIM provisioning from team synchronization. In an enterprise development environment: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. 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.
- Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
- Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
- A new employee receives an account and approved team access, while termination removes both without manual intervention.
- The user returns to their base role and the elevated permission is visible only within approved incident windows.
- Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
Explanation
Correct Answers
C:A new employee receives an account and approved team access, while termination removes both without manual intervention. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
E:Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. A new employee receives an account and approved team access, while termination removes both without manual intervention. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
Incorrect Answers
A:Review branch protections, the available bypass actors and the historical reasons for requested exceptions. It would not provide the evidence needed for the paired diagnosis and follow-up: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. A new employee receives an account and approved team access, while termination removes both without manual intervention.
B: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: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. A new employee receives an account and approved team access, while termination removes both without manual intervention.
D:The user returns to their base role and the elevated permission is visible only within approved incident windows. It would not verify whether the proposed change works: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. A new employee receives an account and approved team access, while termination removes both without manual intervention. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
Question 45
GitHub Enterprise administration scenario — Differentiate SCIM provisioning from team synchronization. In an enterprise development environment: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. 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.
- Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
- Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.
- A new employee receives an account and approved team access, while termination removes both without manual intervention.
- Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.
- Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
- Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
Explanation
Correct Answers
A:Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems. A new employee receives an account and approved team access, while termination removes both without manual intervention.
C:A new employee receives an account and approved team access, while termination removes both without manual intervention. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems.
E:Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. A new employee receives an account and approved team access, while termination removes both without manual intervention.
Incorrect Answers
B:Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change. It is not the rule that supports the proposed change and acceptance test: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Provisioning accounts via SCIM and synchronizing organizational team membership solve different identity-management problems. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
D:Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. It would not independently demonstrate that the control works: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. A new employee receives an account and approved team access, while termination removes both without manual intervention. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
F:Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. It does not implement the governing rule for this approval: A GitHub admin treats successful team synchronization as proof that managed user accounts will be created and disabled automatically. Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. A new employee receives an account and approved team access, while termination removes both without manual intervention.
Question 46
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. 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.
- For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
- Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
- An interactive SAML session does not automatically authorize all token-based API access to protected organizations.
- Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
Explanation
Correct Answer
C:An interactive SAML session does not automatically authorize all token-based API access to protected organizations. Check the organization's token policy, the token's authorization status, scope and associated user's permissions. Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.
Incorrect Answers
A:For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. It does not govern the condition described: 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.
B:Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. It does not govern the condition described: 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.
D:Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification. It does not govern the condition described: 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.
Question 47
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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
- Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
- Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
- Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.
Explanation
Correct Answer
C:Check the organization's token policy, the token's authorization status, scope and associated user's permissions. 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.
Incorrect Answers
A:Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. That check would not establish the decisive facts for this condition: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
B: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 user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
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: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
Question 48
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. 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.
- Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.
- Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.
- Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval.
- Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.
Explanation
Correct Answer
B:Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. Check the organization's token policy, the token's authorization status, scope and associated user's permissions. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.
Incorrect Answers
A:Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail. That change would leave the reported problem unresolved: 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.
C:Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval. That change would leave the reported problem unresolved: 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.
D:Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot. That change would leave the reported problem unresolved: 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.
Question 49
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. 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.
- Check the organization's token policy, the token's authorization status, scope and associated user's permissions.
- The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
- Inspect installed application grants, last activity, repository selections and the pilot's closeout record.
- Check the target policy's controlling scope, the maintainer's role and the proposed integration's functional need.
- The integration can read only its intended repositories while unauthenticated or excessive token requests fail.
Explanation
Correct Answers
A:Check the organization's token policy, the token's authorization status, scope and associated user's permissions. 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.
E:The integration can read only its intended repositories while unauthenticated or excessive token requests fail. Check the organization's token policy, the token's authorization status, scope and associated user's permissions. An interactive SAML session does not automatically authorize all token-based API access to protected organizations.
Incorrect Answers
B:The contractor retains only the approved repository permissions and owner membership is limited to designated staff. It would not verify whether the proposed change 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.
C:Inspect installed application grants, last activity, repository selections and the pilot's closeout record. It would not provide the evidence needed for the paired diagnosis and follow-up: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. Check the organization's token policy, the token's authorization status, scope and associated user's permissions. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.
D: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: A user's browser SSO login succeeds, yet an automation tool using a personal access token cannot read an SSO-protected private repository. Check the organization's token policy, the token's authorization status, scope and associated user's permissions. The integration can read only its intended repositories while unauthenticated or excessive token requests fail.
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.
- 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.
- GitHub repository role selection should grant the narrowest permissions that support the documented work.
- All users in the policy population meet the documented authentication requirement while approved service integrations still function.
- 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.