As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different team

Question

Options

• AStore the token in a configuration file in a private repository. Use GitHub Actions to deploy the
• BStore the token as a GitHub encrypted secret in the same repo as the code. Create a reusable
• CUse a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During
• DStore the token as a GitHub encrypted secret in the same repo as the code. During deployment,
• EStore the token as an organizational-level encrypted secret in GitHub. During deployment, use

• A
  8% (2)
• B
  4% (1)
• C
  71% (17)
• D
  17% (4)

Explanation

Using a corporate secret store like HashiCorp Vault provides a secure, centralized location for sensitive information. GitHub Actions can then retrieve and store the token securely during deployment by setting it as an environment variable, ensuring the token remains secure and accessible at runtime. Storing the token as an organizational-level encrypted secret in GitHub ensures it is accessible across multiple repositories, minimizing management overhead. GitHub Actions can then use this secret during deployment by setting it as an environment variable, allowing the microservice to access it securely at runtime.

No community discussion yet for this question.