Weekend Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = simple70

Home
GitHub
GitHub Certification
GitHub-Actions
GitHub Actions Certificate Exam Questions and Answers

Pass the GitHub Certification GitHub-Actions Questions and answers with ExamsMirror

Practice at least 50% of the questions to maximize your chances of passing.

Exam GitHub-Actions Premium Access

View all detail and faqs for the GitHub-Actions exam

Go to Exam

383 Students Passed

94% Average Score

93% Same Questions

Viewing page 1 out of 3 pages

Viewing questions 1-10 out of questions

Questions # 1:

Which of the following statements are true regarding the use of GitHub Actions on a GitHub Enterprise Server instance? (Choose three.)

Options:

Use of GitHub Actions on GitHub Enterprise Server requires a persistent internet connection

Actions created by GitHub are automatically available and cannot be disabled

Most GitHub authored actions are automatically bundled for use on GitHub Enterprise Server

Third party actions can be used on GitHub Enterprise Server by configuring GitHub Connect

Actions must be defined in the .github repository

Third party actions can be manually synchronized for use on GitHub Enterprise Server

Answer

A, D, F

Explanation

GitHub Actions on GitHub Enterprise Server often requires an internet connection, especially for accessing actions from the GitHub Marketplace or third-party actions unless they are manually synced to the server.

To use third-party actions on GitHub Enterprise Server, GitHub Connect can be used to establish a connection between the server and GitHub.com, enabling access to third-party actions.

Third-party actions can also be manually synchronized to the GitHub Enterprise Server, making them available for use in workflows.

Questions # 2:

You are a developer working on developing reusable workflows for your organization. What keyword should be included as part of the reusable workflow event triggers?

Options:

check_run

workflow_run

workflow_call

pull_request

Answer

Explanation

The workflow_call event is used to trigger a reusable workflow from another workflow. This allows you to create workflows that can be reused in multiple places within your organization, enabling better modularity and reducing duplication.

Questions # 3:

GitHub-hosted runners support which capabilities? (Choose two.)

Options:

automatic patching of both the runner and the underlying OS

automatic file-system caching between workflow runs

support for Linux, Windows, and mac

support for a variety of Linux variations including CentOS, Fedora, and Debian

requiring a payment mechanism (e.g., credit card) to use for private repositories

Answer

C, D

Explanation

GitHub-hosted runners automatically handle patching, meaning they will be kept up to date with the latest security updates and software patches for both the runner environment and the underlying operating system.

GitHub-hosted runners support Linux, Windows, and macOS, giving you flexibility to run workflows on different operating systems without needing to manage your own self-hosted runners.

Questions # 4:

You installed specific software on a Linux self-hosted runner. You have users with workflows that need to be able to select the runner based on the identified custom software. Which steps should you perform to prepare the runner and your users to run these workflows? (Choose two.)

Options:

Create the group custom-software-on-linux and move the runner into the group.

Inform users to identify the runner based on the group.

Add the label custom-software to the runner.

Configure the webhook and network to enable GitHub to trigger workflow.

Add the label linux to the runner.

Answer

B, C

Explanation

Once the runner is properly configured and labeled, users should be informed to select the specific runner by identifying the label or group name when defining the runner in their workflows.

Adding a custom label (likecustom-software) to the runner makes it easier for users to select the runner in their workflows by using theruns-onkey, which allows them to choose this specific runner based on its label.

Questions # 5:

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

Options:

to leverage a self-hosted runner

to create a repository secret

to publish to GitHub Packages

to create issues in the repo

to read from the file system on the runner

to add a member to an organization

Answer

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.

Questions # 6:

Which default GitHub environment variable indicates the owner and repository name?

Options:

REPOSITORY NAME

GITHUB REPOSITORY

ENV REPOSITORY

GITHUB WORKFLOW REPO

Answer

Explanation

The GITHUB_REPOSITORY environment variable contains the owner and repository name in the format owner/repository. It is automatically provided by GitHub Actions and can be used to reference the repository in workflows.

Questions # 7:

As a developer, you need to create a custom action written in Python. Which action type should you choose?

Options:

JavaScript action

composite run step

Python action

Docker container action

Answer

Explanation

ADocker container actionis ideal for custom actions that require specific environments or dependencies, such as Python. By creating a Docker container, you can define the environment with the necessary Python version and dependencies, and your Python code can run inside that container.

Questions # 8:

Which statement is true about using default environment variables?

Options:

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.

Answer

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.

Questions # 9:

How can GitHub Actions encrypted secrets be used in if: conditionals within a workflow job?

Options:

Set the encrypted secret as a job-level environment variable and then reference the environment variable within the conditional statement.

Create a job dependency that exposes the encrypted secret as a job output, which can then be leveraged in a subsequent dependent job.

Use the secrets context within the conditional statement, e.g. ${{ secrets.MySuperSecret }}.

Use a workflow command to expose the encrypted secret via a step's output parameter and then use the step output in the job's if: conditional.

Answer

Explanation

GitHub Actions encrypted secrets can be accessed in workflows using thesecretscontext. You can directly reference the secret within anif:conditional using${{ secrets.MySuperSecret }}to determine whether a job or step should run based on the secret's value.

Questions # 10:

As a DevOps engineer, you are developing a container action. You need to execute a cleanup script after completing the main script execution. Which code block should be used to define the cleanup script?

Options:

Answer

Explanation

The correct syntax for specifying a cleanup script to be run after the main entry point is executed in a Docker-based GitHub Action is to use thepostkey. This ensures thatcleanup.shruns after the main script (main.sh) has completed.

Viewing page 1 out of 3 pages

Viewing questions 1-10 out of questions