cert
cert-1
cert-2

Pass Microsoft GH-100 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
GH-100 Exam - Verified By Experts
GH-100 Premium File

GH-100 Premium File

$69.99
$76.99
  • Premium File 171 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 11 downloads in the last 7 days
block-screenshots
Microsoft GH-100 Practice Test 20

Question 190

GitHub Enterprise administration scenario — Consolidate billing accountability across organizations. In an enterprise development environment: Multiple GitHub organizations belong to one enterprise but engineering teams dispute which cost center should own paid feature consumption. 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.

  1. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits.
  2. Each reviewed charge can be traced to the responsible organization and agreed budget owner.
  3. Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations.
  4. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.
  5. Restore the approved organization-side grant and escalate only if documented platform behavior remains faulty.
  6. Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation.

Explanation

Correct Answers

A:

Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits. Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation. Each reviewed charge can be traced to the responsible organization and agreed budget owner.

B:

Each reviewed charge can be traced to the responsible organization and agreed budget owner. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits. Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation.

F:

Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits. Each reviewed charge can be traced to the responsible organization and agreed budget owner.

Incorrect Answers

C:

Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations. It is not the rule that supports the proposed change and acceptance test: Multiple GitHub organizations belong to one enterprise but engineering teams dispute which cost center should own paid feature consumption. Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits.

D:

Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. It would not independently demonstrate that the control works: Multiple GitHub organizations belong to one enterprise but engineering teams dispute which cost center should own paid feature consumption. Each reviewed charge can be traced to the responsible organization and agreed budget owner. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits.

E:

Restore the approved organization-side grant and escalate only if documented platform behavior remains faulty. It does not implement the governing rule for this approval: Multiple GitHub organizations belong to one enterprise but engineering teams dispute which cost center should own paid feature consumption. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits. Each reviewed charge can be traced to the responsible organization and agreed budget owner.

Question 191

GitHub Enterprise administration scenario — Set safe metered-feature spending controls. In an enterprise development environment: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. 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.

  1. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.
  2. Enterprise Cloud data-residency options have eligibility and account-model prerequisites that must be examined before procurement.
  3. Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials.
  4. Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations.

Explanation

Correct Answer

A:

Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

Incorrect Answers

B:

Enterprise Cloud data-residency options have eligibility and account-model prerequisites that must be examined before procurement. It does not govern the condition described: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.

C:

Repository lifecycle governance should preserve needed history while removing unnecessary write paths and credentials. It does not govern the condition described: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.

D:

Self-hosted service maintenance requires named responsibilities across infrastructure, software and dependent integrations. It does not govern the condition described: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.

Question 192

GitHub Enterprise administration scenario — Set safe metered-feature spending controls. In an enterprise development environment: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Examine the maintenance runbook, backup verification, storage/network dependencies and rollback contact list.
  2. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit.
  3. Compare GitHub account provisioning, license reports, recent activity and business owner attestations.
  4. Compare current and destination organization policies, effective collaborators, automation secrets and repository links.

Explanation

Correct Answer

B:

Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

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 new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit.

C:

Compare GitHub account provisioning, license reports, recent activity and business owner attestations. That check would not establish the decisive facts for this condition: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit.

D:

Compare current and destination organization policies, effective collaborators, automation secrets and repository links. That check would not establish the decisive facts for this condition: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit.

Question 193

GitHub Enterprise administration scenario — Set safe metered-feature spending controls. In an enterprise development environment: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. 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.

  1. Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials.
  2. Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits.
  3. Adopt documented release/tag rulesets and require an auditable source-to-release mapping.
  4. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

Explanation

Correct Answer

D:

Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.

Incorrect Answers

A:

Archive the unused repository with a documented alternative for actively maintained dependencies and retire unneeded credentials. That change would leave the reported problem unresolved: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

B:

Define a documented allocation policy and publish auditable cost-center mappings before changing spend limits. That change would leave the reported problem unresolved: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

C:

Adopt documented release/tag rulesets and require an auditable source-to-release mapping. That change would leave the reported problem unresolved: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

