CI/CD · Jenkins interview questions

1. A.a logically grouped block of steps in a pipeline that appears as a phase in the UI
2. B.a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.a topology where a controller schedules work onto distributed agents for scalable builds
4. D.injecting stored secrets into a build as environment variables or files at runtime

Answer + AI explanation with Pro

1. A.Blue Ocean
2. B.Credentials binding
3. C.Ephemeral agent
4. D.Pipeline

Answer + AI explanation with Pro

1. A.Pipeline — the machine or executor where Jenkins runs the build steps
2. B.Pipeline — a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.Pipeline — a build executor (often a Kubernetes pod) created on demand and destroyed after the build
4. D.Pipeline — a Jenkins UI plugin providing a visual pipeline editor and run visualization

Answer + AI explanation with Pro

1. A.a topology where a controller schedules work onto distributed agents for scalable builds
2. B.a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.a Groovy-based Jenkinsfile syntax offering full programmatic control
4. D.a structured, opinionated Jenkinsfile syntax using a pipeline block with stages

Answer + AI explanation with Pro

1. A.Declarative pipeline
2. B.Stage
3. C.Scripted pipeline
4. D.Node/agent

Answer + AI explanation with Pro

1. A.Declarative pipeline — a structured, opinionated Jenkinsfile syntax using a pipeline block with stages
2. B.Declarative pipeline — a Jenkins UI plugin providing a visual pipeline editor and run visualization
3. C.Declarative pipeline — a suite of plugins that models a delivery process as code in a Jenkinsfile
4. D.Declarative pipeline — injecting stored secrets into a build as environment variables or files at runtime

Answer + AI explanation with Pro

1. A.a classic GUI-configured Jenkins job not defined as pipeline code
2. B.a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.injecting stored secrets into a build as environment variables or files at runtime
4. D.a Groovy-based Jenkinsfile syntax offering full programmatic control

Answer + AI explanation with Pro

1. A.Multibranch pipeline
2. B.Node/agent
3. C.Scripted pipeline
4. D.Stage

Answer + AI explanation with Pro

1. A.Scripted pipeline — a topology where a controller schedules work onto distributed agents for scalable builds
2. B.Scripted pipeline — a project that automatically creates a pipeline for each branch containing a Jenkinsfile
3. C.Scripted pipeline — a Groovy-based Jenkinsfile syntax offering full programmatic control
4. D.Scripted pipeline — a build executor (often a Kubernetes pod) created on demand and destroyed after the build

Answer + AI explanation with Pro

1. A.a logically grouped block of steps in a pipeline that appears as a phase in the UI
2. B.a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.the machine or executor where Jenkins runs the build steps
4. D.a project that automatically creates a pipeline for each branch containing a Jenkinsfile

Answer + AI explanation with Pro

1. A.Pipeline
2. B.Node/agent
3. C.Controller-agent architecture
4. D.Ephemeral agent

Answer + AI explanation with Pro

1. A.Node/agent — a project that automatically creates a pipeline for each branch containing a Jenkinsfile
2. B.Node/agent — a structured, opinionated Jenkinsfile syntax using a pipeline block with stages
3. C.Node/agent — a topology where a controller schedules work onto distributed agents for scalable builds
4. D.Node/agent — the machine or executor where Jenkins runs the build steps

Answer + AI explanation with Pro

1. A.a logically grouped block of steps in a pipeline that appears as a phase in the UI
2. B.a Groovy-based Jenkinsfile syntax offering full programmatic control
3. C.injecting stored secrets into a build as environment variables or files at runtime
4. D.a suite of plugins that models a delivery process as code in a Jenkinsfile

Answer + AI explanation with Pro

1. A.Stage
2. B.Declarative pipeline
3. C.Shared library
4. D.Node/agent

Answer + AI explanation with Pro

1. A.Stage — a logically grouped block of steps in a pipeline that appears as a phase in the UI
2. B.Stage — a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.Stage — injecting stored secrets into a build as environment variables or files at runtime
4. D.Stage — a classic GUI-configured Jenkins job not defined as pipeline code

Answer + AI explanation with Pro

1. A.injecting stored secrets into a build as environment variables or files at runtime
2. B.a classic GUI-configured Jenkins job not defined as pipeline code
3. C.the machine or executor where Jenkins runs the build steps
4. D.a project that automatically creates a pipeline for each branch containing a Jenkinsfile

