What is a valid scenario regarding environment secrets?

Question

Options

• Aconfiguring environment secrets for connecting to GitHub Enterprise Server
• Bconfiguring environment secrets to automatically pull from Azure Key Vault
• Censuring a job cannot access environment secrets until approval is obtained from a required
• Densuring only a specific step can access an environment secret

• A
  88% (36)
• B
  5% (2)
• C
  7% (3)

Explanation

Environment secrets in GitHub Actions are scoped to a specific deployment environment (e.g., production, staging) and are used to store sensitive credentials needed for jobs targeting that environment. Storing a connection key or credential for GitHub Enterprise Server as an environment secret is a textbook valid use case - the secret is tied to the environment where the deployment occurs. Option B is incorrect because environment secrets do not natively auto-pull from Azure Key Vault; that requires explicit workflow steps or integrations. Option C describes a behavior of environment protection rules (required reviewers), not a configuration scenario for environment secrets themselves. Option D is invalid because GitHub Actions does not support restricting secret access to individual steps - secrets are available at the job level once the environment is accessed.

No community discussion yet for this question.