Microsoft GH-100 Practice Test 48
Question 470
GitHub Enterprise administration scenario — Prevent workflow expression injection. In an enterprise development environment: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. 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.
- A fork pull request cannot access internal runner resources while its safe build tests still execute.
- Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests.
- Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
- Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
- A malicious test title is processed as inert data and cannot trigger an unintended shell command.
- Privileged workflow triggers require strict separation from untrusted pull request code and controlled checkout targets.
Explanation
Correct Answers
C:Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
D:Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
E:A malicious test title is processed as inert data and cannot trigger an unintended shell command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
Incorrect Answers
A:A fork pull request cannot access internal runner resources while its safe build tests still execute. It would not independently demonstrate that the control works: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. A malicious test title is processed as inert data and cannot trigger an unintended shell command. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
B:Publish a versioned approved reusable workflow and migrate caller repositories through reviewed pull requests. It does not implement the governing rule for this approval: A workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. A malicious test title is processed as inert data and cannot trigger an unintended shell command.
F: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 workflow embeds the pull request title directly into a shell command and a tester demonstrates that quotes inside the title change the command meaning. Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
Question 471
GitHub Enterprise administration scenario — Adopt OIDC for cloud deployments. In an enterprise development environment: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. 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.
- OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
- Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
- Third-party actions execute code in workflow security context and require trust, permission and change reviews.
- Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
Explanation
Correct Answer
A:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
Incorrect Answers
B:Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. It does not govern the condition described: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
C:Third-party actions execute code in workflow security context and require trust, permission and change reviews. It does not govern the condition described: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
D:Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. It does not govern the condition described: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
Question 472
GitHub Enterprise administration scenario — Adopt OIDC for cloud deployments. In an enterprise development environment: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand.
- Inspect effective GITHUB_TOKEN settings, event types and the API actions made by the test job.
- Correlate audit log policy-change events, runner group access history and approved maintenance tickets.
- Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
Explanation
Correct Answer
D:Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
Incorrect Answers
A:Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand. That check would not establish the decisive facts for this condition: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
B: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: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
C: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: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
Question 473
GitHub Enterprise administration scenario — Adopt OIDC for cloud deployments. In an enterprise development environment: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. 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.
- Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
- Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
- Set read-only token defaults or explicit least-privilege job permissions and grant writes only to reviewed publishing jobs.
Explanation
Correct Answer
B:Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
Incorrect Answers
A:Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. That change would leave the reported problem unresolved: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
C:Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. That change would leave the reported problem unresolved: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
D:Set read-only token defaults or explicit least-privilege job permissions and grant writes only to reviewed publishing jobs. That change would leave the reported problem unresolved: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
Question 474
GitHub Enterprise administration scenario — Adopt OIDC for cloud deployments. In an enterprise development environment: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. 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.
- Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
- Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
- Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand.
- Monthly minutes fall to planned limits while critical build and security checks continue to run.
- Review runner size and OS, assigned IP or private networking requirements and which repositories may use it.
Explanation
Correct Answers
A:Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
B:Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
Incorrect Answers
C:Inspect queued job history, runner resource saturation, labels, groups and concurrent build demand. It would not provide the evidence needed for the paired diagnosis and follow-up: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
D:Monthly minutes fall to planned limits while critical build and security checks continue to run. It would not verify whether the proposed change works: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
E:Review runner size and OS, assigned IP or private networking requirements and which repositories may use it. It would not provide the evidence needed for the paired diagnosis and follow-up: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
Question 475
GitHub Enterprise administration scenario — Adopt OIDC for cloud deployments. In an enterprise development environment: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. 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.
- Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
- Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working.
- OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
- Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
- 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.
Explanation
Correct Answers
A:Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
C:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
D:Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
Incorrect Answers
B:Unapproved repositories cannot access the secret while intended jobs in the selected projects continue working. It would not independently demonstrate that the control works: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
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: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key.
F:Provision job-scoped ephemeral runners with approved images, restricted network access and safe destruction after use. It does not implement the governing rule for this approval: GitHub Actions deployment jobs store a long-lived cloud access key as a repository secret and require recurring manual rotation. Configure a trusted cloud role for GitHub OIDC and remove the unnecessary long-lived deployment key. Only the designated reviewed workflow can assume the cloud role and deployments succeed without static cloud keys.
Question 476
GitHub Enterprise administration scenario — Constrain OIDC trust to reviewed workflow identity. In an enterprise development environment: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. 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 and job-level token permissions should be restricted to minimum required operations.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
- Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments.
Explanation
Correct Answer
C:Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Incorrect Answers
A:Workflow and job-level token permissions should be restricted to minimum required operations. It does not govern the condition described: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
B: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 cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
D:Workflow concurrency controls can serialize mutually exclusive deployments when aligned with protected environments. It does not govern the condition described: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
Question 477
GitHub Enterprise administration scenario — Constrain OIDC trust to reviewed workflow identity. In an enterprise development environment: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
- Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use.
- Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
- Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
Explanation
Correct Answer
C:Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Incorrect Answers
A:Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior. That check would not establish the decisive facts for this condition: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
B:Inspect cloud trust settings, workflow identity claims, repository environments and current deployment secret use. That check would not establish the decisive facts for this condition: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
D: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 cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
Question 478
GitHub Enterprise administration scenario — Constrain OIDC trust to reviewed workflow identity. In an enterprise development environment: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. 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.
- Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
- Restore the supported runner service or replace the failed agent through an approved capacity and image process.
- Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
- Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
Explanation
Correct Answer
A:Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
Incorrect Answers
B: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 cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
C:Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. That change would leave the reported problem unresolved: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
D:Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. That change would leave the reported problem unresolved: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Question 479
GitHub Enterprise administration scenario — Constrain OIDC trust to reviewed workflow identity. In an enterprise development environment: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. The change reviewer separates a justified investigation from a merely plausible fix. Select EXACTLY TWO: the decisive diagnostic evidence required BEFORE change and the independent successful result that must be verified AFTER change.
- The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it.
- Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows.
- Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
- Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
- Inspect which repositories actually use the template and how enterprise Actions rules control alternatives.
Explanation
Correct Answers
B:Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
D:Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
Incorrect Answers
A:The release workflow runs against the reviewed revision and a change in upstream tags cannot silently replace it. It would not verify whether the proposed change works: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
C: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 cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
E:Inspect which repositories actually use the template and how enterprise Actions rules control alternatives. It would not provide the evidence needed for the paired diagnosis and follow-up: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Review OIDC subject and custom claims, role trust policy, ref restrictions and approved release workflows. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
Question 480
GitHub Enterprise administration scenario — Constrain OIDC trust to reviewed workflow identity. In an enterprise development environment: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. 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.
- Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
- OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers.
- Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities.
- Runner group access matches the approved organization list and the change actor is recorded for investigation.
- Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
- Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
Explanation
Correct Answers
A:Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
E:Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name.
F:Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
Incorrect Answers
B:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. It is not the rule that supports the proposed change and acceptance test: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Cloud identity federation must validate specific authorized workflow or environment claims, not merely a broad organization name. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
C:Choose a supported hosted or self-hosted runner model with approved network paths and documented maintenance responsibilities. It does not implement the governing rule for this approval: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role.
D:Runner group access matches the approved organization list and the change actor is recorded for investigation. It would not independently demonstrate that the control works: A cloud administrator allows any workflow from an entire GitHub organization to assume a production deployment role because all repositories share a common enterprise. Authorized release jobs receive short-lived credentials while a different repository or branch fails to assume the production role. Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.