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 58

Question 570

GitHub Enterprise administration scenario — Choose composite actions versus reusable workflows. In an enterprise development environment: A platform team copies several multi-job CI workflows into composite actions and is surprised that environment and job-level governance cannot be represented as expected. 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 standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation.
  2. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
  3. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
  4. Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
  5. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse.
  6. Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls.

Explanation

Correct Answers

A:

The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls.

E:

Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls. The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation.

F:

Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation.

Incorrect Answers

B:

Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. It does not implement the governing rule for this approval: A platform team copies several multi-job CI workflows into composite actions and is surprised that environment and job-level governance cannot be represented as expected. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation.

C:

The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. It would not independently demonstrate that the control works: A platform team copies several multi-job CI workflows into composite actions and is surprised that environment and job-level governance cannot be represented as expected. The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse.

D:

Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It is not the rule that supports the proposed change and acceptance test: A platform team copies several multi-job CI workflows into composite actions and is surprised that environment and job-level governance cannot be represented as expected. Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse.

Question 571

GitHub Enterprise administration scenario — Share private reusable workflows under controlled access. In an enterprise development environment: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. 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. Runner group policies should constrain repository and organization access to trusted workload boundaries.
  2. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
  3. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.
  4. Changes to runner group access are privileged governance events requiring attribution and periodic review.

Explanation

Correct Answer

C:

Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. Inspect the reusable repository's visibility, access settings and the caller's organization policy. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

Incorrect Answers

A:

Runner group policies should constrain repository and organization access to trusted workload boundaries. It does not govern the condition described: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

B:

Larger runners have configurable resource and networking capabilities that require matching security and access policies. It does not govern the condition described: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

D:

Changes to runner group access are privileged governance events requiring attribution and periodic review. It does not govern the condition described: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

Question 572

GitHub Enterprise administration scenario — Share private reusable workflows under controlled access. In an enterprise development environment: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing.
  2. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
  3. Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job.
  4. Inspect the reusable repository's visibility, access settings and the caller's organization policy.

Explanation

Correct Answer

D:

Inspect the reusable repository's visibility, access settings and the caller's organization policy. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

Incorrect Answers

A:

Inspect cache keys, workflow triggers, cache write eligibility and how cached files are executed during publishing. That check would not establish the decisive facts for this condition: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Inspect the reusable repository's visibility, access settings and the caller's organization policy.

B:

Correlate audit log policy-change events, runner group access history and approved maintenance tickets. That check would not establish the decisive facts for this condition: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Inspect the reusable repository's visibility, access settings and the caller's organization policy.

C:

Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job. That check would not establish the decisive facts for this condition: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Inspect the reusable repository's visibility, access settings and the caller's organization policy.

Question 573

GitHub Enterprise administration scenario — Share private reusable workflows under controlled access. In an enterprise development environment: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. 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. Restore the supported runner service or replace the failed agent through an approved capacity and image process.
  2. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.
  3. Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
  4. Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse.

Explanation

Correct Answer

B:

Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. Inspect the reusable repository's visibility, access settings and the caller's organization policy. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

Incorrect Answers

A:

Restore the supported runner service or replace the failed agent through an approved capacity and image process. That change would leave the reported problem unresolved: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

C:

Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. That change would leave the reported problem unresolved: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

D:

Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. That change would leave the reported problem unresolved: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

Question 574

GitHub Enterprise administration scenario — Share private reusable workflows under controlled access. In an enterprise development environment: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. 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. Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns.
  2. Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
  3. Inspect the reusable repository's visibility, access settings and the caller's organization policy.
  4. An authorized workflow dispatches to the restored runner group and execution results are visible.
  5. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

Explanation

Correct Answers

C:

Inspect the reusable repository's visibility, access settings and the caller's organization policy. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

E:

An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded. Inspect the reusable repository's visibility, access settings and the caller's organization policy. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

Incorrect Answers

A:

Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns. It would not provide the evidence needed for the paired diagnosis and follow-up: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Inspect the reusable repository's visibility, access settings and the caller's organization policy. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

B:

Review historical execution durations, external call retry behavior and the workflow's current timeout settings. It would not provide the evidence needed for the paired diagnosis and follow-up: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Inspect the reusable repository's visibility, access settings and the caller's organization policy. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

D:

An authorized workflow dispatches to the restored runner group and execution results are visible. It would not verify whether the proposed change works: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

Question 575

GitHub Enterprise administration scenario — Share private reusable workflows under controlled access. In an enterprise development environment: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. 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. A fork pull request cannot influence the release job's executable dependencies through a shared cache.
  2. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
  3. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.
  4. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.
  5. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
  6. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

Explanation

Correct Answers

C:

An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.

D:

Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

F:

Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

Incorrect Answers

A:

A fork pull request cannot influence the release job's executable dependencies through a shared cache. It would not independently demonstrate that the control works: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

