GitHub Actions Quiz 3 - JinalDesai.com

The quiz simulates GitHub Actions Certification questions, and facilitates aspirants to practice before the actual certification exam. You can study GitHub Actions here before taking this quiz.

Total questions: 30
Time: 50 minutes
Passing score: 70%

START QUIZ

#1. Your open-source publicly available repository contains a workflow with a `pull_request` event trigger. How can you require approval for workflow runs triggered from forks of your repository?

The workflow will not trigger for forks if using pull_request event. If you want to do that you should use fork_pull_request event trigger with require-approval flag

Setup required approvals for fork runs in the repository

Setup deployment protection rules for the repository

Setup branch protection rules for the repository

#2. Which of the following default environment variables contains the name of the person or app that initiated the workflow run?

GITHUB_ACTOR

GITHUB_WORKFLOW

GITHUB_USER

GITHUB_REPOSITORY

#3. When should you use `caching`?

When you want to save binaries produced by a build job to use in a subsequent deploy job to deploy a new version of an application.

When you want to save files produced by a job to view after a workflow run has ended, such as built binaries or build logs.

When you want to reuse files that do often change between jobs or workflow runs, such as build dependencies from a package management system.

When you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a package management system.

#4. When should you use `artifacts`? (Select two.)

Select all that apply:

Use artifacts to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a package management system.

Use artifacts to save files produced by a job to view after a workflow run has ended, such as test results or build logs.

Use artifacts to create new versions of your application together with release notes, mentions and/or contributors.

Use artifacts to save binaries produced by a build job to use in a subsequent deploy job to deploy a new version of an application.

#5. If a workflow runs on a `feature-a` branch, can it restore `caches` created in the default `main` branch?

Yes, all branches can restore caches created on the default branch.

Yes but only if no files were changed on feature-a branch.

No, caches can only be restored from the same branch.

Yes, all caches can be accessed by workflows on any branch within the same repository.

#6. To access an `artifact` that was created in another, previously triggered workflow run you can:

Use the actions/download-artifact action.

Use the actions/download-artifact action and make sure the artifact is not expired.

Use the actions/upload-artifact action.

You cannot access artifacts that were created in a different workflow run

#7. What should you use to store coverage reports or screenshots generated during a workflow that runs automated testing for a repository?

Caches

Packages

Releases

Artifacts

#8. In job `deploy`, if you want to access binaries (containing your application) that were created in job `build` you should

cache the binaries in build and read the files from cache in deploy

upload the binaries as artifacts in deploy and download them in build

cache the binaries in deploy and read the files from cache in build

upload the binaries as artifacts in build and download them in deploy

#9. A job called `job2` is using artifacts created in `job1`. Therefore, it's important to make sure `job1` finishes before `job2` starts looking for the artifacts. How should you create that dependency?

create this dependency by defining job2 after job1 in the workflow's .yaml definition

create this dependency using the concurrency keyword in job2

this dependency is created implicitly when using actions/download-artifact to download artifact from job1

create this dependency using the needs keyword in job2

#10. Which is true about `Starter Workflows` ? (Select three.)

Select all that apply:

Github provides and maintains starter workflows for different categories, languages and tooling

Your organization can create custom starter workflows for users in your organization

Starter workflows cannot call reusable workflows

Starter workflows are a paid Github feature

They allow users to leverage ready-to-use (or requiring minimal changes) workflow templates

Starter workflows are provided ready-to-use and cannot be modified or enhanced

#11. Secrets and configuration variables can be scoped to: (Select three.)

Select all that apply:

Multiple repositories that do not share an organization/enterprise

An environment in a repository

An environment shared across multiple repositories

A specific workflow in a repository

A single repository

A specific job in a workflow

The entire organization, or selected repositories in an organization

#12. For any action published in GitHub Marketplace, you can often use it in multiple versions, which approach is the most stable and secure?

Reference the main branch

Reference a version tag

Reference the commit SHA

#13. Which of these is a proper way of setting an output parameter `PET` with a value of `DOG` in a `step`.

echo "DOG=PET" >> "$GITHUB_OUTPUT"

gh set-output "DOG=PET"

gh set-output "PET=DOG"

echo "PET=DOG" >> "$GITHUB_OUTPUT"

#14. What Github-hosted runner types are available to use? (Select three.)

Select all that apply:

Ubuntu Linux

Windows

Android

macOS

ChromeOS

#15. What are the possible types of an input variable for a manually triggered workflow? (Select five.)

Select all that apply:

number

string

choice

input

dropdown

environment

boolean

select

#16. To stop a workflow from running temporarily without modifying the source code you should?

Use the Disable workflow option in GitHub Actions

Prevent any new commits to main branch

Remove secrets that are required for this workflow

Delete environment that is required for this workflow

#17. You want to create a reusable workflow `CI` that runs some quality checks, linting and tests on code changes. What event should trigger the `CI` workflow define to allow reusing it in other workflows?

workflow_call

workflow_dispatch

workflow_run

workflow_trigger

#18. What are the valid use cases for using defaults? (Select two.)

Select all that apply:

Using defaults.env on job level to set default environment variables for all steps in a single job

Using defaults.env on workflow level to set default environment variables for an entire workflow

Using defaults.run on job level to set default working-directory for all steps in a single job

Using defaults.run on step level to set default shell (e.g bash) for that single step

