Microsoft GH-100 Practice Test 51
Question 500
GitHub Enterprise administration scenario — Use enterprise runner groups for project isolation. In an enterprise development environment: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. 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.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
- A malicious test title is processed as inert data and cannot trigger an unintended shell command.
- Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
- The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
Explanation
Correct Answers
D:Runner group policies should constrain repository and organization access to trusted workload boundaries. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
E:Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. Runner group policies should constrain repository and organization access to trusted workload boundaries. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
F:The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. Runner group policies should constrain repository and organization access to trusted workload boundaries.
Incorrect Answers
A:Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets. It is not the rule that supports the proposed change and acceptance test: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Runner group policies should constrain repository and organization access to trusted workload boundaries. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
B:A malicious test title is processed as inert data and cannot trigger an unintended shell command. It would not independently demonstrate that the control works: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
C:Define a suitable concurrency group or deployment queue policy with controlled cancellation semantics. It does not implement the governing rule for this approval: A shared self-hosted runner executes untrusted experimental jobs alongside sensitive payment release jobs because all enterprise repositories can access one runner pool. Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. The payment release can use its runner pool while an unrelated repository cannot schedule jobs there.
Question 501
GitHub Enterprise administration scenario — Avoid self-hosted runners for untrusted public fork code. In an enterprise development environment: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. 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.
- Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement.
- Workflow and job-level token permissions should be restricted to minimum required operations.
- Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
Explanation
Correct Answer
C:Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation. Review runner persistence, network reachability, PR trust conditions and available credentials or caches. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Incorrect Answers
A:Workflow templates aid adoption but do not alone prove mandatory enterprise policy enforcement. It does not govern the condition described: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
B:Workflow and job-level token permissions should be restricted to minimum required operations. It does not govern the condition described: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
D:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. It does not govern the condition described: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
Question 502
GitHub Enterprise administration scenario — Avoid self-hosted runners for untrusted public fork code. In an enterprise development environment: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
- Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
- Inspect all workflow triggers, secret references, required environments and existing repository security settings.
- Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
Explanation
Correct Answer
D:Review runner persistence, network reachability, PR trust conditions and available credentials or caches. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Incorrect Answers
A:Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. That check would not establish the decisive facts for this condition: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
B:Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. That check would not establish the decisive facts for this condition: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
C:Inspect all workflow triggers, secret references, required environments and existing repository security settings. That check would not establish the decisive facts for this condition: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
Question 503
GitHub Enterprise administration scenario — Avoid self-hosted runners for untrusted public fork code. In an enterprise development environment: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. 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.
- Restore the supported runner service or replace the failed agent through an approved capacity and image process.
- Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories.
- Replace or approve the action through the supply-chain allow process and pin a reviewed revision.
- Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Explanation
Correct Answer
D:Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. Review runner persistence, network reachability, PR trust conditions and available credentials or caches. A fork pull request cannot access internal runner resources while its safe build tests still execute.
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 team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
B:Separate sensitive runners into restricted groups and limit access to explicitly approved organizations or repositories. That change would leave the reported problem unresolved: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
C:Replace or approve the action through the supply-chain allow process and pin a reviewed revision. That change would leave the reported problem unresolved: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Question 504
GitHub Enterprise administration scenario — Avoid self-hosted runners for untrusted public fork code. In an enterprise development environment: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- A fork pull request cannot access internal runner resources while its safe build tests still execute.
- Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
- Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
- Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
Explanation
Correct Answers
A:A fork pull request cannot access internal runner resources while its safe build tests still execute. Review runner persistence, network reachability, PR trust conditions and available credentials or caches. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
D:Review runner persistence, network reachability, PR trust conditions and available credentials or caches. A fork pull request cannot access internal runner resources while its safe build tests still execute. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Incorrect Answers
B: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 team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. A fork pull request cannot access internal runner resources while its safe build tests still execute. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
C:Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. It would not provide the evidence needed for the paired diagnosis and follow-up: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Review runner persistence, network reachability, PR trust conditions and available credentials or caches. A fork pull request cannot access internal runner resources while its safe build tests still execute.
E:Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. It would not provide the evidence needed for the paired diagnosis and follow-up: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Review runner persistence, network reachability, PR trust conditions and available credentials or caches. A fork pull request cannot access internal runner resources while its safe build tests still execute.
Question 505
GitHub Enterprise administration scenario — Avoid self-hosted runners for untrusted public fork code. In an enterprise development environment: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. 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.
- Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
- Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
- Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
- Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls.
- A fork pull request cannot access internal runner resources while its safe build tests still execute.
- The queued job is assigned to a qualified runner and finishes its representative build.
Explanation
Correct Answers
A:Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation. A fork pull request cannot access internal runner resources while its safe build tests still execute.
C:Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. A fork pull request cannot access internal runner resources while its safe build tests still execute.
E:A fork pull request cannot access internal runner resources while its safe build tests still execute. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation.
Incorrect Answers
B:Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. It does not implement the governing rule for this approval: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. A fork pull request cannot access internal runner resources while its safe build tests still execute.
D:Composite actions share reusable steps inside a job while reusable workflows can coordinate reusable jobs and workflow-level controls. It is not the rule that supports the proposed change and acceptance test: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. Untrusted contributor code should not execute on privileged persistent infrastructure without strong isolation. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
F:The queued job is assigned to a qualified runner and finishes its representative build. It would not independently demonstrate that the control works: A team proposes running arbitrary public pull request workflows on a persistent internal self-hosted runner that can reach the company network. A fork pull request cannot access internal runner resources while its safe build tests still execute. Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Question 506
GitHub Enterprise administration scenario — Use ephemeral self-hosted runners for sensitive workloads. In an enterprise development environment: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. 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.
- Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
- Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
- Workflow execution plans should balance required test coverage and resource cost within approved budgets.
- Workflow and job-level token permissions should be restricted to minimum required operations.
Explanation
Correct Answer
B:Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
Incorrect Answers
A:Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. It does not govern the condition described: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
C:Workflow execution plans should balance required test coverage and resource cost within approved budgets. It does not govern the condition described: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
D:Workflow and job-level token permissions should be restricted to minimum required operations. It does not govern the condition described: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
Question 507
GitHub Enterprise administration scenario — Use ephemeral self-hosted runners for sensitive workloads. In an enterprise development environment: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
- Review log excerpts, secret and variable handling, debug flags and downstream log exports.
- Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
- Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job.
Explanation
Correct Answer
C:Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
Incorrect Answers
A:Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies. That check would not establish the decisive facts for this condition: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
B:Review log excerpts, secret and variable handling, debug flags and downstream log exports. That check would not establish the decisive facts for this condition: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
D:Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job. That check would not establish the decisive facts for this condition: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
Question 508
GitHub Enterprise administration scenario — Use ephemeral self-hosted runners for sensitive workloads. In an enterprise development environment: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. 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.
- Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
- Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
- Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
- Set a justified job timeout and meaningful cleanup or evidence capture for the integration step.
Explanation
Correct Answer
A:Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
Incorrect Answers
B:Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. That change would leave the reported problem unresolved: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
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 self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
D:Set a justified job timeout and meaningful cleanup or evidence capture for the integration step. That change would leave the reported problem unresolved: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
Question 509
GitHub Enterprise administration scenario — Use ephemeral self-hosted runners for sensitive workloads. In an enterprise development environment: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements.
- Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
- Compare the workflow runs-on selector, runner labels, runner group access and runner online status.
- A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
- Disposable artifacts expire on policy while required release evidence remains retrievable.
Explanation
Correct Answers
A:Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
D:A newly scheduled job starts from a clean runner state without previous job artifacts or secrets. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
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 self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
C:Compare the workflow runs-on selector, runner labels, runner group access and runner online status. It would not provide the evidence needed for the paired diagnosis and follow-up: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Inspect runner reuse, workspace cleanup, image provenance and job isolation requirements. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
E:Disposable artifacts expire on policy while required release evidence remains retrievable. It would not verify whether the proposed change works: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
Question 510
GitHub Enterprise administration scenario — Use ephemeral self-hosted runners for sensitive workloads. In an enterprise development environment: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. 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.
- Larger runners have configurable resource and networking capabilities that require matching security and access policies.
- Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
- An authorized workflow dispatches to the restored runner group and execution results are visible.
- Move the credential to a protected environment or approved vault-backed access route with controlled job permissions.
- Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
- A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
Explanation
Correct Answers
B:Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
E:Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.
F:A newly scheduled job starts from a clean runner state without previous job artifacts or secrets. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
Incorrect Answers
A: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 self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
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 self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use.
D:Move the credential to a protected environment or approved vault-backed access route with controlled job permissions. It does not implement the governing rule for this approval: A self-hosted build runner remains connected after each job and developers can inspect files left by earlier privileged builds. Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. A newly scheduled job starts from a clean runner state without previous job artifacts or secrets.