Common GitHub Actions Interview Questions Quiz Quiz

Challenge your understanding of workflow automation and configuration with this quiz on common interview questions about GitHub Actions. Enhance your knowledge of best practices, syntax, and key features used in continuous integration and deployment workflows.

1. Understanding Workflow Triggers

   Which event will trigger a workflow run when a pull request is opened against the 'main' branch of a repository?

   1. push_request
   2. pr_opened
   3. pull_request
   4. request_pull

   Explanation: The 'pull_request' event is used to trigger workflows when pull requests are opened, synchronized, or closed. 'push_request' and 'request_pull' may sound plausible but are not valid event names in workflow configuration. 'pr_opened' is a common typo or misremembered event name. Using the correct event ensures your workflows respond to the intended triggers.

2. Workflow Syntax Fundamentals

   What is the correct top-level key to declare the entry point for a workflow job in a YAML workflow file?

   1. tasks
   2. actions
   3. steps
   4. jobs

   Explanation: 'jobs' is the required top-level key that defines the sequence of jobs a workflow will run. 'steps' is defined under 'jobs' to specify individual tasks. 'actions' and 'tasks' are not valid top-level keys; 'actions' refers to reusable commands, and 'tasks' is not recognized in workflow syntax. Knowing the structure prevents configuration errors.

3. Managing Secrets in Workflows

   How should you reference a stored secret, such as an API token, securely within a workflow step?

   1. ${{ variables.API_TOKEN }}
   2. ${ secrets.API_TOKEN }
   3. ${{ api_token }}
   4. ${{ secrets.API_TOKEN }}

   Explanation: The correct and secure way to reference a secret in a workflow step is '${{ secrets.API_TOKEN }}'. '${ secrets.API_TOKEN }' has incorrect syntax due to missing curly braces. '${{ api_token }}' and '${{ variables.API_TOKEN }}' do not point to the secure secrets store and will not retrieve sensitive information safely. Using the right syntax maintains security and access control in workflows.

4. Artifacts and Data Sharing

   Which method can you use to pass build output files from one job to another in a multi-job workflow?

   1. Copy and paste output commands
   2. Directly access the next job's workspace
   3. Use the steps context
   4. Upload and download artifacts

   Explanation: To share build outputs between jobs, you must upload artifacts in one job and download them in another. Copy and paste methods are manual and not applicable in automated workflows. Directly accessing another job's workspace is not possible due to sandboxed environments. While the steps context provides access within a job, it does not facilitate sharing between jobs.

5. Reusable Workflows

   What is the correct way to call a reusable workflow from another workflow file?

   1. Specifying the workflow file within a 'subworkflows' section
   2. Using the 'include' keyword with the workflow YAML
   3. Listing the workflow under 'imports' at the top of the file
   4. Using the 'uses' keyword with the workflow's file path

   Explanation: To invoke a reusable workflow, use the 'uses' keyword followed by the path to the workflow file. The 'include' keyword does not exist in workflow syntax. There is no 'imports' section available for workflows, and 'subworkflows' is not a recognized configuration. Using the correct approach ensures modular and maintainable automation.