Microsoft GH-100 Practice Test 52
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.
Question 511
GitHub Enterprise administration scenario — Choose GitHub-hosted or self-hosted runners by constraints. In an enterprise development environment: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. 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.
- Protected deployment environments help enforce authorized release gates and restrict production secret access.
- Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
- Third-party actions execute code in workflow security context and require trust, permission and change reviews.
Explanation
Correct Answer
A:Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. Compare build resource needs, private endpoint access, supported runner networking and required trust posture. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Incorrect Answers
B:Protected deployment environments help enforce authorized release gates and restrict production secret access. It does not govern the condition described: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
C:Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. It does not govern the condition described: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
D:Third-party actions execute code in workflow security context and require trust, permission and change reviews. It does not govern the condition described: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
Question 512
GitHub Enterprise administration scenario — Choose GitHub-hosted or self-hosted runners by constraints. In an enterprise development environment: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
- Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host.
- Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job.
- Inspect all workflow triggers, secret references, required environments and existing repository security settings.
Explanation
Correct Answer
A:Compare build resource needs, private endpoint access, supported runner networking and required trust posture. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Incorrect Answers
B:Inspect runner group scope, repository allow policy, runner labels and the jobs scheduled on the same host. That check would not establish the decisive facts for this condition: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
C: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 compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
D: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 compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
Question 513
GitHub Enterprise administration scenario — Choose GitHub-hosted or self-hosted runners by constraints. In an enterprise development environment: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. 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.
- Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Explanation
Correct Answer
B:Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. Compare build resource needs, private endpoint access, supported runner networking and required trust posture. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
Incorrect Answers
A:Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs. That change would leave the reported problem unresolved: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
C:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. That change would leave the reported problem unresolved: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
D:Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. That change would leave the reported problem unresolved: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Question 514
GitHub Enterprise administration scenario — Choose GitHub-hosted or self-hosted runners by constraints. In an enterprise development environment: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. 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.
- Unit tests continue to pass without repository write permission and only the release job can publish intended changes.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
- The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
- Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
Explanation
Correct Answers
D:The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. Compare build resource needs, private endpoint access, supported runner networking and required trust posture. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
E:Compare build resource needs, private endpoint access, supported runner networking and required trust posture. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Incorrect Answers
A:Unit tests continue to pass without repository write permission and only the release job can publish intended changes. It would not verify whether the proposed change works: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
B:Check the secret's selected-repository visibility settings and every workflow currently referencing it. It would not provide the evidence needed for the paired diagnosis and follow-up: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Compare build resource needs, private endpoint access, supported runner networking and required trust posture. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
C: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 compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Compare build resource needs, private endpoint access, supported runner networking and required trust posture. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
Question 515
GitHub Enterprise administration scenario — Choose GitHub-hosted or self-hosted runners by constraints. In an enterprise development environment: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. 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.
- Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
- The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
- Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
- Runner group policies should constrain repository and organization access to trusted workload boundaries.
- Production deployments continue using federation and the retired key fails in a credential validation test.
Explanation
Correct Answers
A:Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
B:The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
D:Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
Incorrect Answers
C:Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. It does not implement the governing rule for this approval: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories.
E:Runner group policies should constrain repository and organization access to trusted workload boundaries. It is not the rule that supports the proposed change and acceptance test: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
F:Production deployments continue using federation and the retired key fails in a credential validation test. It would not independently demonstrate that the control works: A compute-heavy CI workload needs isolated internal network connectivity but leadership assumes the cheapest standard GitHub-hosted runner can reach private build dependencies by default. The representative build reaches its allowed dependencies and remains isolated from untrusted repositories. Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
Question 516
GitHub Enterprise administration scenario — Configure larger hosted runner networking appropriately. In an enterprise development environment: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. 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.
- Organization secrets should be shared according to specific repository and environment authorization needs.
- Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
- Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow.
- Larger runners have configurable resource and networking capabilities that require matching security and access policies.
Explanation
Correct Answer
D:Larger runners have configurable resource and networking capabilities that require matching security and access policies. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
Incorrect Answers
A:Organization secrets should be shared according to specific repository and environment authorization needs. It does not govern the condition described: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
B:Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It does not govern the condition described: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
C:Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow. It does not govern the condition described: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
Question 517
GitHub Enterprise administration scenario — Configure larger hosted runner networking appropriately. In an enterprise development environment: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
- Review historical execution durations, external call retry behavior and the workflow's current timeout settings.
- Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
- Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
Explanation
Correct Answer
A:Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. Larger runners have configurable resource and networking capabilities that require matching security and access policies. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
Incorrect Answers
B:Review historical execution durations, external call retry behavior and the workflow's current timeout settings. That check would not establish the decisive facts for this condition: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
C:Review runner persistence, network reachability, PR trust conditions and available credentials or caches. That check would not establish the decisive facts for this condition: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
D:Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. That check would not establish the decisive facts for this condition: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
Question 518
GitHub Enterprise administration scenario — Configure larger hosted runner networking appropriately. In an enterprise development environment: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. 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.
- Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
- Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries.
Explanation
Correct Answer
A:Create the supported larger runner configuration and restrict it to approved repositories or runner groups. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
Incorrect Answers
B:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. That change would leave the reported problem unresolved: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
C:Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. That change would leave the reported problem unresolved: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
D:Grant approved access to the central workflow repository or adjust the reuse design within supported account boundaries. That change would leave the reported problem unresolved: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
Question 519
GitHub Enterprise administration scenario — Configure larger hosted runner networking appropriately. In an enterprise development environment: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
- An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
- Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
- Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
- An authorized workflow dispatches to the restored runner group and execution results are visible.
Explanation
Correct Answers
A:Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
B:An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
Incorrect Answers
C:Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. It would not provide the evidence needed for the paired diagnosis and follow-up: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
D:Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. It would not provide the evidence needed for the paired diagnosis and follow-up: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
E:An authorized workflow dispatches to the restored runner group and execution results are visible. It would not verify whether the proposed change works: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
Question 520
GitHub Enterprise administration scenario — Configure larger hosted runner networking appropriately. In an enterprise development environment: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. 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.
- Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership.
- Larger runners have configurable resource and networking capabilities that require matching security and access policies.
- Production deployments continue using federation and the retired key fails in a credential validation test.
- Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
- An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
- Limit secret availability to approved repositories and document the integration owner and rotation schedule.
Explanation
Correct Answers
B:Larger runners have configurable resource and networking capabilities that require matching security and access policies. Create the supported larger runner configuration and restrict it to approved repositories or runner groups. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
D:Create the supported larger runner configuration and restrict it to approved repositories or runner groups. Larger runners have configurable resource and networking capabilities that require matching security and access policies. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.
E:An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. Create the supported larger runner configuration and restrict it to approved repositories or runner groups. Larger runners have configurable resource and networking capabilities that require matching security and access policies.
Incorrect Answers
A:Runner selection must account for isolation, networking, platform capabilities, cost and maintenance ownership. It is not the rule that supports the proposed change and acceptance test: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Larger runners have configurable resource and networking capabilities that require matching security and access policies. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
C:Production deployments continue using federation and the retired key fails in a credential validation test. It would not independently demonstrate that the control works: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access. Create the supported larger runner configuration and restrict it to approved repositories or runner groups.
F:Limit secret availability to approved repositories and document the integration owner and rotation schedule. It does not implement the governing rule for this approval: An organization buys larger GitHub-hosted runners to reach an allowlisted private service but does not account for required runner networking configuration. Create the supported larger runner configuration and restrict it to approved repositories or runner groups. An authorized job reaches its private service from allowed network paths and a test unapproved job is denied runner access.