B:

Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. It does not implement the governing rule for this approval: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. An authorized caller executes the reviewed shared workflow while unrelated repositories remain excluded.

E:

Larger runners have configurable resource and networking capabilities that require matching security and access policies. It is not the rule that supports the proposed change and acceptance test: A central tooling repository contains reusable workflows, but an application organization cannot reference them because its access policy does not permit reuse. Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.

Question 576

GitHub Enterprise administration scenario — Audit self-hosted runner security changes. In an enterprise development environment: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. 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. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
  2. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
  3. Changes to runner group access are privileged governance events requiring attribution and periodic review.
  4. Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.

Explanation

Correct Answer

C:

Changes to runner group access are privileged governance events requiring attribution and periodic review. Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

Incorrect Answers

A:

Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. It does not govern the condition described: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Changes to runner group access are privileged governance events requiring attribution and periodic review.

B:

Larger runners have configurable resource and networking capabilities that require matching security and access policies. It does not govern the condition described: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Changes to runner group access are privileged governance events requiring attribution and periodic review.

D:

Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It does not govern the condition described: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Changes to runner group access are privileged governance events requiring attribution and periodic review.

Question 577

GitHub Enterprise administration scenario — Audit self-hosted runner security changes. In an enterprise development environment: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.

  1. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
  2. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
  3. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
  4. Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.

Explanation

Correct Answer

B:

Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Changes to runner group access are privileged governance events requiring attribution and periodic review. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

Incorrect Answers

A:

Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. That check would not establish the decisive facts for this condition: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.

C:

Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. That check would not establish the decisive facts for this condition: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.

D:

Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. That check would not establish the decisive facts for this condition: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.

Question 578

GitHub Enterprise administration scenario — Audit self-hosted runner security changes. In an enterprise development environment: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. 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. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
  2. Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks.
  3. Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
  4. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

Explanation

Correct Answer

D:

Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Runner group access matches the approved organization list and the change actor is recorded for investigation.

Incorrect Answers

A:

Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. That change would leave the reported problem unresolved: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

B:

Optimize redundant jobs and establish spending alerts or budgets without disabling essential security checks. That change would leave the reported problem unresolved: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

C:

Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. That change would leave the reported problem unresolved: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

Question 579

GitHub Enterprise administration scenario — Audit self-hosted runner security changes. In an enterprise development environment: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. 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. Runner group access matches the approved organization list and the change actor is recorded for investigation.
  2. Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
  3. Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
  4. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
  5. Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job.

Explanation

Correct Answers

A:

Runner group access matches the approved organization list and the change actor is recorded for investigation. Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Changes to runner group access are privileged governance events requiring attribution and periodic review.

C:

Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Runner group access matches the approved organization list and the change actor is recorded for investigation. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

Incorrect Answers

B:

Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command. It would not provide the evidence needed for the paired diagnosis and follow-up: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Runner group access matches the approved organization list and the change actor is recorded for investigation.

D:

Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. It would not verify whether the proposed change works: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Runner group access matches the approved organization list and the change actor is recorded for investigation. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

E:

Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job. It would not provide the evidence needed for the paired diagnosis and follow-up: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Correlate audit log policy-change events, runner group access history and approved maintenance tickets. Runner group access matches the approved organization list and the change actor is recorded for investigation.

Question 580

GitHub Enterprise administration scenario — Audit self-hosted runner security changes. In an enterprise development environment: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. 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. Protected deployment environments help enforce authorized release gates and restrict production secret access.
  2. Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
  3. An authorized workflow dispatches to the restored runner group and execution results are visible.
  4. Changes to runner group access are privileged governance events requiring attribution and periodic review.
  5. Runner group access matches the approved organization list and the change actor is recorded for investigation.
  6. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

Explanation

Correct Answers

D:

Changes to runner group access are privileged governance events requiring attribution and periodic review. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Runner group access matches the approved organization list and the change actor is recorded for investigation.

E:

Runner group access matches the approved organization list and the change actor is recorded for investigation. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Changes to runner group access are privileged governance events requiring attribution and periodic review.

F:

Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Changes to runner group access are privileged governance events requiring attribution and periodic review. Runner group access matches the approved organization list and the change actor is recorded for investigation.

Incorrect Answers

A:

Protected deployment environments help enforce authorized release gates and restrict production secret access. It is not the rule that supports the proposed change and acceptance test: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Changes to runner group access are privileged governance events requiring attribution and periodic review. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

B:

Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. It does not implement the governing rule for this approval: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Runner group access matches the approved organization list and the change actor is recorded for investigation.

C:

An authorized workflow dispatches to the restored runner group and execution results are visible. It would not independently demonstrate that the control works: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Runner group access matches the approved organization list and the change actor is recorded for investigation. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.

GitHub Administration (GH-100) Practice Tests