APURV
  • Home
  • Journey
  • Projects
  • Blogs
  • Interview
  • Exams
Resume
APURV

Building scalable, secure, and production-ready cloud infrastructure. Automation first.

NAVIGATION

HomeExperienceProjectsCertificationsSkills

TECH STACK

AWSGCPK8sCI/CDLinuxDocker

CONNECT

LinkedInGitHubEmailResume
© 2026 Apurv Gujjar. All rights reserved.
Apurv Gujjar
Apurv GujjarDevOps & Cloud Engineer
|Interview Documentation
Portfolio
Handbooks
🎯Linux🐙Git & GitHub🤖GitHub Actions🌐Networking☁AWS🛠Terraform🐳Docker☸Kubernetes📊Monitoring🛡DevSecOps💰Cost Optimization🚨Incident Scenarios👤HR & Behavioral☁GCP🐍Python
Interview DocumentationGitHub ActionsCan you list and explain the key architectural components of GitHub Actions?
Back to all GitHub Actions questions
Q2

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

💬Answer
  • Workflows: Automated procedures defined in YAML files located in .github/workflows/.
  • Events: Specific activities that trigger a workflow (e.g., push, pull_request, schedule).
  • Jobs: A set of steps that execute on the same runner. Jobs run in parallel by default, but can be configured to run sequentially using needs.
  • Steps: Individual tasks running commands or actions. Steps run sequentially.
  • Actions: Standalone, reusable commands or custom application integrations (e.g., actions/checkout).
  • Runners: The underlying virtual machines or containers executing the steps.

Related GitHub Actions Questions

View All GitHub ActionsQuestions →
Q1

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

Q3

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

Q4

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

Q5

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

Apurv Gujjar - DevOps & Cloud Engineer
Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker
View Portfolio