CI/CD · GitHub Actions interview questions

1. A.a set of steps that execute on the same runner, running in parallel with other jobs by default
2. B.a keyless auth method where Actions exchanges a short-lived OIDC token for cloud credentials, eliminating long-lived secrets
3. C.an automated process defined in a YAML file under .github/workflows triggered by GitHub events
4. D.a workflow called by another workflow via workflow_call to avoid duplication

Answer + AI explanation with Pro

1. A.Workflow
2. B.OIDC federation
3. C.Matrix strategy
4. D.Step

Answer + AI explanation with Pro

1. A.Workflow — a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
2. B.Workflow — an automated process defined in a YAML file under .github/workflows triggered by GitHub events
3. C.Workflow — a set of steps that execute on the same runner, running in parallel with other jobs by default
4. D.Workflow — a reusable unit of code packaged to be referenced from a workflow step via the uses keyword

Answer + AI explanation with Pro

1. A.a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
2. B.a set of steps that execute on the same runner, running in parallel with other jobs by default
3. C.the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow
4. D.a workflow called by another workflow via workflow_call to avoid duplication

Answer + AI explanation with Pro

1. A.Job
2. B.Runner
3. C.OIDC federation
4. D.Event trigger

Answer + AI explanation with Pro

1. A.Job — a keyless auth method where Actions exchanges a short-lived OIDC token for cloud credentials, eliminating long-lived secrets
2. B.Job — a set of steps that execute on the same runner, running in parallel with other jobs by default
3. C.Job — the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow
4. D.Job — a server (GitHub-hosted or self-hosted) that executes the jobs in a workflow

Answer + AI explanation with Pro

1. A.a set of steps that execute on the same runner, running in parallel with other jobs by default
2. B.an automated process defined in a YAML file under .github/workflows triggered by GitHub events
3. C.an individual task within a job that runs a command or an action
4. D.a custom action that bundles multiple workflow steps into a single reusable action

Answer + AI explanation with Pro

1. A.Composite action
2. B.Workflow
3. C.Matrix strategy
4. D.Step

Answer + AI explanation with Pro

1. A.Step — a custom action that bundles multiple workflow steps into a single reusable action
2. B.Step — the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow
3. C.Step — a set of steps that execute on the same runner, running in parallel with other jobs by default
4. D.Step — an individual task within a job that runs a command or an action

Answer + AI explanation with Pro

1. A.an automated process defined in a YAML file under .github/workflows triggered by GitHub events
2. B.an individual task within a job that runs a command or an action
3. C.a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
4. D.a reusable unit of code packaged to be referenced from a workflow step via the uses keyword

Answer + AI explanation with Pro

1. A.Matrix strategy
2. B.Job
3. C.Action
4. D.Workflow

Answer + AI explanation with Pro

1. A.Action — a keyless auth method where Actions exchanges a short-lived OIDC token for cloud credentials, eliminating long-lived secrets
2. B.Action — a reusable unit of code packaged to be referenced from a workflow step via the uses keyword
3. C.Action — a build configuration that runs a job multiple times across combinations of variables like OS and language version
4. D.Action — an individual task within a job that runs a command or an action

Answer + AI explanation with Pro

1. A.a server (GitHub-hosted or self-hosted) that executes the jobs in a workflow
2. B.a workflow called by another workflow via workflow_call to avoid duplication
3. C.a custom action that bundles multiple workflow steps into a single reusable action
4. D.an automated process defined in a YAML file under .github/workflows triggered by GitHub events

Answer + AI explanation with Pro

1. A.Step
2. B.Event trigger
3. C.Action
4. D.Runner

Answer + AI explanation with Pro

1. A.Runner — a gate requiring approval or a wait timer before a job deploys to a named environment
2. B.Runner — a custom action that bundles multiple workflow steps into a single reusable action
3. C.Runner — a server (GitHub-hosted or self-hosted) that executes the jobs in a workflow
4. D.Runner — a keyless auth method where Actions exchanges a short-lived OIDC token for cloud credentials, eliminating long-lived secrets

Answer + AI explanation with Pro

