---
title: "Jenkins: CI/CD Automation & Pipeline Management"
description: "Test your knowledge of Jenkins fundamentals with a quiz covering pipeline as code, Jenkinsfile syntax, agents, stages, build automation, plugins, distributed builds, Blue Ocean, and CI/CD best practices with Jenkins."
author: "Mohammad Abu Mattar"
canonical: https://mkabumattar.com/quizzes/post/jenkins-automation-fundamentals-quiz
---

# Jenkins: CI/CD Automation & Pipeline Management

Welcome to the Jenkins Basics Quiz! This quiz covers fundamental Jenkins concepts, including pipeline as code, Jenkinsfile syntax, agents and stages, build automation, plugins, and CI/CD best practices with Jenkins. Each question is multiple-choice, and you'll find hints to help you along the way. Good luck!

## Questions

### 1. What is Jenkins?

- A domain-specific language for building web-based interfaces
- An open-source automation server used to implement CI/CD
- A cloud-native database used for storing containerized images
- A specialized hardware appliance for hosting high-traffic sites

**Hint:** An open-source automation server.

### 2. What is a "Jenkinsfile"?

- A configuration script containing the list of authorized users
- A text file that defines the logic of a Jenkins Pipeline as code
- A compressed backup archive of the Jenkins global configuration
- A binary executable used to install the Jenkins core software

**Hint:** Pipeline as Code.

### 3. Which programming language is used to write Jenkins Pipelines?

- Python
- Groovy
- C++
- PHP

**Hint:** It runs on the JVM.

### 4. What is the difference between "Declarative" and "Scripted" pipelines?

- Declarative is for Windows; Scripted is for Unix-based systems
- Declarative uses a strict structure; Scripted offers full Groovy
- Scripted pipelines offer significantly faster execution speeds
- Declarative pipelines do not require an external Jenkinsfile

**Hint:** One is stricter; the other is more flexible.

### 5. What is a Jenkins "Agent"?

- An administrative user with full access to the Jenkins UI
- A machine or container that executes the assigned build tasks
- A background service that scans the server for security threats
- A plugin that manages external SMTP and notification services

**Hint:** Offloading work from the main server.

### 6. What does the "Blue Ocean" plugin provide?

- A plugin for managing containerized cluster networking logic
- A modern, redesigned user experience for Jenkins Pipelines
- A tool for automating the cleanup of old build artifacts
- A security feature for encrypting stored password variables

**Hint:** A modern UI.

### 7. In a Declarative Pipeline, what is the "agent any" directive?

- It restricts the pipeline to only run on the master controller
- It allows the pipeline to run on any available Jenkins agent
- It disables all agent-level security and permission checks
- It permits any registered user to modify the pipeline code

**Hint:** Choosing where to run.

### 8. What is a "Freestyle Project" in Jenkins?

- A project type that permits developers to use any language
- A traditional method of configuring jobs using the web UI
- A project that is provided free of cost by Jenkins vendors
- A project that functions without the use of external plugins

**Hint:** The legacy way.

### 9. What is the purpose of "Credentials" in Jenkins?

- To display the professional certifications of the developers
- To securely store sensitive data like API keys and passwords
- To provide a list of hardware specifications for each node
- To verify the network bandwidth between the agent and master

**Hint:** Security.

### 10. What is a "Trigger" in Jenkins?

- A user interface button that manually aborts a running build
- An event that initiates a build, such as a commit or schedule
- A logic error that causes the Jenkins controller to restart
- A post-build step that removes temporary workspace files

**Hint:** What starts the job?

### 11. What does the "Post" section in a Declarative Pipeline do?

- It publishes the pipeline metadata to a central log server
- It defines actions to run after the pipeline stages complete
- It serves as the main entry point for the application code
- It configures the network address for the Jenkins controller

**Hint:** Run after the stages.

### 12. What is "Poll SCM"?

- A survey tool used to gather feedback from development teams
- A trigger where Jenkins checks the repository for new changes
- A utility for deleting obsolete branches from the SCM host
- A cryptographic method for securing the source code in transit

**Hint:** Checking for changes.

### 13. What is a "Shared Library" in Jenkins?

- A central repository where team members share technical docs
- A way to share common Groovy code across multiple pipelines
- A shared file system directory mounted on all Jenkins agents
- A list of all plugins currently installed on the controller

**Hint:** Reusing Groovy code.

### 14. What is the purpose of the "Master" (Controller) node?

