GitHub Actions Practice Test

GitHub Actions Practice Test practice questions, page 2 of 4, with answer review and explanations.

Question 6

Which of the following commands will set the $FOO environment variable within a script, so that it may be used in subsequent workflow job steps?

  1. run: echo "::set-env name=FOO::bar"
  2. run: echo "FOO=bar" >> $GITHUB_ENV
  3. run: echo ${{ $FOO=bar }}
  4. run: export FOO=bar

Question 7

You are reaching your organization's storage limit for GitHub artifacts and packages. What should you do to prevent the storage limit from being reached?

  1. via the .github repository owned by the organization
  2. via repositories owned by the organization
  3. via the GitHub Marketplace
  4. via a repository owned by a third party

Question 8

As a developer, how can you identify a JavaScript action on GitHub?

  1. The actions repository name includes the keyword "JavaScript."
  2. The action's repository includes a js.yml file in the .github/workflows directory.
  3. The action.yml metadata file references a package.json file.
  4. The action,yml metadata file has the runs.using value set to node16.

Question 9

In which scenarios could the GITHUB_TOKEN be used? (Choose two.)

  1. to leverage a self-hosted runner
  2. to create a repository secret
  3. to publish to GitHub Packages
  4. to create issues in the repo
  5. to read from the file system on the runner
  6. to add a member to an organization

Question 10

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.)

  1. Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.
  2. 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.
  3. 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.
  4. 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.
  5. 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.