Microsoft GH-100 Practice Test 60
Question 590
GitHub Enterprise administration scenario — Integrate third-party vaults with scoped workflow identity. In an enterprise development environment: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. 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.
- Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
- Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
- Workflow and job-level token permissions should be restricted to minimum required operations.
- Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
- A fork pull request cannot influence the release job's executable dependencies through a shared cache.
- Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
Explanation
Correct Answers
A:Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
B:Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code. Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
D:Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
Incorrect Answers
C:Workflow and job-level token permissions should be restricted to minimum required operations. It is not the rule that supports the proposed change and acceptance test: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
E:A fork pull request cannot influence the release job's executable dependencies through a shared cache. It would not independently demonstrate that the control works: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code. Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
F: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 team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
Question 591
GitHub Enterprise administration scenario — Migrate from permanent cloud keys to federated tokens. In an enterprise development environment: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. 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.
- Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
- Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
- Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling.
- Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions.
Explanation
Correct Answer
B:Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Incorrect Answers
A:Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. It does not govern the condition described: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
C:Untrusted event data should not be interpolated into executable shell syntax without isolation or strict handling. It does not govern the condition described: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
D:Runner capacity and queue telemetry should determine scaling actions instead of broad permission exceptions. It does not govern the condition described: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
Question 592
GitHub Enterprise administration scenario — Migrate from permanent cloud keys to federated tokens. In an enterprise development environment: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. 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.
- Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job.
- Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
Explanation
Correct Answer
A:Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Incorrect Answers
B:Inspect trigger type, fork trust boundary, token permissions and secret availability for the affected job. That check would not establish the decisive facts for this condition: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
C:Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. That check would not establish the decisive facts for this condition: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
D:Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. That check would not establish the decisive facts for this condition: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
Question 593
GitHub Enterprise administration scenario — Migrate from permanent cloud keys to federated tokens. In an enterprise development environment: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. 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.
- Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
- Provide the supported workflow template together with enforceable Actions policies and measured adoption checks.
- Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs.
- Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
Explanation
Correct Answer
A:Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Production deployments continue using federation and the retired key fails in a credential validation test.
Incorrect Answers
B:Provide the supported workflow template together with enforceable Actions policies and measured adoption checks. That change would leave the reported problem unresolved: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
C:Retain only safe metadata operations in the privileged workflow and move fork-code tests into isolated low-privilege jobs. That change would leave the reported problem unresolved: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
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 release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Question 594
GitHub Enterprise administration scenario — Migrate from permanent cloud keys to federated tokens. In an enterprise development environment: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. 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 the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
- Production deployments continue using federation and the retired key fails in a credential validation test.
- Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
- Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns.
- Disposable artifacts expire on policy while required release evidence remains retrievable.
Explanation
Correct Answers
B:Production deployments continue using federation and the retired key fails in a credential validation test. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
C:Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Production deployments continue using federation and the retired key fails in a credential validation test. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Incorrect Answers
A: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 release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Production deployments continue using federation and the retired key fails in a credential validation test.
D:Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns. It would not provide the evidence needed for the paired diagnosis and follow-up: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. Production deployments continue using federation and the retired key fails in a credential validation test.
E:Disposable artifacts expire on policy while required release evidence remains retrievable. It would not verify whether the proposed change works: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Production deployments continue using federation and the retired key fails in a credential validation test. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Question 595
GitHub Enterprise administration scenario — Migrate from permanent cloud keys to federated tokens. In an enterprise development environment: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. 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.
- Production deployments continue using federation and the retired key fails in a credential validation test.
- A fork pull request cannot influence the release job's executable dependencies through a shared cache.
- Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
- Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
- Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
- Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
Explanation
Correct Answers
A:Production deployments continue using federation and the retired key fails in a credential validation test. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
D:Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. Production deployments continue using federation and the retired key fails in a credential validation test.
F:Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. Production deployments continue using federation and the retired key fails in a credential validation test.
Incorrect Answers
B:A fork pull request cannot influence the release job's executable dependencies through a shared cache. It would not independently demonstrate that the control works: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Production deployments continue using federation and the retired key fails in a credential validation test. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
C:Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. It is not the rule that supports the proposed change and acceptance test: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
E:Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. It does not implement the governing rule for this approval: A release workflow already supports GitHub OIDC but retains an unused long-lived cloud key after a successful federation pilot. Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. Production deployments continue using federation and the retired key fails in a credential validation test.
Question 596
GitHub Enterprise administration scenario — Pass secrets to reusable workflows with least privilege. In an enterprise development environment: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. 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.
- Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface.
- An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- Larger runners have configurable resource and networking capabilities that require matching security and access policies.
Explanation
Correct Answer
C:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
Incorrect Answers
A:Once a trusted federation path works, obsolete static secrets should be revoked to remove unnecessary compromise surface. It does not govern the condition described: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
B:An eligible online runner with valid connectivity and access is necessary for self-hosted workflow execution. It does not govern the condition described: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
D:Larger runners have configurable resource and networking capabilities that require matching security and access policies. It does not govern the condition described: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
Question 597
GitHub Enterprise administration scenario — Pass secrets to reusable workflows with least privilege. In an enterprise development environment: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference.
- Review runner persistence, network reachability, PR trust conditions and available credentials or caches.
- Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
- Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
Explanation
Correct Answer
C:Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
Incorrect Answers
A:Inspect the action repository provenance, requested workflow permissions, update history and verified commit reference. That check would not establish the decisive facts for this condition: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
B:Review runner persistence, network reachability, PR trust conditions and available credentials or caches. That check would not establish the decisive facts for this condition: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
D:Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. That check would not establish the decisive facts for this condition: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
Question 598
GitHub Enterprise administration scenario — Pass secrets to reusable workflows with least privilege. In an enterprise development environment: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. 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.
- Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
- Configure supported environment protection rules and route release jobs through the protected environment.
- Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts.
- Run untrusted PR checks on suitably isolated runners and reserve sensitive self-hosted capacity for trusted jobs.
Explanation
Correct Answer
A:Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
Incorrect Answers
B:Configure supported environment protection rules and route release jobs through the protected environment. That change would leave the reported problem unresolved: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
C:Separate untrusted validation from privileged deployment and remove secrets from fork-triggered execution contexts. That change would leave the reported problem unresolved: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
D: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 caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
Question 599
GitHub Enterprise administration scenario — Pass secrets to reusable workflows with least privilege. In an enterprise development environment: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. 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 which repositories actually use the template and how enterprise Actions rules control alternatives.
- Examine the caller's secret inheritance, callee permissions, environment protection and required credentials.
- Review environment branch restrictions, required reviewers, workflow triggers and production secret placement.
- The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation.
- The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
Explanation
Correct Answers
B:Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
E:The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
Incorrect Answers
A: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 caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
C:Review environment branch restrictions, required reviewers, workflow triggers and production secret placement. It would not provide the evidence needed for the paired diagnosis and follow-up: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Examine the caller's secret inheritance, callee permissions, environment protection and required credentials. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
D:The standardized release workflow preserves separate review-gated jobs and callers use the intended shared implementation. It would not verify whether the proposed change works: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
Question 600
GitHub Enterprise administration scenario — Pass secrets to reusable workflows with least privilege. In an enterprise development environment: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. 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.
- Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
- Workflow execution plans should balance required test coverage and resource cost within approved budgets.
- Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan.
- The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected.
- Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
- The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
Explanation
Correct Answers
A:Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
E:Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
F:The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose.
Incorrect Answers
B:Workflow execution plans should balance required test coverage and resource cost within approved budgets. It is not the rule that supports the proposed change and acceptance test: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Reusable workflow secret passing should be explicit and consistent with the callee's trust boundary and job purpose. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.
C:Retire and revoke the old cloud key, remove stale Actions secrets and retain a supported rollback plan. It does not implement the governing rule for this approval: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed.
D:The release pipeline runs with a vetted action while attempted substitution from an untrusted publisher is rejected. It would not independently demonstrate that the control works: A caller workflow gives a shared deployment workflow all inherited organization secrets although the shared job only needs one nonproduction token. The shared job succeeds using its minimum credential set and unrelated organization secrets are not exposed. Pass only the needed named secret or use protected environment identity with an approved shared workflow contract.