[Q26-Q41] GitHub Actions Certificate Exam Practice Tests 2025 Pass GitHub-Actions with confidence!

4.4/5 - (5 votes)

GitHub Actions Certificate Exam Practice Tests 2025 | Pass GitHub-Actions with confidence!

Practice GitHub Certification GitHub-Actions exam. Online Exam Practice Tests with detailed explanations!

GitHub GitHub-Actions Exam Syllabus Topics:

Topic	Details
Topic 1	Leverage GitHub Actions to publish to GitHub Packages: This section of the exam measures the skills of Software Engineers and Package Managers and covers the use of GitHub Actions for publishing to GitHub Packages. It focuses on setting up CI workflows for package publishing and authentication. One skill to be measured is configuring workflows to publish to package registries.
Topic 2	Build and deploy applications to Azure by using GitHub Actions: This section of the exam covers deploying applications to Azure using GitHub Actions. It focuses on continuous delivery workflows, environment protections, and Azure resource management.
Topic 3	Automate development tasks by using GitHub Actions: This section of the exam measures the skills of DevOps Engineers and covers the fundamentals of GitHub Actions. It focuses on understanding action types, planning automation workflows, and creating container actions. One skill to be measured is creating workflows triggered by repository events.
Topic 4	Create and publish custom GitHub actions: This section of the exam measures the skills of Software Engineers and covers the creation and publication of custom GitHub actions.

NEW QUESTION 26
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

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.

NEW QUESTION 27
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.)

Use cachingwhen reusing files that change rarely between jobs or workflow runs.

Use artifacts when referencingfiles produced by a job after a workflow has ended.

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

Use artifacts to access theGitHub Package Registry and download a package for a workflow

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.

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

REPOSITORY NAME

GITHUB REPOSITORY

ENV REPOSITORY

GITHUB WORKFLOW REPO

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.

NEW QUESTION 29
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.)

Use artifacts when referencingfiles produced by a job after a workflow has ended.

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

Use cachingwhen reusing files that change rarely between jobs or workflow runs.

Use artifacts to access theGitHub Package Registry and download a package for a workflow

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

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.

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.

NEW QUESTION 31
What can be used to set a failed status of an action from its code?

@actions/github toolkit

JavaScript dist/ folder

Dockerfile CMD

a non-zero exit code

output variable

composite run step

A non-zero exit code is used to set the status of an action to “failed” in GitHub Actions. When the action’s script or code exits with a non-zero status, it indicates failure, and GitHub will mark the action as failed.

NEW QUESTION 32
Which action type should be used to bundle a series of run steps into a reusable custom action?

Composite action

Bash script action

Docker container action

JavaScript action

A composite action allows you to bundle multiple steps into a single reusable action within a workflow. It is composed of multiple run steps or other actions and can be reused across workflows, making it the perfect choice for bundling a series of steps.

NEW QUESTION 33
You need to trigger a workflow using the GitHub API for activity that happens outside of GitHub. Which workflow event do you use?

check_suite

workflow_run

deployment

repository_dispatch

Therepository_dispatchevent allows you to trigger a workflow in response to external activity. It is commonly used when you need to trigger a workflow from outside GitHub, such as from another system or service, by sending a request to the GitHub API. This event provides flexibility to integrate with various external systems and trigger workflows in a GitHub repository.

NEW QUESTION 34
What metadata file in a custom action defines the main entry point?

action.js

index.js

action.yml

main.yml

The action.yml file is the metadata file in a custom GitHub Action that defines the main entry point, including information such as the inputs, outputs, description, and the runs key that specifies the main entry point (e.g., a script or a Docker container).

NEW QUESTION 35
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.

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.

NEW QUESTION 36
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.)

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

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.

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.

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.

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.

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.

NEW QUESTION 37
What will the output be for the following event trigger block in a workflow?

It throws a workflow syntax error, pointing to the types definition in issue_comment event.

It throws a workflow syntax error, pointing to the types definition in issues event.

It runs the workflow when an issue is edited or when an issue comment created.

It runs the workflow when an issue or issue comment in the workflow’s repository is created or modified.

It runs the workflow when an issue is created or edited, or when an issue or pull request comment is created.

The provided event trigger block specifies two types of events:
For issues: the workflow triggers on opened or edited issues.
For issue_comment: the workflow triggers when an issue comment is created.
This configuration ensures the workflow will run when either an issue is opened or edited, or an issue comment is created.

NEW QUESTION 38
What are the two ways to pass data between jobs? (Choose two.)

Use the copy action with restore parameter to restore the data from the cache

Use the copy action to save the data that should be passed in the artifacts folder.

Use the copy action with cache parameter to cache the data

Use data storage.

Use job outputs

Use artifact storage.

Job outputs are used to pass data from one job to another in a workflow. A job can produce output values (like variables or files), which can be referenced by subsequent jobs using theneedskeyword and${{ steps.step_id.
outputs.output_name }}syntax.
Artifact storage allows data (such as files or results) to be saved by a job and then retrieved by another job in a later step. This is commonly used for passing large amounts of data or files between jobs.

NEW QUESTION 39
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?

check_run

workflow_run

workflow_call

pull_request

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.

NEW QUESTION 40
In which locations can actions be referenced by workflows? (Choose three.)

a separate public repository

an .action extension file in the repository

the same repository as the workflow

a published Docker container image on Docker Hub

the runs-on: keyword of a workflow file

the repository’s Secrets settings page

a public NPM registry

Actions can be stored in a separate public repository and referenced in workflows by specifying the repository and action name.
Actions can also be stored in the same repository as the workflow and referenced directly by their path (e.g., ./.
github/actions/my-action).
Actions can be packaged as Docker container images and published to Docker Hub. These can then be referenced in workflows by specifying the Docker image.

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

Dockerfile

Actionfile

metadata.yml

action.yml

Dockerfile: TheDockerfileis 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: Theaction.ymlfile 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 underruns.using).

Loading …