GitHub Actions GitHub-Actions Exam Questions

Preparing for the GitHub-Actions exam is simple with ExamsTeacher. We offer easy-to-understand study materials that help you learn the most important exam topics. You can study using our PDF questions, practice online with a real exam-style test, or use the desktop practice software. Choose the study method that works best for you and prepare at your own pace.

At ExamsTeacher, we keep our GitHub-Actions practice questions up to date. Whenever the exam syllabus or objectives change, we update our study materials so you always learn the latest topics. This helps you save time, avoid outdated content, and feel more confident when you take your exam.

Question #1 (Topic: Demo Questions)

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

Use the actions/setup-docker action

Authenticate to the GitHub Container Registry.

Build the container image.

Push the image to the GitHub Container Registry

Pull the image from the GitHub Container Registry

Correct Answer: A, B, D

Question #2 (Topic: Demo Questions)

As a developer, you have a 10-MB data set that is required in a specific workflow. Which stepsshould you perform so the dataset is stored encrypted and can be decrypted during the workflow? (Choose three.)

Encrypt the dataset.

Leverage the actions/download-secret action in the workflow.

Store the dataset in a GitHub encrypted secret.

Store the encryption keys in a GitHub encrypted secret.

Compress the dataset

Commit the encrypted dataset to the same repository as the workflow

Create a GitHub encrypted secret with the Large object option selected and upload the dataset.

Correct Answer: A, C, D

Explanation:

First, the dataset should be encrypted before being stored. This ensures that the data is protected when stored in a repository. The encrypted dataset can be stored in a GitHub secret, ensuring it is securely kept and not exposed publicly. The encryption key needed to decrypt the dataset should also be stored in a GitHub secret to maintain security during the workflow, allowing access only when needed.

Question #3 (Topic: Demo Questions)

Which statement is true about using default environment variables?

The environment variables can be read in workflows using the ENV: variable_name syntax.

The environment variables created should be prefixed with GITHUB_ to ensure they can be accessed in workflows

The environment variables can be set in the defaults:sections of the workflow

The GITHUB_WORKSPACE environment variable should be used to access files from within the runner

Correct Answer: D

Explanation:

GITHUB_WORKSPACE is a default environment variable in GitHub Actions that points to the directory on the runner where your repository is checked out. This variable allows you to access files within your repository during the workflow.

Question #4 (Topic: Demo Questions)

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

ENV_ACTOR

GITHUB_WORKFLOW_ACTOR

GITHUB_ACTOR

GITHUB_USER

Correct Answer: C

Explanation:

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 #5 (Topic: Demo Questions)

Which workflow commands send information from the runner? (Choose two.)

reading from environment variables

setting a debug message

populating variables in a Dockerfile

setting output parameters

Correct Answer: B, D

Explanation:

Setting a debug message using ::debug:: command sends a message to the logs, helping with troubleshooting and providing insight into the workflow run.

Setting output parameters using ::set-output sends data from a job step to subsequent steps or jobs, which can be used later in the workflow.

Page: 1 / 1