GitHub-Actions Exam Practice Test Instant Access

Question 1

As a developer, your self-hosted runner sometimes looses connection while running jobs. How should you troubleshoot the issue affecting your self-hosted runner?

ASet the DEBUG environment variable to true before starting the self-hosted runner to produce more verbose console output.

BLocate the self-hosted runner in your repository's settings page and download its log archive.

CAccess the self-hosted runner's installation directory and look for log files in the _diag folder.

DStart the self-hosted runner with the --debug flag to produce more verbose console output.

Answer : C

When troubleshooting a self-hosted runner, you can access the _diag folder located in the self-hosted runner's installation directory. This folder contains diagnostic logs that can help you identify the root cause of issues, such as connection problems.

Question 2

As a DevOps engineer developing a JavaScript action, you need to include annotations to pass warning messages to workflow runners. Which code snippet can you use to implement an annotation in your Actions?

Acore.info('Something went wrong, but it\'s not bad enough to fail the build.')

Bcore.notice('Something went wrong, but it\'s not bad enough to fail the build.')

Ccore.warning('Something went wrong, but it\'s not bad enough to fail the build.')

Dcore.warn('Something went wrong, but it\'s not bad enough to fail the build.')

Answer : C

The core.warning() function from the @actions/core package is used to create a warning message in the workflow logs. This is an annotation type that informs users about issues that don't require failing the build but still need attention.

Question 3

Which files are required for a Docker container action in addition to the source code? (Choose two.)

ADockerfile

BActionfile

Cmetadata.yml

Daction.yml

Answer : A, D

Dockerfile: The Dockerfile is required for Docker container actions. It defines the environment for the action, specifying the base image, dependencies, and any commands to set up the action's runtime inside the container.

action.yml: The action.yml file is required for all GitHub Actions, including Docker container actions. It contains metadata about the action, including the inputs, outputs, and the runtime environment (which in this case is Docker, defined under runs.using).

Question 4

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

AThe action's repository includes @actions/core in the root directory.

BThe action's repository name includes the keyword 'Docker.'

CThe action.yml metadata file references a Dockerfile file.

DThe action.yml metadata file has the runs.using value set to Docker.

Answer : D

In a Docker container action, the action.yml file includes the runs.using field, which is set to docker to specify that the action runs inside a Docker container. This is the key indicator that the action is a Docker container action.

Question 5

Which scopes are available to define custom environment variables within a workflow file? (Choose three.)

Athe entire workflow, by using env at the top level of the workflow file

Ball jobs being run on a single Actions runner, by using runner.env at the top of the workflow file

Cthe entire stage, by using env at the top of the defined build stage

Dwithin the run attribute of a job step

Ethe contents of a job within a workflow, by using jobs.<job_id>.env

Fa specific step within a job, by using jobs.<job_id>.steps[*].env

Answer : A, D, F

You can define environment variables for the entire workflow by using the env key at the top level of the workflow file. These environment variables will be available to all jobs and steps within the workflow.

Environment variables can also be set within the run attribute of a job step, and these variables will be scoped only to that specific step.

You can set environment variables for specific steps within a job by using jobs.<job_id>.steps[*].env, which allows you to define variables that will only be available to that step.

Question 6

Which of the following is the best way for an enterprise to prevent certain marketplace actions from running?

ACreate a list of the actions that are restricted from being used as an enterprise policy. Every other action can be run.

BIt is not possible; if an action is in the marketplace, its use cannot be restricted.

CCreate a list that is maintained as a . yml file in a . github repository specified in the enterprise. Only these actions can be run.

DCreate a list of the actions that are allowed to run as an enterprise policy. Only these actions can be run.

Answer : D

The best way for an enterprise to control which GitHub Actions run is by creating a list of approved actions as an enterprise policy. This approach restricts workflows to only use the actions that are explicitly allowed, ensuring security and compliance within the organization.

Question 7

As a developer, you are designing a workflow and need to communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks. Which of the following options should you use?

Aenvironment variables

Bworkflow commands

Cself-hosted runners

Denable debug logging
E composite run step

Answer : B

Workflow commands are special commands that allow you to interact with the runner, set environment variables, output values, add debug messages, and perform other tasks within the workflow. These commands are used to modify the environment or influence the behavior of the GitHub Actions runner.

GitHub-Actions GitHub Actions Certificate Exam Practice Test