Microsoft GH-100 Practice Test 18
Question 170
GitHub Enterprise administration scenario — Govern enterprise organization creation. In an enterprise development environment: New business teams repeatedly open GitHub organizations outside the enterprise's security review and create uncontrolled billing islands. 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.
- Require a reviewed onboarding path for new organizations and map them to the approved enterprise account.
- Organization creation and enrollment need centrally accountable governance and integration to enterprise policies.
- Every active organization appears in governance and licensing records with responsible owners.
- Self-hosted enterprise operations must distinguish appliance diagnostics and local infrastructure responsibility from vendor support analysis.
- Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.
- The target environment is deployed under approved responsibility boundaries and a representative developer signs in successfully.
Explanation
Correct Answers
A:Require a reviewed onboarding path for new organizations and map them to the approved enterprise account. Organization creation and enrollment need centrally accountable governance and integration to enterprise policies. Every active organization appears in governance and licensing records with responsible owners.
B:Organization creation and enrollment need centrally accountable governance and integration to enterprise policies. Require a reviewed onboarding path for new organizations and map them to the approved enterprise account. Every active organization appears in governance and licensing records with responsible owners.
C:Every active organization appears in governance and licensing records with responsible owners. Require a reviewed onboarding path for new organizations and map them to the approved enterprise account. Organization creation and enrollment need centrally accountable governance and integration to enterprise policies.
Incorrect Answers
D:Self-hosted enterprise operations must distinguish appliance diagnostics and local infrastructure responsibility from vendor support analysis. It is not the rule that supports the proposed change and acceptance test: New business teams repeatedly open GitHub organizations outside the enterprise's security review and create uncontrolled billing islands. Organization creation and enrollment need centrally accountable governance and integration to enterprise policies. Require a reviewed onboarding path for new organizations and map them to the approved enterprise account.
E:Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. It does not implement the governing rule for this approval: New business teams repeatedly open GitHub organizations outside the enterprise's security review and create uncontrolled billing islands. Require a reviewed onboarding path for new organizations and map them to the approved enterprise account. Every active organization appears in governance and licensing records with responsible owners.
F:The target environment is deployed under approved responsibility boundaries and a representative developer signs in successfully. It would not independently demonstrate that the control works: New business teams repeatedly open GitHub organizations outside the enterprise's security review and create uncontrolled billing islands. Every active organization appears in governance and licensing records with responsible owners. Require a reviewed onboarding path for new organizations and map them to the approved enterprise account.
Question 171
GitHub Enterprise administration scenario — Archive repositories without breaking dependency ownership. In an enterprise development environment: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. 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.
- Release standards should provide traceable commit, branch and tag conventions linked to accountable approvals.
- Admins should gather local configuration evidence and reproduction details before asking GitHub Support to investigate a service defect.
- Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.
- Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
Explanation
Correct Answer
D:Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
Incorrect Answers
A:Release standards should provide traceable commit, branch and tag conventions linked to accountable approvals. It does not govern the condition described: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
B:Admins should gather local configuration evidence and reproduction details before asking GitHub Support to investigate a service defect. It does not govern the condition described: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
C:Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. It does not govern the condition described: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
Question 172
GitHub Enterprise administration scenario — Archive repositories without breaking dependency ownership. In an enterprise development environment: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Examine the maintenance runbook, backup verification, storage/network dependencies and rollback contact list.
- Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit.
- Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner.
- Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.
Explanation
Correct Answer
C:Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
Incorrect Answers
A:Examine the maintenance runbook, backup verification, storage/network dependencies and rollback contact list. That check would not establish the decisive facts for this condition: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner.
B:Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. That check would not establish the decisive facts for this condition: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner.
D:Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. That check would not establish the decisive facts for this condition: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner.
Question 173
GitHub Enterprise administration scenario — Archive repositories without breaking dependency ownership. In an enterprise development environment: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. 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.
- Publish a proportional review baseline with enforceable rulesets and documented risk-based exceptions.
- Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.
- Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.
- Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
Explanation
Correct Answer
D:Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
Incorrect Answers
A:Publish a proportional review baseline with enforceable rulesets and documented risk-based exceptions. That change would leave the reported problem unresolved: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
B:Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES. That change would leave the reported problem unresolved: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
C:Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. That change would leave the reported problem unresolved: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
Question 174
GitHub Enterprise administration scenario — Archive repositories without breaking dependency ownership. In an enterprise development environment: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner.
- Idle entitlements are reduced and retained employees can still access required repositories.
- Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
- Record the GHES version, failure times, topology, relevant health metrics and a sanitized support bundle.
- Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.
Explanation
Correct Answers
A:Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
C:Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
Incorrect Answers
B:Idle entitlements are reduced and retained employees can still access required repositories. It would not verify whether the proposed change works: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
D:Record the GHES version, failure times, topology, relevant health metrics and a sanitized support bundle. It would not provide the evidence needed for the paired diagnosis and follow-up: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
E:Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. It would not provide the evidence needed for the paired diagnosis and follow-up: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
Question 175
GitHub Enterprise administration scenario — Archive repositories without breaking dependency ownership. In an enterprise development environment: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. 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.
- Representative repositories enforce the required approvals while low-risk teams retain permitted flexibility.
- Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
- Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
- Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
- Use the supported version-specific configuration or schedule a tested upgrade rather than copying cloud instructions blindly.
- Admins should gather local configuration evidence and reproduction details before asking GitHub Support to investigate a service defect.
Explanation
Correct Answers
B:Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
C:Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
D:Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
Incorrect Answers
A:Representative repositories enforce the required approvals while low-risk teams retain permitted flexibility. It would not independently demonstrate that the control works: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
E:Use the supported version-specific configuration or schedule a tested upgrade rather than copying cloud instructions blindly. It does not implement the governing rule for this approval: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. Repository history remains readable to authorized auditors but unneeded updates and automation no longer execute.
F:Admins should gather local configuration evidence and reproduction details before asking GitHub Support to investigate a service defect. It is not the rule that supports the proposed change and acceptance test: A retired library repository remains writable with old deployment credentials even though no team actively maintains it. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
Question 176
GitHub Enterprise administration scenario — Reconcile paid license consumption to identity roster. In an enterprise development environment: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. 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.
- License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
- Release standards should provide traceable commit, branch and tag conventions linked to accountable approvals.
- Admins should gather local configuration evidence and reproduction details before asking GitHub Support to investigate a service defect.
- Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.
Explanation
Correct Answer
A:License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
Incorrect Answers
B:Release standards should provide traceable commit, branch and tag conventions linked to accountable approvals. It does not govern the condition described: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
C:Admins should gather local configuration evidence and reproduction details before asking GitHub Support to investigate a service defect. It does not govern the condition described: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
D:Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. It does not govern the condition described: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
Question 177
GitHub Enterprise administration scenario — Reconcile paid license consumption to identity roster. In an enterprise development environment: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Check the installed GHES release, product documentation, feature prerequisites and enterprise license capabilities.
- Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports.
- Compare approved legal regions, supported enterprise types and the team's external collaboration requirements.
- Compare release risk tiers, current branch rulesets, CODEOWNERS usage and stakeholder approval requirements.
Explanation
Correct Answer
B:Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
Incorrect Answers
A:Check the installed GHES release, product documentation, feature prerequisites and enterprise license capabilities. That check would not establish the decisive facts for this condition: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports.
C:Compare approved legal regions, supported enterprise types and the team's external collaboration requirements. That check would not establish the decisive facts for this condition: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports.
D:Compare release risk tiers, current branch rulesets, CODEOWNERS usage and stakeholder approval requirements. That check would not establish the decisive facts for this condition: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports.
Question 178
GitHub Enterprise administration scenario — Reconcile paid license consumption to identity roster. In an enterprise development environment: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. 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.
- Collect the supported diagnostics and open an authorized support case while retaining access-control and data-handling protections.
- Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
- Publish a proportional review baseline with enforceable rulesets and documented risk-based exceptions.
- Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
Explanation
Correct Answer
B:Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. Billed active seats align with supported current access without removing authorized collaborators.
Incorrect Answers
A:Collect the supported diagnostics and open an authorized support case while retaining access-control and data-handling protections. That change would leave the reported problem unresolved: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
C:Publish a proportional review baseline with enforceable rulesets and documented risk-based exceptions. That change would leave the reported problem unresolved: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
D:Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. That change would leave the reported problem unresolved: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
Question 179
GitHub Enterprise administration scenario — Reconcile paid license consumption to identity roster. In an enterprise development environment: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. 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 compliance team retrieves required historical events and selected repos are usable after migration.
- Validate data control, hosting, connectivity and patch-management requirements against supported GHEC and GHES options.
- Inventory existing repositories, external identities, integrations, SSO configuration and managed-user collaboration restrictions.
- Billed active seats align with supported current access without removing authorized collaborators.
- Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports.
Explanation
Correct Answers
D:Billed active seats align with supported current access without removing authorized collaborators. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
E:Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. Billed active seats align with supported current access without removing authorized collaborators. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
Incorrect Answers
A:The compliance team retrieves required historical events and selected repos are usable after migration. It would not verify whether the proposed change works: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Billed active seats align with supported current access without removing authorized collaborators. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
B:Validate data control, hosting, connectivity and patch-management requirements against supported GHEC and GHES options. It would not provide the evidence needed for the paired diagnosis and follow-up: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. Billed active seats align with supported current access without removing authorized collaborators.
C:Inventory existing repositories, external identities, integrations, SSO configuration and managed-user collaboration restrictions. It would not provide the evidence needed for the paired diagnosis and follow-up: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Reconcile billed identities, SCIM removal status, outside collaborators and enterprise usage reports. Billed active seats align with supported current access without removing authorized collaborators.
Question 180
GitHub Enterprise administration scenario — Reconcile paid license consumption to identity roster. In an enterprise development environment: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. 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.
- Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
- Moving from personal-account enterprise practices to managed-user operation requires a deliberate migration and separate enterprise planning.
- Stage the policy change in a representative pilot and obtain cross-organization owner approval before rollout.
- The compliance team retrieves required historical events and selected repos are usable after migration.
- Billed active seats align with supported current access without removing authorized collaborators.
- License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
Explanation
Correct Answers
A:Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements. Billed active seats align with supported current access without removing authorized collaborators.
E:Billed active seats align with supported current access without removing authorized collaborators. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements.
F:License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. Billed active seats align with supported current access without removing authorized collaborators.
Incorrect Answers
B:Moving from personal-account enterprise practices to managed-user operation requires a deliberate migration and separate enterprise planning. It is not the rule that supports the proposed change and acceptance test: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. License optimization requires comparing actual billable account assignments with effective employee and collaborator entitlements. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.
C:Stage the policy change in a representative pilot and obtain cross-organization owner approval before rollout. It does not implement the governing rule for this approval: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats. Billed active seats align with supported current access without removing authorized collaborators.
D:The compliance team retrieves required historical events and selected repos are usable after migration. It would not independently demonstrate that the control works: Enterprise billing indicates more occupied licenses than active employees, while an admin assumes all seats are automatically released on HR termination. Billed active seats align with supported current access without removing authorized collaborators. Deprovision unused accounts through their authoritative lifecycle and document legitimate external seats.