GitHub Actions

Automated CI/CD Workflow & Runner Guide with GitHub Actions

What is GitHub Actions, and how does it process workflows under the hood?

💬Answer

GitHub Actions is an API-driven workflow automation and CI/CD platform integrated directly into GitHub. It allows you to automate tasks—such as building, testing, packaging, and deploying code—directly in response to repository events (e.g., code pushes, pull requests, release creation, or cron schedules).

Can you list and explain the key architectural components of GitHub Actions?

How do you configure workflow triggers, and what is the syntax for defining manual execution parameters?

What is a matrix strategy in GitHub Actions, and in what scenarios would you use it?

How do GitHub-hosted runners compare to self-hosted runners? When is self-hosting required?

How do environments and environment protection rules help secure deployments to production?

Why should we use OpenID Connect (OIDC) integration for cloud auth instead of storing static AWS credentials?

How do we implement caching in GitHub Actions to speed up dependency installation times?

Since jobs run in isolated virtual environments, how do we pass build artifacts from a build job to a deploy job?

Q10

How do concurrency groups work, and how do you configure a workflow to automatically cancel in-progress runs when a new commit is pushed?

Q11

How do you manage and inject encrypted secrets into our workflow runs securely?

Q12

What is the difference between 'run' and 'uses' in a workflow step definition?

Q13

What are composite actions, and why would we use them instead of repeating YAML code?

Q14

If a workflow fails, what is your systematic troubleshooting process?

Q15

What are Reusable Workflows, and how do they differ from composite actions?

Q16

Can you summarize when to choose a Reusable Workflow over a Composite Action?

Q17

What security measures must be put in place when operating self-hosted runners?

Q18

How do you construct a pipeline that deploys to staging first, and then to production only if staging succeeds?

Q19

How do you implement a manual approval gate for production deployments?

Q20

What steps do you take to prevent credentials and secrets from leaking into the build runner logs?

Q21

How do you sign build artifacts or container images within a GitHub Actions run to verify their authenticity?

Q22

Explain the difference between Continuous Integration (CI) and Continuous Deployment (CD).

Q23

What are some popular CI/CD tools, and how do on-premises models compare to SaaS models?

Q24

# 1. On-Premises / Self-Hosted Tools

Q25

# 2. Cloud-Based / SaaS Tools

Q26

What is a build pipeline, and what are its typical execution stages?

Q27

# Typical Stages of a Build Pipeline:

Q28

How do you optimize a CI/CD pipeline for both speed and reliability?

Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker

View Portfolio