support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. GitHub
  4. GitHub Actions

GitHub GitHub Actions Exam Prep
GitHub Actions (Page 4 )

Updated On: 31-Aug-2026
Page 3 of 16
PDF with 115 Questions

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

Answer(s): B

Explanation:

The $GITHUB_ENV environment variable is used to set environment variables that persist across steps in a workflow job. By echoing FOO=bar into $GITHUB_ENV, the variable FOO will be available in subsequent steps within the same job.



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

Answer(s): B

Explanation:

To prevent reaching the storage limit for GitHub artifacts and packages, you should manage and clean up artifacts and packages stored in repositories owned by your organization. This includes deleting unnecessary artifacts and managing the lifecycle of packages, as they contribute directly to your organization's storage quota.



Based on the YAML below, which two statements are correct? (Choose two.)

  1. This workflow will publish a package to an npm registry.
  2. This workflow will publish a package to GitHub Packages.
  3. This workflow file is using a matrix strategy.
  4. The workflow job publish-npm will only run after the build job passes.

Answer(s): A,D

Explanation:

The publish-npm job includes the JS-DevTools/npm-publish action, which is used to publish an npm package to an npm registry.
The publish-npm job has the needs: build directive, meaning it will only run after the build job successfully completes.



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

Answer(s): C,D

Explanation:

The GITHUB_TOKEN is automatically provided by GitHub in workflows and can be used to authenticate API requests to GitHub, including publishing packages to GitHub Packages. The GITHUB_TOKEN is also used to authenticate API requests for actions like creating issues, commenting, or interacting with pull requests within the same repository.



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.

Answer(s): C,E

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.



  PDF
Viewing page 4 of 16
Viewing questions 16 - 20 out of 115 questions


Post your Comments and Discuss GitHub GitHub Actions exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!