- To perform high-resource tasks like container image builds
- To manage the UI, coordinate schedules, and store metadata
- To act as a production web server for the application code
- To function as a network firewall for the internal network

**Hint:** The brain.

### 15. What is the "JENKINS_HOME" directory?

- The default directory for the developer's local workspace
- The directory that stores all Jenkins data and configuration
- The network URL used to access the Jenkins web interface
- A configuration file that lists all registered Jenkins nodes

**Hint:** Where the data lives.

### 16. What is an "Executor"?

- A system administrator who manages the Jenkins lifecycle
- A computational slot for executing a job on a Jenkins node
- A specialized script that restarts the Jenkins service
- A development tool used for writing and debugging HCL code

**Hint:** A slot for a task.

### 17. What is a "Pipeline Stage"?

- A physical server dedicated to testing the application code
- A logical segment of a pipeline such as Build, Test, or Deploy
- A method for tagging specific versions of code in the SCM
- A graphical tool used for drawing infrastructure diagrams

**Hint:** A block of steps.

### 18. What does "Discard Old Builds" do?

- Permanently removes the source code from the remote SCM
- Removes the logs and artifacts of older build executions
- Updates the Jenkins controller to the latest stable version
- Moves the current source code to a temporary system trash

**Hint:** Saving disk space.

### 19. What is the "Build Pipeline View"?

- A real-time monitor for watching code being written
- A visualization of a sequence of upstream and downstream jobs
- A dashboard used for monitoring the health of server hardware
- A built-in editor for modifying application image assets

**Hint:** Visualizing downstream jobs.

### 20. How do you parameterize a Jenkins job?

- By entering environment variables directly into the console
- By defining variables that users set before the build starts
- By modifying the Jenkins Java source code on the server
- By deleting the config.xml file from the Jenkins home path

**Hint:** User input at runtime.

### 21. What is a "Multi-branch Pipeline"?

- A pipeline that manages physical infrastructure connections
- A project that creates a pipeline for every branch in the SCM
- A tool used for merging multiple code branches together
- A configuration for managing multiple cloud provider accounts

**Hint:** A job for every branch.

### 22. What is "Artifact Archiving"?

- The process of deleting build files to save storage space
- Storing build outputs like JAR or WAR files for later use
- Creating a historical log of every developer commit
- Moving the source code to a long-term cold storage facility

**Hint:** Saving the build output.

### 23. What is a "Post-build Action"?

- A task that re-executes the build if the first one fails
- A step performed after the build, such as sending notifications
- A system utility that shuts down the agent after a build
- A global setting for managing user authentication levels

**Hint:** What happens after the work is done?

### 24. What is the "Jenkins API" used for?

- To facilitate real-time chat between Jenkins administrators
- To interact with Jenkins through external scripts or tools
- To install the Java Runtime Environment on the agent nodes
- To modify the visual CSS themes of the Jenkins dashboard

**Hint:** Programmatic access.

### 25. What is a "Pipeline Script" (from SCM)?

- A self-healing script that automatically fixes build errors
- A setting that loads the pipeline definition from a Git file
- A script that deletes the local repository after every build
- A tool for generating graphical diagrams of the source code

**Hint:** Loading the Jenkinsfile from Git.

### 26. What is "Upstream" and "Downstream"?

- The network direction of traffic flowing to the server
- Relationships where one job triggers or is triggered by another
- A method for differentiating between Linux and Windows agents
- A categorization for senior versus junior development tasks

**Hint:** The flow of jobs.

### 27. What does "Replay" do in a Jenkins Pipeline?

- Displays a video recording of the previous build execution
- Allows temporary pipeline modification without a Git commit
- Permanently deletes the build history and restarts the count
- Broadcasts a notification email to all project stakeholders

**Hint:** Modifying the script for one run.

### 28. What is a "Build Environment"?

- The physical room where the server hardware is located
- Configuration that prepares the node, such as setting variables
- A network security layer that isolates the Jenkins server
- A summary page displaying the history of all previous builds

**Hint:** Setting up the node.

### 29. What is the "Matrix Project"?

- A project that integrates virtual reality into the build
- A job type that runs a build across multiple configurations
- A cryptographic tool used to encrypt sensitive build data
- A specialized dashboard for managing project team members

**Hint:** One job, many variations.

### 30. What is "Quiet Period"?

- A policy that prevents developers from making commits
- A scheduled delay between a trigger and the build start
- A period of time where no automated builds are permitted
- A configuration that silences all audible server alarms

**Hint:** Waiting before starting.