1. A.an automated process defined in a YAML file under .github/workflows triggered by GitHub events
2. B.a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
3. C.the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow
4. D.a build configuration that runs a job multiple times across combinations of variables like OS and language version

Answer + AI explanation with Pro

1. A.Composite action
2. B.Event trigger
3. C.Workflow
4. D.Job

Answer + AI explanation with Pro

1. A.Event trigger — a workflow called by another workflow via workflow_call to avoid duplication
2. B.Event trigger — an individual task within a job that runs a command or an action
3. C.Event trigger — the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow
4. D.Event trigger — a set of steps that execute on the same runner, running in parallel with other jobs by default

Answer + AI explanation with Pro

1. A.a set of steps that execute on the same runner, running in parallel with other jobs by default
2. B.a build configuration that runs a job multiple times across combinations of variables like OS and language version
3. C.an individual task within a job that runs a command or an action
4. D.the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow

Answer + AI explanation with Pro

1. A.Composite action
2. B.Workflow
3. C.Matrix strategy
4. D.OIDC federation

Answer + AI explanation with Pro

1. A.Matrix strategy — a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
2. B.Matrix strategy — a build configuration that runs a job multiple times across combinations of variables like OS and language version
3. C.Matrix strategy — a custom action that bundles multiple workflow steps into a single reusable action
4. D.Matrix strategy — a server (GitHub-hosted or self-hosted) that executes the jobs in a workflow

Answer + AI explanation with Pro

1. A.a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
2. B.a set of steps that execute on the same runner, running in parallel with other jobs by default
3. C.a workflow called by another workflow via workflow_call to avoid duplication
4. D.a reusable unit of code packaged to be referenced from a workflow step via the uses keyword

Answer + AI explanation with Pro

1. A.Concurrency group
2. B.Composite action
3. C.Reusable workflow
4. D.OIDC federation

Answer + AI explanation with Pro

1. A.Reusable workflow — a build configuration that runs a job multiple times across combinations of variables like OS and language version
2. B.Reusable workflow — a workflow called by another workflow via workflow_call to avoid duplication
3. C.Reusable workflow — the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow
4. D.Reusable workflow — an individual task within a job that runs a command or an action

Answer + AI explanation with Pro

1. A.a custom action that bundles multiple workflow steps into a single reusable action
2. B.a set of steps that execute on the same runner, running in parallel with other jobs by default
3. C.a workflow called by another workflow via workflow_call to avoid duplication
4. D.a server (GitHub-hosted or self-hosted) that executes the jobs in a workflow

Answer + AI explanation with Pro

1. A.Event trigger
2. B.Composite action
3. C.Matrix strategy
4. D.OIDC federation

Answer + AI explanation with Pro

1. A.Composite action — a build configuration that runs a job multiple times across combinations of variables like OS and language version
2. B.Composite action — a custom action that bundles multiple workflow steps into a single reusable action
3. C.Composite action — a workflow setting that cancels or queues in-progress runs sharing the same key to prevent overlapping deploys
4. D.Composite action — a gate requiring approval or a wait timer before a job deploys to a named environment

Answer + AI explanation with Pro

1. A.a keyless auth method where Actions exchanges a short-lived OIDC token for cloud credentials, eliminating long-lived secrets
2. B.a workflow called by another workflow via workflow_call to avoid duplication
3. C.a build configuration that runs a job multiple times across combinations of variables like OS and language version
4. D.a gate requiring approval or a wait timer before a job deploys to a named environment

Answer + AI explanation with Pro

1. A.Environment protection rule
2. B.Step
3. C.Reusable workflow
4. D.Workflow

Answer + AI explanation with Pro

1. A.Environment protection rule — a set of steps that execute on the same runner, running in parallel with other jobs by default
2. B.Environment protection rule — an individual task within a job that runs a command or an action
3. C.Environment protection rule — a gate requiring approval or a wait timer before a job deploys to a named environment
4. D.Environment protection rule — the on: key that specifies which GitHub activity (push, pull_request, schedule) starts a workflow

Answer + AI explanation with Pro