Jenkins Jenkins Distributed Builds

Question 1

What is a Jenkins agent (formerly called a slave)?

Accepted Answer

A machine that runs build jobs delegated by the Jenkins controller

Answer

A user account with limited permissions

Answer

A secondary Jenkins installation

Answer

A Docker container on the controller

Question 2

What are the two primary methods for connecting a Jenkins agent to the controller?

Accepted Answer

JNLP (inbound/WebSocket) and SSH

Answer

HTTP and FTP

Answer

SMTP and IMAP

Answer

REST API and CLI

Question 3

What is a Jenkins 'label' used for in the context of distributed builds?

Accepted Answer

Tags agents with capabilities so pipeline stages can target the right agent type

Answer

Names the agent for display in the UI

Answer

Sets the agent priority in the build queue

Answer

Defines the agent's workspace path

Question 4

What happens to a Jenkins build when no agent matching the requested label is available?

Accepted Answer

The build stays in the queue until a matching agent becomes available

Answer

The build fails immediately

Answer

The build runs on the controller

Answer

The build is reassigned to any available agent

Question 5

What is the difference between an online and offline Jenkins agent?

Accepted Answer

Online agents are connected and available for builds; offline agents are disconnected and cannot accept builds

Answer

Online agents run 24/7; offline agents run only during business hours

Answer

Online agents use cloud; offline agents are on-premises

Answer

Online agents are faster than offline agents

Question 6

What is the purpose of setting a 'Remote Root Directory' when configuring a Jenkins agent?

Accepted Answer

Defines the file system path on the agent where Jenkins stores workspaces and temp files

Answer

Sets the root of the agent's SCM checkout

Answer

Defines the Jenkins controller's URL from the agent's perspective

Answer

Sets the user home directory on the agent