Question 194

GitHub Enterprise administration scenario — Set safe metered-feature spending controls. In an enterprise development environment: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. 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.

  1. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit.
  2. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.
  3. The target environment is deployed under approved responsibility boundaries and a representative developer signs in successfully.
  4. Record the GHES version, failure times, topology, relevant health metrics and a sanitized support bundle.
  5. Inventory existing organizations, their owner groups, billing associations and mandatory security policy exceptions.

Explanation

Correct Answers

A:

Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

B:

Spending alerts fire at planned thresholds and critical production work retains the agreed capacity. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.

Incorrect Answers

C:

The target environment is deployed under approved responsibility boundaries and a representative developer signs in successfully. It would not verify whether the proposed change works: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

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 new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.

E:

Inventory existing organizations, their owner groups, billing associations and mandatory security policy exceptions. It would not provide the evidence needed for the paired diagnosis and follow-up: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Compare current billing reports, included allowances, expected job volume and consequences of hitting a spending limit. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.

Question 195

GitHub Enterprise administration scenario — Set safe metered-feature spending controls. In an enterprise development environment: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. 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.

  1. Support receives reproducible evidence and local admins retain the ability to investigate their owned infrastructure.
  2. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.
  3. Choose a currently supported regional configuration only after a verified compatibility and migration assessment.
  4. Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation.
  5. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.
  6. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

Explanation

Correct Answers

B:

Spending alerts fire at planned thresholds and critical production work retains the agreed capacity. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements.

E:

Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.

F:

Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.

Incorrect Answers

A:

Support receives reproducible evidence and local admins retain the ability to investigate their owned infrastructure. It would not independently demonstrate that the control works: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

C:

Choose a currently supported regional configuration only after a verified compatibility and migration assessment. It does not implement the governing rule for this approval: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls. Spending alerts fire at planned thresholds and critical production work retains the agreed capacity.

D:

Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation. It is not the rule that supports the proposed change and acceptance test: A new continuous integration program starts consuming paid services rapidly and its owner requests an immediate unrestricted enterprise budget. Metered enterprise features need usage visibility and spending controls aligned with business continuity requirements. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

Question 196

GitHub Enterprise administration scenario — Plan migration evidence retention. In an enterprise development environment: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. 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.

  1. GitHub feature availability can depend on deployment type, enterprise version and enabled plan.
  2. Cross-platform migration must separately address source content, audit records and required retention periods.
  3. Organization creation and enrollment need centrally accountable governance and integration to enterprise policies.
  4. Enterprise Cloud data-residency options have eligibility and account-model prerequisites that must be examined before procurement.

Explanation

Correct Answer

B:

Cross-platform migration must separately address source content, audit records and required retention periods. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

Incorrect Answers

A:

GitHub feature availability can depend on deployment type, enterprise version and enabled plan. It does not govern the condition described: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Cross-platform migration must separately address source content, audit records and required retention periods.

C:

Organization creation and enrollment need centrally accountable governance and integration to enterprise policies. It does not govern the condition described: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Cross-platform migration must separately address source content, audit records and required retention periods.

D:

Enterprise Cloud data-residency options have eligibility and account-model prerequisites that must be examined before procurement. It does not govern the condition described: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Cross-platform migration must separately address source content, audit records and required retention periods.

Question 197

GitHub Enterprise administration scenario — Plan migration evidence retention. In an enterprise development environment: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner.
  2. Validate data control, hosting, connectivity and patch-management requirements against supported GHEC and GHES options.
  3. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.
  4. Check the installed GHES release, product documentation, feature prerequisites and enterprise license capabilities.

Explanation

Correct Answer

C:

Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. Cross-platform migration must separately address source content, audit records and required retention periods. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

Incorrect Answers

A:

Review downstream dependencies, outstanding security alerts, licenses and the archive decision owner. That check would not establish the decisive facts for this condition: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.

B:

Validate data control, hosting, connectivity and patch-management requirements against supported GHEC and GHES options. That check would not establish the decisive facts for this condition: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.

