Microsoft GH-100 Practice Test 1
Question 1
GitHub Enterprise administration scenario — Select Enterprise Managed Users for centrally owned identities. In an enterprise development environment: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. 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.
- Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
- Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
- Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
- Managed-account offboarding must revoke the GitHub account lifecycle through the configured IdP provisioning channel.
Explanation
Correct Answer
B:Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
Incorrect Answers
A:Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. It does not govern the condition described: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
C:Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. It does not govern the condition described: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
D:Managed-account offboarding must revoke the GitHub account lifecycle through the configured IdP provisioning channel. It does not govern the condition described: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
Question 2
GitHub Enterprise administration scenario — Select Enterprise Managed Users for centrally owned identities. In an enterprise development environment: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect direct repository grants, parent and child team membership and inherited permission levels.
- Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
- Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
- Inspect installed application grants, last activity, repository selections and the pilot's closeout record.
Explanation
Correct Answer
C:Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
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 regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
B:Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. That check would not establish the decisive facts for this condition: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
D:Inspect installed application grants, last activity, repository selections and the pilot's closeout record. That check would not establish the decisive facts for this condition: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
Question 3
GitHub Enterprise administration scenario — Select Enterprise Managed Users for centrally owned identities. In an enterprise development environment: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. 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.
- Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
- Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
- Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
- Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
Explanation
Correct Answer
B:Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
Incorrect Answers
A:Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider. That change would leave the reported problem unresolved: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
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 regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
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 regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
Question 4
GitHub Enterprise administration scenario — Select Enterprise Managed Users for centrally owned identities. In an enterprise development environment: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. 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.
- A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
- Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events.
- The maintainer can perform assigned edits but cannot alter privileged security or repository settings.
- Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
- Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
Explanation
Correct Answers
A:A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
D:Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
Incorrect Answers
B:Inspect the organization or enterprise team-sync configuration, the mapped IdP group and the affected team membership audit events. It would not provide the evidence needed for the paired diagnosis and follow-up: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
C:The maintainer can perform assigned edits but cannot alter privileged security or repository settings. It would not verify whether the proposed change works: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
E:Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests. It would not provide the evidence needed for the paired diagnosis and follow-up: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
Question 5
GitHub Enterprise administration scenario — Select Enterprise Managed Users for centrally owned identities. In an enterprise development environment: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. 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.
- Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
- Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.
- A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
- Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
- Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy.
- Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval.
Explanation
Correct Answers
A:Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
C:A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise.
D:Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
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 regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Enterprise Managed Users delegates account lifecycle to the enterprise identity provider and restricts collaboration outside the enterprise. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
E:Audit-only users inspect findings but cannot edit workflows, secrets or protected branch policy. It would not independently demonstrate that the control works: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan.
F:Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval. It does not implement the governing rule for this approval: A regulated software company wants its identity provider to own account creation and removal, but its pilot developers currently use their personal GitHub accounts. Choose an EMU enterprise only after confirming collaboration restrictions and an IdP-driven provisioning migration plan. A test employee is provisioned and disabled from the IdP while required internal repository access works and prohibited external collaboration remains blocked.
Question 6
GitHub Enterprise administration scenario — Repair SCIM provisioning of a new managed user. In an enterprise development environment: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. 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.
- 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.
- External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
Explanation
Correct Answer
B:For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
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: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
C:Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. It does not govern the condition described: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
D:External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. It does not govern the condition described: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
Question 7
GitHub Enterprise administration scenario — Repair SCIM provisioning of a new managed user. In an enterprise development environment: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
- Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions.
- Check the target policy's controlling scope, the maintainer's role and the proposed integration's functional need.
- Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
Explanation
Correct Answer
A:Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
Incorrect Answers
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: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
C:Check the target policy's controlling scope, the maintainer's role and the proposed integration's functional need. That check would not establish the decisive facts for this condition: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
D: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: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
Question 8
GitHub Enterprise administration scenario — Repair SCIM provisioning of a new managed user. In an enterprise development environment: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. 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.
- Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval.
- Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
- Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
- Split incompatible audit and modification duties into separate permitted roles with documented owners.
Explanation
Correct Answer
B:Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
Incorrect Answers
A:Uninstall the unused integration or reduce its granted permissions and repositories with affected owners' approval. That change would leave the reported problem unresolved: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
C:Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. That change would leave the reported problem unresolved: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
D:Split incompatible audit and modification duties into separate permitted roles with documented owners. That change would leave the reported problem unresolved: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
Question 9
GitHub Enterprise administration scenario — Repair SCIM provisioning of a new managed user. In an enterprise development environment: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. 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.
- Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
- Nonmembers cannot read the private repository while approved project participants retain access.
- The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
- Compare the incident approval and duration with current repository roles and relevant audit events.
- Inspect the proposed permission matrix and test roles against sample repositories and workflow files.
Explanation
Correct Answers
A:Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
C:The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
Incorrect Answers
B:Nonmembers cannot read the private repository while approved project participants retain access. It would not verify whether the proposed change works: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
D:Compare the incident approval and duration with current repository roles and relevant audit events. It would not provide the evidence needed for the paired diagnosis and follow-up: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
E:Inspect the proposed permission matrix and test roles against sample repositories and workflow files. It would not provide the evidence needed for the paired diagnosis and follow-up: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
Question 10
GitHub Enterprise administration scenario — Repair SCIM provisioning of a new managed user. In an enterprise development environment: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. 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.
- Document and exercise GitHub-supported recovery controls with restricted emergency access and a time-limited audit trail.
- The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
- Team members have only the intended read capability across all reviewed repositories.
- For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
- Unexpected invitations demand attribution and effective-access review rather than assuming a legitimate team change.
- Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
Explanation
Correct Answers
B:The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
D:For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
F:Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
Incorrect Answers
A: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: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership.
C:Team members have only the intended read capability across all reviewed repositories. It would not independently demonstrate that the control works: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. The employee's identity is created by SCIM, signs in through the IdP and receives only intended enterprise membership. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.
E: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: An employee authenticates to the corporate identity provider, but no managed GitHub account appears after the approved onboarding step. For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. Correct the approved provisioning mapping or assignment before testing the managed account sign-in route.