GitHub Actions CI/CD Fundamentals Quiz Quiz

Evaluate your understanding of continuous integration and continuous deployment workflows using GitHub Actions, focusing on essential concepts, configuration, and common practices within automation pipelines for version control ecosystems.

1. Workflow Definition Location

   In a standard repository setup, where should the configuration file for defining an automated workflow, such as building and testing code, be placed?

   1. .github/workflows
   2. actions/scripts
   3. .ci/scripts
   4. workflows/github

   Explanation: The correct directory for workflow configuration files is .github/workflows, ensuring automation tools can locate and execute the workflow. The other options, such as actions/scripts and .ci/scripts, resemble typical directory names for scripts but are not recognized as standard workflow locations. The option workflows/github is a misplacement and will not trigger the automation. Placing files outside the official directory will prevent automatic workflow activation.

2. Understanding Workflow Triggers

   Which keyword is used within a workflow configuration to specify events like code pushes or pull requests that initiate the automation process?

   1. on
   2. run
   3. trigger
   4. start

   Explanation: The keyword 'on' is used to define repository events that trigger the workflow, such as push or pull_request. The term 'run' is used for specifying the command inside steps, not as a trigger. 'Trigger' and 'start' are incorrect and will not be interpreted as valid event keywords in workflow configuration files. Therefore, only 'on' properly links repository events to the automation.

3. Job and Step Relationship

   In a typical workflow, what is the relationship between jobs and steps within the configuration structure?

   1. A job contains multiple steps
   2. A step contains multiple jobs
   3. Jobs and steps are unrelated
   4. A workflow only includes steps

   Explanation: A job is a collection of steps that run sequentially within the job context, making 'A job contains multiple steps' correct. The hierarchy does not allow a step to contain jobs, so 'A step contains multiple jobs' is wrong. Jobs and steps have a defined nested relationship, contrary to the claim they are unrelated. While steps are present, a workflow is organized into jobs, each of which holds steps.

4. Reusable Actions Purpose

   Suppose you want to use a prebuilt automation component like 'actions/checkout' to handle repository code. What is the main benefit of using such reusable actions in your workflow?

   1. They let you easily share and standardize automation tasks
   2. They automatically secure sensitive data
   3. They provide unlimited compute resources
   4. They update configuration files without user input

   Explanation: Reusable actions are primarily designed for sharing, reusing, and standardizing common automation tasks across multiple workflows, making this option correct. While actions can assist with security, they do not automatically secure sensitive data or grant unlimited compute resources. They also do not modify configuration files without user intervention. Thus, the other options exaggerate or misrepresent what reusable actions actually do.

5. Artifacts in CI/CD Pipelines

   In the context of a continuous integration and deployment workflow, what is an 'artifact' typically used for?

   1. Storing build outputs for later use or download
   2. Triggering new workflow runs automatically
   3. Managing user permissions
   4. Directly modifying code in the repository

   Explanation: Artifacts serve as storage for build outputs, such as compiled binaries or test results, which can be downloaded or used in later jobs. They do not trigger workflow runs, so that option is incorrect. Artifacts are not related to user permissions and cannot directly modify repository code. The primary function is to manage outputs produced during automated processes for subsequent access.