Answer + AI explanation with Pro

1. A.Controller-agent architecture
2. B.Node/agent
3. C.Freestyle job
4. D.Scripted pipeline

Answer + AI explanation with Pro

1. A.Freestyle job — a suite of plugins that models a delivery process as code in a Jenkinsfile
2. B.Freestyle job — a Jenkins UI plugin providing a visual pipeline editor and run visualization
3. C.Freestyle job — reusable Groovy pipeline code stored in a separate repository and loaded across jobs
4. D.Freestyle job — a classic GUI-configured Jenkins job not defined as pipeline code

Answer + AI explanation with Pro

1. A.reusable Groovy pipeline code stored in a separate repository and loaded across jobs
2. B.a classic GUI-configured Jenkins job not defined as pipeline code
3. C.a topology where a controller schedules work onto distributed agents for scalable builds
4. D.a build executor (often a Kubernetes pod) created on demand and destroyed after the build

Answer + AI explanation with Pro

1. A.Shared library
2. B.Blue Ocean
3. C.Scripted pipeline
4. D.Freestyle job

Answer + AI explanation with Pro

1. A.Shared library — injecting stored secrets into a build as environment variables or files at runtime
2. B.Shared library — the machine or executor where Jenkins runs the build steps
3. C.Shared library — a topology where a controller schedules work onto distributed agents for scalable builds
4. D.Shared library — reusable Groovy pipeline code stored in a separate repository and loaded across jobs

Answer + AI explanation with Pro

1. A.a build executor (often a Kubernetes pod) created on demand and destroyed after the build
2. B.a topology where a controller schedules work onto distributed agents for scalable builds
3. C.a classic GUI-configured Jenkins job not defined as pipeline code
4. D.a project that automatically creates a pipeline for each branch containing a Jenkinsfile

Answer + AI explanation with Pro

1. A.Blue Ocean
2. B.Controller-agent architecture
3. C.Credentials binding
4. D.Multibranch pipeline

Answer + AI explanation with Pro

1. A.Multibranch pipeline — a project that automatically creates a pipeline for each branch containing a Jenkinsfile
2. B.Multibranch pipeline — the machine or executor where Jenkins runs the build steps
3. C.Multibranch pipeline — a topology where a controller schedules work onto distributed agents for scalable builds
4. D.Multibranch pipeline — a Jenkins UI plugin providing a visual pipeline editor and run visualization

Answer + AI explanation with Pro

1. A.a Jenkins UI plugin providing a visual pipeline editor and run visualization
2. B.injecting stored secrets into a build as environment variables or files at runtime
3. C.reusable Groovy pipeline code stored in a separate repository and loaded across jobs
4. D.a Groovy-based Jenkinsfile syntax offering full programmatic control

Answer + AI explanation with Pro

1. A.Freestyle job
2. B.Pipeline
3. C.Multibranch pipeline
4. D.Credentials binding

Answer + AI explanation with Pro

1. A.Credentials binding — injecting stored secrets into a build as environment variables or files at runtime
2. B.Credentials binding — reusable Groovy pipeline code stored in a separate repository and loaded across jobs
3. C.Credentials binding — a suite of plugins that models a delivery process as code in a Jenkinsfile
4. D.Credentials binding — the machine or executor where Jenkins runs the build steps

Answer + AI explanation with Pro

1. A.reusable Groovy pipeline code stored in a separate repository and loaded across jobs
2. B.a Jenkins UI plugin providing a visual pipeline editor and run visualization
3. C.a suite of plugins that models a delivery process as code in a Jenkinsfile
4. D.the machine or executor where Jenkins runs the build steps

Answer + AI explanation with Pro

1. A.Blue Ocean
2. B.Scripted pipeline
3. C.Shared library
4. D.Stage

Answer + AI explanation with Pro

1. A.Blue Ocean — a project that automatically creates a pipeline for each branch containing a Jenkinsfile
2. B.Blue Ocean — a suite of plugins that models a delivery process as code in a Jenkinsfile
3. C.Blue Ocean — a Jenkins UI plugin providing a visual pipeline editor and run visualization
4. D.Blue Ocean — a classic GUI-configured Jenkins job not defined as pipeline code

Answer + AI explanation with Pro