GitHub Actions Reusable Workflows Quiz

1. What does the 'secrets: inherit' keyword do in a workflow call?

It passes all secrets from the calling workflow to the reusable workflow

It creates a copy of secrets in the reusable workflow's context

It encrypts all environment variables in the reusable workflow

It restricts secret access to the reusable workflow only

2. How do you provide a default value for an input in a reusable workflow?

Using the 'default' property in the input definition

Setting environment variables in the 'env' section

Using conditional logic in the workflow steps

Default values cannot be set for inputs

3. What is a best practice when designing reusable workflows for large teams?

Create focused, single-purpose workflows with clear inputs and outputs

Combine all CI/CD logic into one large reusable workflow

Avoid using inputs and outputs to keep workflows simple

Store all reusable workflows in a separate GitHub organization

4. Can a reusable workflow define its own 'on' trigger events (e.g., push, pull_request)?

No, reusable workflows can only use 'on: workflow_call'

Yes, reusable workflows can define any trigger event

Yes, but only push and pull_request triggers are allowed

No, all triggers must be defined in the calling workflow

5. What is the correct way to reference an input in a reusable workflow's job steps?

Inputs.

Github.event.inputs.

Env.

Steps.

6. How can you conditionally call a reusable workflow based on an event or condition?

Using 'if' statements in the job that calls the reusable workflow

Reusable workflows always execute regardless of conditions

By setting conditions in the reusable workflow's 'on' trigger

Using GitHub's conditional syntax in the workflow file

7. What is the purpose of the 'concurrency' keyword in a reusable workflow?

To limit concurrent job runs and prevent duplicate executions

To increase the number of parallel jobs in a workflow

To define which runners can execute the workflow

To set timeout limits for workflow execution

8. Can a reusable workflow be stored in a different repository than the calling workflow?

Yes, as long as the repository is public or the caller has access

No, reusable workflows must be in the same repository

Yes, but only for workflows in the same organization

No, GitHub does not support cross-repository workflow calls

9. In a reusable workflow, what does the 'required' property indicate?

Whether an input parameter must be provided by the caller

Whether a job must complete before others run

Whether the workflow must be called from the same repository

Whether outputs must be used by the caller

10. Which of the following is a valid input type in a reusable workflow?

String, number, boolean

String, array, object

String, integer, float

String, secret, file

11. What is the primary purpose of a reusable workflow in GitHub Actions?

To reduce code duplication and promote workflow reuse across repositories

To replace the need for Docker containers in CI/CD

To eliminate the use of secrets in workflows

To automatically deploy code to production without approval

12. How do you pass secrets to a reusable workflow from the calling workflow?

Using 'secrets: inherit' or explicitly passing secrets as inputs

Secrets are automatically inherited by all called workflows

Secrets cannot be passed to reusable workflows

By setting them as environment variables in the caller

13. What is the maximum number of levels of workflow nesting allowed in GitHub Actions?

3 levels (a workflow can call a reusable workflow that calls another reusable workflow)

Unlimited nesting is supported

1 level only (reusable workflows cannot call other workflows)

5 levels maximum

14. Can a reusable workflow call another reusable workflow?

Yes, workflows can be nested to multiple levels

No, only one level of reusable workflow is supported

Yes, but only if they are in the same repository

No, reusable workflows cannot call other workflows

15. What is the correct syntax to reference a reusable workflow output in the calling workflow?

Needs..outputs.

Workflow.outputs.

Steps..outputs.

Env.

16. How do reusable workflows pass data back to the calling workflow?

By defining outputs in the reusable workflow and referencing them in the caller

By writing to a shared file in the runner

By setting environment variables globally

By using GitHub API calls to update the caller

17. What syntax is used to call a reusable workflow from another workflow?

Uses: owner/repo/path/workflow.yml@ref

Run: ./workflow.yml

Import: workflow.yml

Include: path/to/workflow.yml

18. In a reusable workflow, how are input parameters defined?

Using the 'inputs' key under 'on: workflow_call'

Using environment variables in the 'env' section

Using secrets passed directly in the workflow call

Using GitHub's context variables like github.event

19. Which keyword defines a reusable workflow that can be called by other workflows?

On: workflow_call

On: workflow_reuse

Uses: workflow_template

Trigger: reusable