GH-200 Token Practice Questions

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 teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Choose two.)

Select 2 answers.

• AA. Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.
• BB. Store the token as a GitHub encrypted secret in the same repo as the code. Create a reusable custom GitHub Action to access the token by the microservice at runtime.
• CC. Use a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
• DD. Store the token as a GitHub encrypted secret in the same repo as the code. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
• EE. Store the token as an organizational-level encrypted secret in GitHub. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.

Which of the following scenarios requires a developer to explicitly use the GITHUB_TOKEN or github.token secret within a workflow? (Choose two.)

Select 2 answers.

• AA. passing the GITHUB_TOKEN secret to an action that requires a token as an input
• BB. making an authenticated GitHub API request
• CC. checking out source code with the actions/checkout@v3 action
• DD. assigning non-default permissions to the GITHUB_TOKEN