Free practice · No sign-up required
15 questions with answer explanations. Choose an answer below to begin.
Which GitHub feature allows you to define workflows using YAML files stored in the repository?
Understand core components and terminology of GitHub Actions.
0/15 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.
Learn by doing
Use official documentation and hands-on labs to work through topics you missed.
Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.
Which GitHub feature allows you to define workflows using YAML files stored in the repository?
Actions
Insights
Environments
Secrets
Correct answer
Actions
GitHub Actions uses YAML workflow files stored in the .github/workflows directory to define automated processes. These workflows can be triggered by various events such as pushes or pull requests.
What is the primary purpose of a workflow file in GitHub Actions?
To define automated processes and steps
To manage repository permissions
To store secrets securely
To track issues and pull requests
Correct answer
To define automated processes and steps
A workflow file describes a series of automated steps that run in response to defined events. It specifies jobs, steps, and the environment in which they execute.
Which event triggers a workflow when code is pushed to the main branch?
push
pull_request
schedule
workflow_dispatch
Correct answer
push
The push event is used to trigger workflows when commits are pushed to a branch. It can be filtered to specific branches like main.
What is the default shell used by GitHub Actions when running steps on Ubuntu runners?
bash
pwsh
cmd
sh
Correct answer
bash
On Ubuntu runners, the default shell for running commands is bash. This can be changed using the shell keyword if needed.
Which keyword is used to reference outputs from one step to another within the same job?
needs
outputs
steps
env
Correct answer
outputs
The outputs keyword allows a step to define data that can be accessed by subsequent steps using steps..outputs..
What is the purpose of the jobs..strategy.max-parallel setting in a workflow?
To limit the number of concurrent job runs
To set the maximum number of steps in a job
To define the runner label
To control retry attempts
Correct answer
To limit the number of concurrent job runs
This setting controls how many matrix job instances can run simultaneously. It helps manage resource usage and concurrency limits.
Which of the following is used to securely store sensitive information such as API keys in GitHub Actions?
Secrets
Variables
Artifacts
Environments
Correct answer
Secrets
GitHub Secrets allow you to store encrypted values that can be accessed in workflows. They are not exposed in logs and are only passed to steps that explicitly request them.
What does a job in a GitHub Actions workflow represent?
A single step in a workflow
A collection of steps that run on the same runner
A trigger for starting workflows
A repository permission setting
Correct answer
A collection of steps that run on the same runner
A job is a set of steps that execute on the same runner machine. Jobs can run independently or depend on other jobs using the needs keyword.
Which keyword allows a workflow to reuse a set of steps across multiple jobs?
composite
reusable
template
action
Correct answer
action
Reusable workflows are defined in a separate file and can be called from other workflows using the workflow_call trigger. They promote DRY principles.
What is the purpose of the if conditional in a workflow step?
To skip the step based on a condition
To define the runner label
To set environment variables
To trigger another workflow
Correct answer
To skip the step based on a condition
The if statement allows a step to run only when a specified condition evaluates to true. This helps control workflow execution dynamically.
Which GitHub Actions feature enables you to create custom logic that can be shared across workflows?
Actions
Environments
Secrets
Runners
Correct answer
Actions
Actions are reusable units of code that can encapsulate a single command or a set of commands. They can be published and shared across workflows.
What is the default concurrency behavior for GitHub Actions workflows in a repository?
All workflows run sequentially
Multiple workflows can run in parallel
Only one workflow can run at a time
Concurrency is disabled by default
Correct answer
Multiple workflows can run in parallel
By default, multiple workflows can run concurrently. You can limit concurrency using the concurrency keyword to prevent overlapping runs.
Which file path is used to store workflow definitions in a GitHub repository?
.github/workflows/
.git/actions/
workflows/.github/
actions/
Correct answer
.github/workflows/
Workflow files must be placed in the .github/workflows directory at the root of the repository. GitHub automatically detects and runs these workflows.
What is the role of a runner in GitHub Actions?
To host and execute workflow jobs
To manage repository settings
To review pull requests
To store workflow logs
Correct answer
To host and execute workflow jobs
A runner is a machine that runs your workflow jobs. It can be hosted by GitHub or self-hosted depending on your needs and permissions.
Which feature allows you to define different deployment strategies for environments?
Environments
Secrets
Labels
Contexts
Correct answer
Environments
Environments in GitHub Actions let you define deployment targets and associate protection rules, reviewers, and secrets specific to each environment.
Recall the answer before opening each card.
.github/workflows/ directory at the repository root. All YAML files in that folder are treated as workflows.
The push event. It can be filtered by branch (e.g., on: push: branches: [main]).
bash. It can be overridden using the shell keyword in a step.
Use steps. .outputs. within the workflow. The step must define outputs using the outputs keyword.
The maximum number of concurrent matrix job instances that can run at the same time.
As GitHub Secrets. They are encrypted and only passed to steps that explicitly reference them; never exposed in logs.
A collection of steps that run on the same runner. Jobs can run independently or depend on other jobs using the needs keyword.
workflow_call. It is defined in the reusable workflow as a trigger, and the caller uses the uses keyword with a path or reference.
It allows the step to run only when a specified condition evaluates to true. Otherwise, the step is skipped.
A reusable unit of custom logic that encapsulates commands in a single step. Actions can be shared across workflows.
Multiple workflows can run in parallel simultaneously with no limit. Use the concurrency keyword to restrict overlapping runs.
.github/workflows/ at the root of the repository. Workflow files are YAML and named descriptively (e.g., ci.yml).
A machine (hosted by GitHub or self-hosted) that executes workflow jobs. Runners have a configured operating system and environment.
Environments. They can have protection rules, required reviewers, and secrets specific to that environment.
By using the concurrency keyword with a group name. For example, concurrency: group: {{ github.workflow }} cancel-in-progress: true.
To override the default shell for that step. For example, shell: pwsh to use PowerShell.
pull_request. It can be filtered by types (e.g., opened, synchronize).
Use the outputs keyword at the job level and access them via needs. .outputs. .
It specifies the path to an action to run. The action can be in a public repository, local path, or Docker image.
To define job dependencies. The job will wait for all specified upstream jobs to complete successfully before starting.
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Connect the concepts
Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Workflows are defined in YAML files stored in .github/workflows/ at the repository root. Each workflow consists of one or more jobs, and each job contains a series of steps that run on the same runner. A runner (hosted or self-hosted) is the machine that executes the job. On Ubuntu runners, the default shell is bash. The primary purpose of a workflow file is to define automated processes triggered by events like push.
Workflows are triggered by events (e.g., push, pull_request). The if conditional allows steps or jobs to run only when a condition is met, enabling dynamic pipelines. The strategy.max-parallel setting controls how many concurrent matrix job instances execute. By default, multiple workflows can run in parallel; concurrency can be limited via the concurrency keyword. Outputs from one step can be passed to later steps using the outputs keyword.
Sensitive information like API keys is stored securely using GitHub Secrets. Secrets are encrypted and not exposed in logs; they are only accessible to steps that explicitly reference them. Environments provide a way to manage deployment targets with protection rules, reviewers, and environment-specific secrets. This ensures that sensitive data and deployment approvals are enforced per environment (e.g., production vs. staging).
Reusable workflows (defined via the workflow_call trigger) allow you to call a workflow from another workflow, promoting DRY principles. The action keyword is used to reference a composite or Docker action that encapsulates custom logic. Actions are the building blocks of workflows; they can be published and shared across repositories. Understanding these features helps modularize pipelines and reduce duplication.
Study workflow
Read the GitHub Actions documentation on workflow syntax. Pay special attention to the structure: name, on, jobs, runs-on, steps. Practice writing a simple workflow that runs on push to main and echoes a message.
Create workflows with different triggers (push, pull_request) and use the if conditional with expressions like success() or variables. Observe how jobs are skipped or run based on conditions.
Set up a repository secret and use it in a workflow (e.g., ${{ secrets.MY_SECRET }}). Create an environment with required reviewers and deploy a job to that environment to see approval in action.
Define a job that generates an output and pass it to a dependent job. Implement a matrix strategy with strategy.matrix and test the max-parallel setting to control concurrency.
Write a reusable workflow in .github/workflows/ with on: workflow_call. Then call it from another workflow. Next, create a simple composite action and use it in a step to encapsulate a command.
FAQ
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
The default shell on Ubuntu runners is bash. This can be changed using the shell keyword in a step to other options like pwsh, python, or sh.
Use the outputs keyword to define output variables in a step, then reference them in subsequent steps using steps.<step_id>.outputs.<output_name>.
A job is a collection of steps that run on the same runner. Steps are individual tasks within a job, such as running a command or using an action. Jobs can run in parallel or depend on others.
Yes, GitHub provides hosted runners for Windows, Ubuntu, and macOS. The runs-on keyword specifies the operating system. Windows runners use PowerShell as the default shell.
Use the concurrency keyword in a workflow to group runs by a key. This ensures that only one run per group executes at a time, cancelling any queued or running runs if a new one starts.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
