GitHub-Actions Exam Practice Test Instant Access

Question 1

As a developer, which workflow steps should you perform to publish an image to the GitHub Container Registry? (Choose three.)

AUse the actions/setup-docker action

BAuthenticate to the GitHub Container Registry.

CBuild the container image.

DPush the image to the GitHub Container Registry

EPull the image from the GitHub Container Registry.

Answer : A, B, D

A . Use the actions/setup-docker action

B . Authenticate to the GitHub Container Registry.

C . Build the container image.

D . Push the image to the GitHub Container Registry

E . Pull the image from the GitHub Container Registry.

Question 2

As a developer, you are optimizing a GitHub workflow that uses and produces many different files. You need to determine when to use caching versus workflow artifacts. Which two statements are true? (Choose two.)

AUse caching when reusing files that change rarely between jobs or workflow runs.

BUse artifacts when referencing files produced by a job after a workflow has ended.

CUse caching to store cache entries for up to 30 days between accesses.

DUse artifacts to access the GitHub Package Registry and download a package for a workflow

Answer : A, B

Caching is ideal for files that change rarely, such as dependencies or build outputs, as it speeds up subsequent workflow runs by reusing previously cached files instead of re-downloading or rebuilding them.

Artifacts are used for persisting files produced during a job that need to be used in later jobs or after the workflow has ended, allowing them to be downloaded or referenced later.

Question 3

You are a developer, and your container jobs are failing on a self-hosted runner. Which requirements must you check to ensure that the self-hosted runner is properly configured? (Choose two.)

AThe self-hosted runner is running a Linux operating system.

BThe self-hosted runner is running a Windows operating system.

CDocker is installed on the self-hosted runner.

DKubernetes is installed on the self-hosted runner.

EThe service status of Kubernetes is 'active'.

Answer : A, C

While Docker can run on various operating systems, Linux is often the most common and preferred OS for containerized workloads. Docker works well on Linux and is a widely-used platform for running containers.

For container jobs to run on a self-hosted runner, Docker must be installed and properly configured on the runner. Docker is required to build and run containerized workloads in a GitHub Actions workflow.

Question 4

As a developer, what options should you recommend to implement standards for automation reuse? (Choose two.)

ACreate workflow templates and store them in the organization's .github repository.

BCreate reusable actions and workflows that can be called from other workflows.

CCreate a marketplace partition to publish reusable automation for the company.

DStore shared corporate actions in subfolders in a defined and documented internally accessible repository.

Answer : A, B

Creating workflow templates in the organization's .github repository allows the organization to standardize workflows and make them easily reusable across multiple repositories. This ensures consistency and simplifies maintenance.

Creating reusable actions and workflows that can be called from other workflows helps modularize and standardize automation tasks. These reusable components can be maintained centrally and called from different workflows across repositories.

Question 5

Which default GitHub environment variable indicates the name of the person or app that initiated a workflow?

AENV_ACTOR

BGITHUB_WORKFLOW_ACTOR

CGITHUB_ACTOR

DGITHUB_USER

Answer : C

The GITHUB_ACTOR environment variable indicates the name of the person or app that initiated the workflow. This variable is automatically provided by GitHub in the workflow and can be used to identify the user or application triggering the workflow.

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?

Arun: echo '::set-env name=FOO::bar'

Brun: echo 'FOO=bar' >> $GITHUB_ENV

Crun: echo ${{ $FOO=bar }}

Drun: export FOO=bar

Answer : B

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.

Question 7

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

AStore the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.

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

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

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

EStore 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 : C, E

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.

GitHub-Actions GitHub Actions Certificate Exam Practice Test