Microsoft GH-100 Practice Test 7
Question 60
GitHub Enterprise administration scenario — Use custom organization repository roles appropriately. In an enterprise development environment: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. 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.
- The reviewer can inspect required security settings while write and administrator capabilities remain restricted.
- GitHub repository role selection should grant the narrowest permissions that support the documented work.
- Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
- Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
- Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
- The terminated user cannot access any in-scope enterprise repository and audit records show the accountable disablement.
Explanation
Correct Answers
A:The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported.
C:Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.
E:Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.
Incorrect Answers
B:GitHub repository role selection should grant the narrowest permissions that support the documented work. It is not the rule that supports the proposed change and acceptance test: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Custom repository roles can separate narrowly defined governance duties from global organization ownership where supported. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
D:Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. It does not implement the governing rule for this approval: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner. The reviewer can inspect required security settings while write and administrator capabilities remain restricted.
F:The terminated user cannot access any in-scope enterprise repository and audit records show the accountable disablement. It would not independently demonstrate that the control works: A compliance reviewer requires access to view code scanning and audit-related repository settings without unrestricted owner authority. The reviewer can inspect required security settings while write and administrator capabilities remain restricted. Define a bounded supported custom role and assign it to the reviewed users instead of defaulting to organization owner.
Question 61
GitHub Enterprise administration scenario — Audit accidental organization-owner privileges. In an enterprise development environment: A project contractor appears as an organization owner despite having an engagement that only requires one repository. The administrator must identify the controlling access, governance or platform principle rather than an unrelated configuration fix. Which principle BEST addresses this condition? Choose ONE best answer.
- Ruleset bypass permissions should be deliberate, role-restricted and traceable rather than a routine shortcut.
- GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
- Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
- A transfer requires reviewing both team-based grants and direct repository or organization role assignments.
Explanation
Correct Answer
C:Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification. Inspect the owner's creation history, security log, contract scope and affected organization resources. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
Incorrect Answers
A:Ruleset bypass permissions should be deliberate, role-restricted and traceable rather than a routine shortcut. It does not govern the condition described: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
B:GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. It does not govern the condition described: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
D:A transfer requires reviewing both team-based grants and direct repository or organization role assignments. It does not govern the condition described: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
Question 62
GitHub Enterprise administration scenario — Audit accidental organization-owner privileges. In an enterprise development environment: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect the owner's creation history, security log, contract scope and affected organization resources.
- Inspect the proposed permission matrix and test roles against sample repositories and workflow files.
- Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state.
- Compare employee lifecycle requirements, external collaboration needs and the managed-user restrictions in the documented enterprise design.
Explanation
Correct Answer
A:Inspect the owner's creation history, security log, contract scope and affected organization resources. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
Incorrect Answers
B:Inspect the proposed permission matrix and test roles against sample repositories and workflow files. That check would not establish the decisive facts for this condition: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Inspect the owner's creation history, security log, contract scope and affected organization resources.
C:Compare the identity provider provisioning assignment, SCIM response logs and the employee's GitHub managed-account state. That check would not establish the decisive facts for this condition: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Inspect the owner's creation history, security log, contract scope and affected organization resources.
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: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Inspect the owner's creation history, security log, contract scope and affected organization resources.
Question 63
GitHub Enterprise administration scenario — Audit accidental organization-owner privileges. In an enterprise development environment: A project contractor appears as an organization owner despite having an engagement that only requires one repository. The enterprise administrator needs a least-privilege corrective change with accountable approval and rollback. Which action BEST resolves the reported GitHub configuration or governance problem? Choose ONE best answer.
- Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence.
- Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
- Replace admin access with the lowest suitable role and confirm that required content changes still work.
- Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations.
Explanation
Correct Answer
B:Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight. Inspect the owner's creation history, security log, contract scope and affected organization resources. The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
Incorrect Answers
A:Revoke unauthorized invitations and repair the access-grant process while protecting audit evidence. That change would leave the reported problem unresolved: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
C: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 project contractor appears as an organization owner despite having an engagement that only requires one repository. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
D:Enforce the appropriate SAML policy with pilot validation and documented recovery for owners and service integrations. That change would leave the reported problem unresolved: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
Question 64
GitHub Enterprise administration scenario — Audit accidental organization-owner privileges. In an enterprise development environment: A project contractor appears as an organization owner despite having an engagement that only requires one repository. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
- Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
- Review the configured SSO mechanism, recovery controls, authorized emergency operators and outage runbook tests.
- Inspect the owner's creation history, security log, contract scope and affected organization resources.
- Removing the user from the IdP group removes the matching GitHub team-granted repository permission.
Explanation
Correct Answers
A:The contractor retains only the approved repository permissions and owner membership is limited to designated staff. Inspect the owner's creation history, security log, contract scope and affected organization resources. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
D:Inspect the owner's creation history, security log, contract scope and affected organization resources. The contractor retains only the approved repository permissions and owner membership is limited to designated staff. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
Incorrect Answers
B:Review branch protections, the available bypass actors and the historical reasons for requested exceptions. It would not provide the evidence needed for the paired diagnosis and follow-up: A project contractor appears as an organization owner despite having an engagement that only requires one repository. Inspect the owner's creation history, security log, contract scope and affected organization resources. The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
C: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 project contractor appears as an organization owner despite having an engagement that only requires one repository. Inspect the owner's creation history, security log, contract scope and affected organization resources. The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
E:Removing the user from the IdP group removes the matching GitHub team-granted repository permission. It would not verify whether the proposed change works: A project contractor appears as an organization owner despite having an engagement that only requires one repository. The contractor retains only the approved repository permissions and owner membership is limited to designated staff. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
Question 65
GitHub Enterprise administration scenario — Audit accidental organization-owner privileges. In an enterprise development environment: A project contractor appears as an organization owner despite having an engagement that only requires one repository. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- A mandatory identity provider is a critical availability dependency that requires an approved recovery procedure.
- Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
- The terminated user cannot access any in-scope enterprise repository and audit records show the accountable disablement.
- Configure and validate SCIM lifecycle and team access mapping as separate controls appropriate to the account model.
- Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
- The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
Explanation
Correct Answers
B:Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification. The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
E:Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight. The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
F:The contractor retains only the approved repository permissions and owner membership is limited to designated staff. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification.
Incorrect Answers
A: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 project contractor appears as an organization owner despite having an engagement that only requires one repository. Organization-owner authority spans policies and resources beyond a single repository, requiring an explicit operational justification. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
C:The terminated user cannot access any in-scope enterprise repository and audit records show the accountable disablement. It would not independently demonstrate that the control works: A project contractor appears as an organization owner despite having an engagement that only requires one repository. The contractor retains only the approved repository permissions and owner membership is limited to designated staff. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight.
D: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 project contractor appears as an organization owner despite having an engagement that only requires one repository. Remove unauthorized owner status and assign reviewed repository-specific permissions with owner oversight. The contractor retains only the approved repository permissions and owner membership is limited to designated staff.
Question 66
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. 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.
- GitHub repository role selection should grant the narrowest permissions that support the documented work.
- Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model.
- GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective.
Explanation
Correct Answer
A:External collaborators should be assigned only necessary supported repository access and reviewed separately from employees. Compare the contract scope, invitation type, repository permissions and external collaborator inventory. Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
Incorrect Answers
B:GitHub repository role selection should grant the narrowest permissions that support the documented work. It does not govern the condition described: 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.
C:Available enterprise-managed authentication patterns depend on supported IdP integrations and the enterprise's configured account model. It does not govern the condition described: 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.
D:GitHub team hierarchy and inherited repository permissions must be traced before declaring an access removal effective. It does not govern the condition described: 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.
Question 67
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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review branch protections, the available bypass actors and the historical reasons for requested exceptions.
- Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy.
- Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
- Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions.
Explanation
Correct Answer
C:Compare the contract scope, invitation type, repository permissions and external collaborator inventory. 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.
Incorrect Answers
A:Review branch protections, the available bypass actors and the historical reasons for requested exceptions. That check would not establish the decisive facts for this condition: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
B:Review enterprise and organization 2FA enforcement settings, account enrollment exceptions and the IdP MFA assurance policy. That check would not establish the decisive facts for this condition: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
D:Correlate HR termination, IdP deactivation, SCIM events and the account's enterprise membership and sessions. That check would not establish the decisive facts for this condition: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
Question 68
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. 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.
- Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration.
- Repair the approved team-to-group mapping and test both adding and removing a member through the identity provider.
- Issue or approve an appropriately scoped supported token, satisfy the applicable SSO requirement, and retest the automation.
Explanation
Correct Answer
B:Use narrowly scoped external repository collaboration subject to the enterprise account model and approved expiration. Compare the contract scope, invitation type, repository permissions and external collaborator inventory. The vendor accesses the specified repository only and is excluded from unrelated source code.
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: 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.
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 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.
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 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.
Question 69
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. 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.
- Every external invitation maps to an approved business request and unauthorized access is removed.
- Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope.
- Compare the contract scope, invitation type, repository permissions and external collaborator inventory.
- Compare the incident approval and duration with current repository roles and relevant audit events.
- The vendor accesses the specified repository only and is excluded from unrelated source code.
Explanation
Correct Answers
C:Compare the contract scope, invitation type, repository permissions and external collaborator inventory. 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.
E:The vendor accesses the specified repository only and is excluded from unrelated source code. Compare the contract scope, invitation type, repository permissions and external collaborator inventory. External collaborators should be assigned only necessary supported repository access and reviewed separately from employees.
Incorrect Answers
A:Every external invitation maps to an approved business request and unauthorized access is removed. It would not verify whether the proposed change 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.
B:Compare enterprise team designs with each subsidiary's organization ownership and the applicable team synchronization scope. It would not provide the evidence needed for the paired diagnosis and follow-up: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. Compare the contract scope, invitation type, repository permissions and external collaborator inventory. The vendor accesses the specified repository only and is excluded from unrelated source code.
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: A vendor's access request is approved for one private integration repository but admins invite the vendor into a broad internal team. Compare the contract scope, invitation type, repository permissions and external collaborator inventory. The vendor accesses the specified repository only and is excluded from unrelated source code.
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.