Microsoft GH-100 Practice Test 59
Question 580
GitHub Enterprise administration scenario — Audit self-hosted runner security changes. In an enterprise development environment: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. A controlled enterprise configuration review requires a coherent rationale, approved change and confirmed outcome. Select EXACTLY THREE: the governing GitHub administration principle, the proportionate authorized intervention AND the independently observable outcome for this scenario.
- Protected deployment environments help enforce authorized release gates and restrict production secret access.
- Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines.
- An authorized workflow dispatches to the restored runner group and execution results are visible.
- Changes to runner group access are privileged governance events requiring attribution and periodic review.
- Runner group access matches the approved organization list and the change actor is recorded for investigation.
- Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
Explanation
Correct Answers
D:Changes to runner group access are privileged governance events requiring attribution and periodic review. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Runner group access matches the approved organization list and the change actor is recorded for investigation.
E:Runner group access matches the approved organization list and the change actor is recorded for investigation. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Changes to runner group access are privileged governance events requiring attribution and periodic review.
F:Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Changes to runner group access are privileged governance events requiring attribution and periodic review. Runner group access matches the approved organization list and the change actor is recorded for investigation.
Incorrect Answers
A:Protected deployment environments help enforce authorized release gates and restrict production secret access. It is not the rule that supports the proposed change and acceptance test: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Changes to runner group access are privileged governance events requiring attribution and periodic review. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
B:Configure a supported allow policy with reviewed first-party or approved action exceptions and test representative pipelines. It does not implement the governing rule for this approval: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes. Runner group access matches the approved organization list and the change actor is recorded for investigation.
C:An authorized workflow dispatches to the restored runner group and execution results are visible. It would not independently demonstrate that the control works: A runner group suddenly permits all organizations after an administrator edits enterprise Actions settings, and no one knows who approved the change. Runner group access matches the approved organization list and the change actor is recorded for investigation. Revert the unapproved expansion and add ownership reviews or automated alerts for sensitive runner policy changes.
Question 581
GitHub Enterprise administration scenario — Prevent sensitive output from leaking in workflow logs. In an enterprise development environment: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. 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.
- Pull request code from untrusted forks should run under restricted credentials and cannot be assumed safe because it is in a workflow.
- Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required.
- Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
Explanation
Correct Answer
D:Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. Review log excerpts, secret and variable handling, debug flags and downstream log exports. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
Incorrect Answers
A:OIDC federation can replace static cloud credentials with short-lived, policy-constrained tokens for supported providers. It does not govern the condition described: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
B: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 Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
C:Ephemeral runner lifecycles help reduce cross-job persistence when self-hosted execution is required. It does not govern the condition described: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
Question 582
GitHub Enterprise administration scenario — Prevent sensitive output from leaking in workflow logs. In an enterprise development environment: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Review log excerpts, secret and variable handling, debug flags and downstream log exports.
- Inspect triggers, concurrency group expressions, active run histories and the deployment service's rollback behavior.
- Compare build resource needs, private endpoint access, supported runner networking and required trust posture.
- Inspect workflow action references, publisher trust, verified commits and the update process for pinned dependencies.
Explanation
Correct Answer
A:Review log excerpts, secret and variable handling, debug flags and downstream log exports. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
Incorrect Answers
B: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: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Review log excerpts, secret and variable handling, debug flags and downstream log exports.
C:Compare build resource needs, private endpoint access, supported runner networking and required trust posture. That check would not establish the decisive facts for this condition: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Review log excerpts, secret and variable handling, debug flags and downstream log exports.
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: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Review log excerpts, secret and variable handling, debug flags and downstream log exports.
Question 583
GitHub Enterprise administration scenario — Prevent sensitive output from leaking in workflow logs. In an enterprise development environment: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. 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.
- Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
- Limit secret availability to approved repositories and document the integration owner and rotation schedule.
- Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys.
- Correct the supported selector or provision an appropriately labeled authorized runner with approval.
Explanation
Correct Answer
A:Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. Review log excerpts, secret and variable handling, debug flags and downstream log exports. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
Incorrect Answers
B:Limit secret availability to approved repositories and document the integration owner and rotation schedule. That change would leave the reported problem unresolved: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
C:Isolate privileged caches or rebuild trusted dependencies for release paths using reviewed actions and keys. That change would leave the reported problem unresolved: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
D:Correct the supported selector or provision an appropriately labeled authorized runner with approval. That change would leave the reported problem unresolved: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
Question 584
GitHub Enterprise administration scenario — Prevent sensitive output from leaking in workflow logs. In an enterprise development environment: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. 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.
- New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow.
- Review log excerpts, secret and variable handling, debug flags and downstream log exports.
- Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions.
- Inspect the workflow YAML expression, job shell and all paths by which the user-controlled title reaches the command.
- A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
Explanation
Correct Answers
B:Review log excerpts, secret and variable handling, debug flags and downstream log exports. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
E:A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked. Review log excerpts, secret and variable handling, debug flags and downstream log exports. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
Incorrect Answers
A:New repositories can start from the standard template and the sampled required control is enforced even when a team edits its workflow. It would not verify whether the proposed change works: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
C:Compare copies of deployment steps, trigger contexts, secrets passed and existing shared workflow permissions. It would not provide the evidence needed for the paired diagnosis and follow-up: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Review log excerpts, secret and variable handling, debug flags and downstream log exports. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
D: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: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Review log excerpts, secret and variable handling, debug flags and downstream log exports. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
Question 585
GitHub Enterprise administration scenario — Prevent sensitive output from leaking in workflow logs. In an enterprise development environment: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. 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.
- Peak release jobs complete within an agreed queue-time target without crossing runner trust boundaries.
- Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions.
- Workflow execution plans should balance required test coverage and resource cost within approved budgets.
- Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
- A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
- Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
Explanation
Correct Answers
D:Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
E:A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets.
F:Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
Incorrect Answers
A:Peak release jobs complete within an agreed queue-time target without crossing runner trust boundaries. It would not independently demonstrate that the control works: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
B:Constrain federation to the correct repository and trusted environment or reusable workflow identity with documented exceptions. It does not implement the governing rule for this approval: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields. A test workflow emits only non-sensitive diagnostics and compromised credentials are revoked.
C: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: An Action prints the full deployment environment during debugging and several variables contain access tokens and private API URLs. Sensitive workflow values should not be logged even when GitHub masking reduces visibility for recognized secrets. Remove indiscriminate environment printing, rotate exposed credentials and constrain debugging to safe redacted fields.
Question 586
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. 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.
- Third-party actions execute code in workflow security context and require trust, permission and change reviews.
- Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
- Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks.
Explanation
Correct Answer
C:Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
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 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.
B:Third-party actions execute code in workflow security context and require trust, permission and change reviews. It does not govern the condition described: 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.
D:Private workflow sharing across repositories requires supported enterprise or organization access policy and trust checks. It does not govern the condition described: 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.
Question 587
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. Before changing enterprise policies, permissions or workflows, which diagnostic check BEST establishes the decisive fact? Choose ONE best answer.
- Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
- Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows.
- Check the secret's selected-repository visibility settings and every workflow currently referencing it.
- Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
Explanation
Correct Answer
A:Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. 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.
Incorrect Answers
B:Review the enterprise action policy, affected organization overrides and the exact third-party action references in active workflows. That check would not establish the decisive facts for this condition: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
C:Check the secret's selected-repository visibility settings and every workflow currently referencing it. That check would not establish the decisive facts for this condition: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
D:Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage. That check would not establish the decisive facts for this condition: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
Question 588
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. 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.
- Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation.
- Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs.
- Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse.
- Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed.
Explanation
Correct Answer
B:Configure a least-privilege vault integration and use short-lived authenticated retrieval from trusted deployment jobs. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
Incorrect Answers
A:Move external values through appropriately quoted environment variables or vetted actions and remove unsafe command interpolation. That change would leave the reported problem unresolved: A 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.
C:Use reusable workflows for centralized multi-job policy and composite actions only for appropriate step-level reuse. That change would leave the reported problem unresolved: A 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.
D:Set appropriate supported retention limits and move mandatory evidence to a governed repository where needed. That change would leave the reported problem unresolved: 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.
Question 589
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. 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.
- Verify successful OIDC role assumption, job identity restrictions, secret references and the old key's last usage.
- Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
- Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls.
- Inspect required job boundaries, environment approvals, runner types and existing code reuse patterns.
- Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates.
Explanation
Correct Answers
B:Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. Actions can retrieve secrets from supported vault-backed integrations using controlled workflow identity and network configuration.
E:Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. 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.
Incorrect Answers
A: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: A team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
C:Sample callers invoke the same reviewed workflow revision and conform to the required deployment controls. It would not verify whether the proposed change 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.
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 team stores production deployment credentials in a reusable script file because it has not connected its existing enterprise vault to GitHub Actions. Inspect vault roles, supported federation mechanisms, workflow permissions, secret consumers and review gates. Only an approved deployment job retrieves its authorized secret and no secret is stored in repository source code.
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.