Using defaults.run on workflow level to set default shell (e.g bash) for an entire workflow

#19. If job B requires job A to be finished you have to:

use the requires keyword in job A to create this dependency

use the needs keyword in job A to create this dependency

use the needs keyword in job B to create this dependency

use the requires keyword in job B to create this dependency

#20. In a workflow with multiple jobs, if job A fails then:

the workflow immediately cancels all other jobs

the jobs that are dependent on job A are skipped

the jobs that are dependent on job A fail

#21. When using the `pull_request` and `pull_request_target` events, how do you configure the workflow to run only when targeting the `prod` branch?

Using branches filter

Using glob patterns

You create the workflow only on prod branch

Using branch filter

#22. Fill in the blank: When using `push` event trigger filters you can use patterns to target multiple branches

glob

scheme

action

regex

#23. Which event allows you to manually trigger a workflow from the GitHub UI?

workflow_dispatch

manual_trigger

workflow_trigger

manual_dispatch

#24. Which statement is correct regarding passing permissions to reusable workflows?

The GITHUB_TOKEN permissions passed from the caller workflow can be both downgraded and elevated by the called workflow.

The GITHUB_TOKEN permissions passed from the caller workflow can be only downgraded by the called workflow.

The GITHUB_TOKEN permissions passed from the caller workflow can be neither downgraded or elevated by the called workflow.

The GITHUB_TOKEN permissions passed from the caller workflow can be only elevated by the called workflow.

#25. What are the different permission levels you can assign to `GITHUB_TOKEN` in the `permissions` block?

none, write, read

read, write, delete

read, write

#26. Which of these is not a valid event that could trigger a workflow?

Cloning the repository

Committing a file to master branch

A branch is created

Adding a label to a pull request

#27. Which is true about workflows? (Select three.)

Select all that apply:

Workflows have to be defined in the .github/workflows directory

Workflows are written in any of .yaml, .json or .toml formats

Workflows can be shared in Github Marketplace

Workflows can only be run on a schedule

Workflows can run one or multiple jobs at a time

Workflows can be triggered manually, by an event or run on a schedule

Workflow can run only one job at a time

#28. Which components are required for a workflow? (Select two.)

Select all that apply:

Defined branches on which the workflow will run

Workflow name

One or more jobs

One or more events that will trigger the workflow

#29. Which event is triggered by a webhook action from outside of the repository?

webhook_dispatch

repository_dispatch

workflow_dispatch

api_dispatch

remote_dispatch

#30. You can use `permissions` to modify the `GITHUB_TOKEN` permissions on: (Select two.)

Select all that apply:

Job level

Workflow level

Step level

Finish

Results

pass

Post Views: 9

fail

Post Views: 9

Post Views: 9

#1. Your open-source publicly available repository contains a workflow with a `pull_request` event trigger. How can you require approval for workflow runs triggered from forks of your repository?

#2. Which of the following default environment variables contains the name of the person or app that initiated the workflow run?

#3. When should you use `caching`?

#4. When should you use `artifacts`? (Select two.)

#5. If a workflow runs on a `feature-a` branch, can it restore `caches` created in the default `main` branch?

#6. To access an `artifact` that was created in another, previously triggered workflow run you can:

#7. What should you use to store coverage reports or screenshots generated during a workflow that runs automated testing for a repository?

#8. In job `deploy`, if you want to access binaries (containing your application) that were created in job `build` you should

#9. A job called `job2` is using artifacts created in `job1`. Therefore, it's important to make sure `job1` finishes before `job2` starts looking for the artifacts. How should you create that dependency?

#10. Which is true about `Starter Workflows` ? (Select three.)

#11. Secrets and configuration variables can be scoped to: (Select three.)

#12. For any action published in GitHub Marketplace, you can often use it in multiple versions, which approach is the most stable and secure?

#13. Which of these is a proper way of setting an output parameter `PET` with a value of `DOG` in a `step`.

#14. What Github-hosted runner types are available to use? (Select three.)

#15. What are the possible types of an input variable for a manually triggered workflow? (Select five.)

#16. To stop a workflow from running temporarily without modifying the source code you should?

#17. You want to create a reusable workflow `CI` that runs some quality checks, linting and tests on code changes. What event should trigger the `CI` workflow define to allow reusing it in other workflows?

#18. What are the valid use cases for using **defaults**? (Select two.)

#19. If job B requires job A to be finished you have to:

#20. In a workflow with multiple jobs, if job A fails then:

#21. When using the `pull_request` and `pull_request_target` events, how do you configure the workflow to run only when targeting the `prod` branch?

#22. Fill in the blank: When using `push` event trigger filters you can use patterns to target multiple branches

#23. Which event allows you to manually trigger a workflow from the GitHub UI?

#24. Which statement is correct regarding passing permissions to reusable workflows?

#25. What are the different permission levels you can assign to `GITHUB_TOKEN` in the `permissions` block?

#26. Which of these is not a valid event that could trigger a workflow?

#27. Which is true about workflows? (Select three.)

#28. Which components are required for a workflow? (Select two.)

#29. Which event is triggered by a webhook action from outside of the repository?

#30. You can use `permissions` to modify the `GITHUB_TOKEN` permissions on: (Select two.)

Results

#18. What are the valid use cases for using defaults? (Select two.)