Microsoft GH-100 Practice Test 8
Question 70
GitHub Enterprise administration scenario — Restrict outside collaborators to approved repositories. In an enterprise development environment: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. 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.
- Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
- The maintainer can perform assigned edits but cannot alter privileged security or repository settings.
- External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
- The vendor accesses the specified repository only and is excluded from unrelated source code.
- Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
Explanation
Correct Answers
B:Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. The vendor accesses the specified repository only and is excluded from unrelated source code.
D:External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. The vendor accesses the specified repository only and is excluded from unrelated source code.
E:The vendor accesses the specified repository only and is excluded from unrelated source code. Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
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: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
C:The maintainer can perform assigned edits but cannot alter privileged security or repository settings. It would not independently demonstrate that the control works: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. The vendor accesses the specified repository only and is excluded from unrelated source code. Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
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 vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. The vendor accesses the specified repository only and is excluded from unrelated source code.
Question 71
GitHub Enterprise administration scenario — Review nested team permission inheritance. In an enterprise development environment: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. 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.
- External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
- Enterprise and organization governance controls require authorization from accountable higher-scope policy owners.
- Application permissions must be inventoried and periodically reduced or revoked to their current business purpose.
- GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
Explanation
Correct Answer
D:GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. Inspect direct repository grants, parent and child team membership and inherited permission levels. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
Incorrect Answers
A:External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. It does not govern the condition described: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
B:Enterprise and organization governance controls require authorization from accountable higher-scope policy owners. It does not govern the condition described: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
C:Application permissions must be inventoried and periodically reduced or revoked to their current business purpose. It does not govern the condition described: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
Question 72
GitHub Enterprise administration scenario — Review nested team permission inheritance. In an enterprise development environment: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. 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.
- Check the target policy's controlling scope, the maintainer's role and the proposed integration's functional need.
- Review the role's proposed permissions, subscription support and which repositories actually require the access.
Explanation
Correct Answer
A:Inspect direct repository grants, parent and child team membership and inherited permission levels. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
Incorrect Answers
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 developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Inspect direct repository grants, parent and child team membership and inherited permission levels.
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: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Inspect direct repository grants, parent and child team membership and inherited permission levels.
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 developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Inspect direct repository grants, parent and child team membership and inherited permission levels.
Question 73
GitHub Enterprise administration scenario — Review nested team permission inheritance. In an enterprise development environment: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. 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.
- Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
- Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
- Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
- Correct the upstream team permission or membership while preserving unrelated authorized developer access.
Explanation
Correct Answer
D:Correct the upstream team permission or membership while preserving unrelated authorized developer access. Inspect direct repository grants, parent and child team membership and inherited permission levels. A privilege review shows the developer no longer has write access through any team path.
Incorrect Answers
A:Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. That change would leave the reported problem unresolved: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
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: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
C: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 developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
Question 74
GitHub Enterprise administration scenario — Review nested team permission inheritance. In an enterprise development environment: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. 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 privilege review shows the developer no longer has write access through any team path.
- Correlate invite actor, target repository, team permissions, approved tickets and accepted invitations.
- Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions.
- Identify the contributor's real operations and compare them with the available organization and repository roles.
- Inspect direct repository grants, parent and child team membership and inherited permission levels.
Explanation
Correct Answers
A:A privilege review shows the developer no longer has write access through any team path. Inspect direct repository grants, parent and child team membership and inherited permission levels. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
E:Inspect direct repository grants, parent and child team membership and inherited permission levels. A privilege review shows the developer no longer has write access through any team path. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
Incorrect Answers
B: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: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Inspect direct repository grants, parent and child team membership and inherited permission levels. A privilege review shows the developer no longer has write access through any team path.
C:Authorized operators can restore management during a simulated IdP outage without granting unrestricted permanent exemptions. It would not verify whether the proposed change works: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. A privilege review shows the developer no longer has write access through any team path. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
D:Identify the contributor's real operations and compare them with the available organization and repository roles. It would not provide the evidence needed for the paired diagnosis and follow-up: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Inspect direct repository grants, parent and child team membership and inherited permission levels. A privilege review shows the developer no longer has write access through any team path.
Question 75
GitHub Enterprise administration scenario — Review nested team permission inheritance. In an enterprise development environment: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. 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.
- The vendor accesses the specified repository only and is excluded from unrelated source code.
- A privilege review shows the developer no longer has write access through any team path.
- A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.
- GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
- Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
Explanation
Correct Answers
A:Correct the upstream team permission or membership while preserving unrelated authorized developer access. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. A privilege review shows the developer no longer has write access through any team path.
C:A privilege review shows the developer no longer has write access through any team path. Correct the upstream team permission or membership while preserving unrelated authorized developer access. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
E:GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. Correct the upstream team permission or membership while preserving unrelated authorized developer access. A privilege review shows the developer no longer has write access through any team path.
Incorrect Answers
B:The vendor accesses the specified repository only and is excluded from unrelated source code. It would not independently demonstrate that the control works: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. A privilege review shows the developer no longer has write access through any team path. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
D:A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure. It is not the rule that supports the proposed change and acceptance test: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. Correct the upstream team permission or membership while preserving unrelated authorized developer access.
F:Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. It does not implement the governing rule for this approval: A developer is removed from one repository directly but retains write access through a parent team that grants permissions to a child team. Correct the upstream team permission or membership while preserving unrelated authorized developer access. A privilege review shows the developer no longer has write access through any team path.
Question 76
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. 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.
- Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
- Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
- Application permissions must be inventoried and periodically reduced or revoked to their current business purpose.
Explanation
Correct Answer
C:Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly.
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 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.
B:Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. It does not govern the condition described: 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.
D:Application permissions must be inventoried and periodically reduced or revoked to their current business purpose. It does not govern the condition described: 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.
Question 77
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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare the incident approval and duration with current repository roles and relevant audit events.
- Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
- Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
- Review the role's proposed permissions, subscription support and which repositories actually require the access.
Explanation
Correct Answer
B:Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. 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.
Incorrect Answers
A:Compare the incident approval and duration with current repository roles and relevant audit events. That check would not establish the decisive facts for this condition: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
C: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: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
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 company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
Question 78
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. 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.
- Escalate a minimal reviewed exception to the proper policy owner rather than granting enterprise admin rights.
- Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly.
- Correct the team repository permission and document the least-privilege approval for the repository owner.
- Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.
Explanation
Correct Answer
B:Standardize the enterprise team lifecycle and map approved access to owning organization repositories explicitly. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
Incorrect Answers
A:Escalate a minimal reviewed exception to the proper policy owner rather than granting enterprise admin rights. That change would leave the reported problem unresolved: 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.
C:Correct the team repository permission and document the least-privilege approval for the repository owner. That change would leave the reported problem unresolved: 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.
D:Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation. That change would leave the reported problem unresolved: 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.
Question 79
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. 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.
- Inspect the intended reader population and the enterprise's repository visibility and access policies.
- Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
- The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
- A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
- Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings.
Explanation
Correct Answers
B:Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. 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.
D:A test user gets the correct rights in the correct organization without accidental cross-subsidiary access. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. Enterprise-wide access governance still requires explicit mapping of organizational membership, team administration and repository permissions.
Incorrect Answers
A:Inspect the intended reader population and the enterprise's repository visibility and access policies. It would not provide the evidence needed for the paired diagnosis and follow-up: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
C: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 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.
E:Examine the SCIM identity lifecycle events independently of team synchronization group-to-team mappings. It would not provide the evidence needed for the paired diagnosis and follow-up: A company tries to use a single team grant to secure separate subsidiaries without agreeing which GitHub organizations own their repositories. Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. A test user gets the correct rights in the correct organization without accidental cross-subsidiary access.
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.