D:

Check the installed GHES release, product documentation, feature prerequisites and enterprise license capabilities. That check would not establish the decisive facts for this condition: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.

Question 198

GitHub Enterprise administration scenario — Plan migration evidence retention. In an enterprise development environment: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. 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.

  1. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.
  2. Stage the policy change in a representative pilot and obtain cross-organization owner approval before rollout.
  3. Require a reviewed onboarding path for new organizations and map them to the approved enterprise account.
  4. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.

Explanation

Correct Answer

A:

Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. The compliance team retrieves required historical events and selected repos are usable after migration.

Incorrect Answers

B:

Stage the policy change in a representative pilot and obtain cross-organization owner approval before rollout. That change would leave the reported problem unresolved: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

C:

Require a reviewed onboarding path for new organizations and map them to the approved enterprise account. That change would leave the reported problem unresolved: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

D:

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 company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

Question 199

GitHub Enterprise administration scenario — Plan migration evidence retention. In an enterprise development environment: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. 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.

  1. The compliance team retrieves required historical events and selected repos are usable after migration.
  2. Compare approved legal regions, supported enterprise types and the team's external collaboration requirements.
  3. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities.
  4. Compare current and destination organization policies, effective collaborators, automation secrets and repository links.
  5. Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval.

Explanation

Correct Answers

A:

The compliance team retrieves required historical events and selected repos are usable after migration. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. Cross-platform migration must separately address source content, audit records and required retention periods.

C:

Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. The compliance team retrieves required historical events and selected repos are usable after migration. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

Incorrect Answers

B:

Compare approved legal regions, supported enterprise types and the team's external collaboration requirements. It would not provide the evidence needed for the paired diagnosis and follow-up: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. The compliance team retrieves required historical events and selected repos are usable after migration.

D:

Compare current and destination organization policies, effective collaborators, automation secrets and repository links. It would not provide the evidence needed for the paired diagnosis and follow-up: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Inventory repository metadata, audit retention requirements, integration history and the migration tooling's documented capabilities. The compliance team retrieves required historical events and selected repos are usable after migration.

E:

Routine requests are resolved by authorized local admins while sensitive changes still receive enterprise approval. It would not verify whether the proposed change works: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. The compliance team retrieves required historical events and selected repos are usable after migration. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

Question 200

GitHub Enterprise administration scenario — Plan migration evidence retention. In an enterprise development environment: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. 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.

  1. The compliance team retrieves required historical events and selected repos are usable after migration.
  2. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.
  3. Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation.
  4. Cross-platform migration must separately address source content, audit records and required retention periods.
  5. Set approved budgets and alerts with contingency paths for critical workflows rather than disabling all spending controls.
  6. Support receives reproducible evidence and local admins retain the ability to investigate their owned infrastructure.

Explanation

Correct Answers

A:

The compliance team retrieves required historical events and selected repos are usable after migration. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES. Cross-platform migration must separately address source content, audit records and required retention periods.

B:

Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES. Cross-platform migration must separately address source content, audit records and required retention periods. The compliance team retrieves required historical events and selected repos are usable after migration.

D:

Cross-platform migration must separately address source content, audit records and required retention periods. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES. The compliance team retrieves required historical events and selected repos are usable after migration.

Incorrect Answers

C:

Enterprise billing and metered feature chargeback require organization-level attribution rules and periodic reconciliation. It is not the rule that supports the proposed change and acceptance test: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Cross-platform migration must separately address source content, audit records and required retention periods. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

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: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES. The compliance team retrieves required historical events and selected repos are usable after migration.

F:

Support receives reproducible evidence and local admins retain the ability to investigate their owned infrastructure. It would not independently demonstrate that the control works: A company migrates from GitHub Enterprise Server to Cloud and assumes historical audit records will automatically be retained indefinitely in the new environment. The compliance team retrieves required historical events and selected repos are usable after migration. Archive required historical audit evidence externally and validate transferred repository metadata before decommissioning GHES.

GitHub Administration (GH-100) Practice Tests