Microsoft GH-100 Practice Test 9
Question 80
GitHub Enterprise administration scenario — Coordinate enterprise-level team and organization boundaries. In an enterprise development environment: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their 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.
- Correct the upstream team permission or membership while preserving unrelated authorized developer access.
- Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
- A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
- For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions.
- Nonmembers cannot read the private repository while approved project participants retain access.
- Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly.
Explanation
Correct Answers
B:Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
C:A test user gets the correct rights in the correct organization without accidental cross-subsidiary access. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
F:Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
Incorrect Answers
A:Correct the upstream team permission or membership while preserving unrelated authorized developer access. It does not implement the governing rule for this approval: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
D:For Enterprise Managed Users, authentication and SCIM-based account provisioning are separate identity lifecycle functions. It is not the rule that supports the proposed change and acceptance test: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly.
E:Nonmembers cannot read the private repository while approved project participants retain access. It would not independently demonstrate that the control works: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly.
Question 81
GitHub Enterprise administration scenario — Remove stale repository permissions after job rotation. In an enterprise development environment: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. 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.
- GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
- SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU.
- A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
Explanation
Correct Answer
D:A transfer requires reviewing both team-based grants and direct repository or organization role assignments. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. Remove historical grants and assign the new role using a formally approved least-privilege review.
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 engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
B:GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. It does not govern the condition described: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
C:SAML SSO for personal-account organizations binds enterprise resource access to IdP authentication without converting accounts to EMU. It does not govern the condition described: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
Question 82
GitHub Enterprise administration scenario — Remove stale repository permissions after job rotation. In an enterprise development environment: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.
- Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
- Inspect installed application grants, last activity, repository selections and the pilot's closeout record.
- Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
Explanation
Correct Answer
A:Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. A transfer requires reviewing both team-based grants and direct repository or organization role assignments. Remove historical grants and assign the new role using a formally approved least-privilege review.
Incorrect Answers
B:Review branch protections, the available bypass actors and the historical reasons for requested exceptions. That check would not establish the decisive facts for this condition: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.
C: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: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.
D:Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. That check would not establish the decisive facts for this condition: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.
Question 83
GitHub Enterprise administration scenario — Remove stale repository permissions after job rotation. In an enterprise development environment: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. 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.
- Remove historical grants and assign the new role using a formally approved least-privilege review.
- Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
- Use private visibility for restricted proprietary code and grant exact teams explicit repository access.
- Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement.
Explanation
Correct Answer
A:Remove historical grants and assign the new role using a formally approved least-privilege review. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. A permissions inventory confirms no payments administrative path while analytics work remains available.
Incorrect Answers
B: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: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Remove historical grants and assign the new role using a formally approved least-privilege review.
C:Use private visibility for restricted proprietary code and grant exact teams explicit repository access. That change would leave the reported problem unresolved: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Remove historical grants and assign the new role using a formally approved least-privilege review.
D:Require supported 2FA or equivalent approved controls and resolve exceptions before applying blanket enforcement. That change would leave the reported problem unresolved: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Remove historical grants and assign the new role using a formally approved least-privilege review.
Question 84
GitHub Enterprise administration scenario — Remove stale repository permissions after job rotation. In an enterprise development environment: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. 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.
- Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.
- The maintainer can perform assigned edits but cannot alter privileged security or repository settings.
- Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions.
- Review the role's proposed permissions, subscription support and which repositories actually require the access.
- A permissions inventory confirms no payments administrative path while analytics work remains available.
Explanation
Correct Answers
C:Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. A permissions inventory confirms no payments administrative path while analytics work remains available. Remove historical grants and assign the new role using a formally approved least-privilege review.
E:A permissions inventory confirms no payments administrative path while analytics work remains available. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
Incorrect Answers
A:Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. It would not provide the evidence needed for the paired diagnosis and follow-up: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. A permissions inventory confirms no payments administrative path while analytics work remains available.
B:The maintainer can perform assigned edits but cannot alter privileged security or repository settings. It would not verify whether the proposed change works: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. A permissions inventory confirms no payments administrative path while analytics work remains available. Remove historical grants and assign the new role using a formally approved least-privilege review.
D:Review the role's proposed permissions, subscription support and which repositories actually require the access. It would not provide the evidence needed for the paired diagnosis and follow-up: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Reconcile the employee's new responsibilities against effective team grants, invitations and direct repository permissions. A permissions inventory confirms no payments administrative path while analytics work remains available.
Question 85
GitHub Enterprise administration scenario — Remove stale repository permissions after job rotation. In an enterprise development environment: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments 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.
- Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.
- Ordinary contributors cannot bypass main-branch safeguards and an approved emergency is attributable.
- Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
- Remove historical grants and assign the new role using a formally approved least-privilege review.
- A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
- A permissions inventory confirms no payments administrative path while analytics work remains available.
Explanation
Correct Answers
D:Remove historical grants and assign the new role using a formally approved least-privilege review. A transfer requires reviewing both team-based grants and direct repository or organization role assignments. A permissions inventory confirms no payments administrative path while analytics work remains available.
E:A transfer requires reviewing both team-based grants and direct repository or organization role assignments. Remove historical grants and assign the new role using a formally approved least-privilege review. A permissions inventory confirms no payments administrative path while analytics work remains available.
F:A permissions inventory confirms no payments administrative path while analytics work remains available. Remove historical grants and assign the new role using a formally approved least-privilege review. A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
Incorrect Answers
A:Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. It is not the rule that supports the proposed change and acceptance test: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. A transfer requires reviewing both team-based grants and direct repository or organization role assignments. Remove historical grants and assign the new role using a formally approved least-privilege review.
B:Ordinary contributors cannot bypass main-branch safeguards and an approved emergency is attributable. It would not independently demonstrate that the control works: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. A permissions inventory confirms no payments administrative path while analytics work remains available. Remove historical grants and assign the new role using a formally approved least-privilege review.
C: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: An engineer transfers from payments to analytics and loses payments team membership in the HR system but keeps direct admin access to payments repositories. Remove historical grants and assign the new role using a formally approved least-privilege review. A permissions inventory confirms no payments administrative path while analytics work remains available.
Question 86
GitHub Enterprise administration scenario — Expire temporary release-manager rights. In an enterprise development environment: A support engineer was given elevated production repository permissions for one incident and retains them a month later. 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.
- Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent.
- Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
- GitHub repository role selection should grant the narrowest permissions that support the documented work.
Explanation
Correct Answer
A:Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. Compare the incident approval and duration with current repository roles and relevant audit events. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
Incorrect Answers
B:Team synchronization must be deliberately configured to keep a supported IdP group and GitHub team membership consistent. It does not govern the condition described: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
C:Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. It does not govern the condition described: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
D:GitHub repository role selection should grant the narrowest permissions that support the documented work. It does not govern the condition described: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
Question 87
GitHub Enterprise administration scenario — Expire temporary release-manager rights. In an enterprise development environment: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.
- Inspect enterprise-versus-organization SAML scope, the affected account's linked identity and active authenticated session.
- Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
- Compare the incident approval and duration with current repository roles and relevant audit events.
Explanation
Correct Answer
D:Compare the incident approval and duration with current repository roles and relevant audit events. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
Incorrect Answers
A:Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations. That check would not establish the decisive facts for this condition: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Compare the incident approval and duration with current repository roles and relevant audit events.
B: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 support engineer was given elevated production repository permissions for one incident and retains them a month later. Compare the incident approval and duration with current repository roles and relevant audit events.
C: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 support engineer was given elevated production repository permissions for one incident and retains them a month later. Compare the incident approval and duration with current repository roles and relevant audit events.
Question 88
GitHub Enterprise administration scenario — Expire temporary release-manager rights. In an enterprise development environment: A support engineer was given elevated production repository permissions for one incident and retains them a month later. 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.
- Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
- Repair the IdP-to-GitHub deprovisioning workflow and test revocation without deleting unrelated accounts.
- Select the supported managed-user SSO protocol for the chosen enterprise after a controlled compatibility pilot.
- Replace admin access with the lowest suitable role and confirm that required content changes still work.
Explanation
Correct Answer
A:Revoke the expired elevation and use a documented temporary access workflow for later emergencies. Compare the incident approval and duration with current repository roles and relevant audit events. The user returns to their base role and the elevated permission is visible only within approved incident windows.
Incorrect Answers
B:Repair the IdP-to-GitHub deprovisioning workflow and test revocation without deleting unrelated accounts. That change would leave the reported problem unresolved: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
C: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 support engineer was given elevated production repository permissions for one incident and retains them a month later. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
D:Replace admin access with the lowest suitable role and confirm that required content changes still work. That change would leave the reported problem unresolved: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
Question 89
GitHub Enterprise administration scenario — Expire temporary release-manager rights. In an enterprise development environment: A support engineer was given elevated production repository permissions for one incident and retains them a month later. 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.
- The user returns to their base role and the elevated permission is visible only within approved incident windows.
- Inspect the proposed permission matrix and test roles against sample repositories and workflow files.
- Inspect direct repository grants, parent and child team membership and inherited permission levels.
- Compare the incident approval and duration with current repository roles and relevant audit events.
- The maintainer can perform assigned edits but cannot alter privileged security or repository settings.
Explanation
Correct Answers
A:The user returns to their base role and the elevated permission is visible only within approved incident windows. Compare the incident approval and duration with current repository roles and relevant audit events. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
D:Compare the incident approval and duration with current repository roles and relevant audit events. The user returns to their base role and the elevated permission is visible only within approved incident windows. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
Incorrect Answers
B: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: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Compare the incident approval and duration with current repository roles and relevant audit events. The user returns to their base role and the elevated permission is visible only within approved incident windows.
C:Inspect direct repository grants, parent and child team membership and inherited permission levels. It would not provide the evidence needed for the paired diagnosis and follow-up: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Compare the incident approval and duration with current repository roles and relevant audit events. The user returns to their base role and the elevated permission is visible only within approved incident windows.
E:The maintainer can perform assigned edits but cannot alter privileged security or repository settings. It would not verify whether the proposed change works: A support engineer was given elevated production repository permissions for one incident and retains them a month later. The user returns to their base role and the elevated permission is visible only within approved incident windows. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
Question 90
GitHub Enterprise administration scenario — Expire temporary release-manager rights. In an enterprise development environment: A support engineer was given elevated production repository permissions for one incident and retains them a month later. 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.
- Application permissions must be inventoried and periodically reduced or revoked to their current business purpose.
- Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
- Every external invitation maps to an approved business request and unauthorized access is removed.
- Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
- The user returns to their base role and the elevated permission is visible only within approved incident windows.
- Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
Explanation
Correct Answers
B:Revoke the expired elevation and use a documented temporary access workflow for later emergencies. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. The user returns to their base role and the elevated permission is visible only within approved incident windows.
D:Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. Revoke the expired elevation and use a documented temporary access workflow for later emergencies. The user returns to their base role and the elevated permission is visible only within approved incident windows.
E:The user returns to their base role and the elevated permission is visible only within approved incident windows. Revoke the expired elevation and use a documented temporary access workflow for later emergencies. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege.
Incorrect Answers
A:Application permissions must be inventoried and periodically reduced or revoked to their current business purpose. It is not the rule that supports the proposed change and acceptance test: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Emergency elevation should be scoped, audited and time-limited rather than converted to permanent privilege. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
C:Every external invitation maps to an approved business request and unauthorized access is removed. It would not independently demonstrate that the control works: A support engineer was given elevated production repository permissions for one incident and retains them a month later. The user returns to their base role and the elevated permission is visible only within approved incident windows. Revoke the expired elevation and use a documented temporary access workflow for later emergencies.
F:Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model. It does not implement the governing rule for this approval: A support engineer was given elevated production repository permissions for one incident and retains them a month later. Revoke the expired elevation and use a documented temporary access workflow for later emergencies. The user returns to their base role and the elevated permission is visible only within approved incident windows.