Agent types (permanent, cloud) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between permanent and cloud agents in Jenkins

Which statement correctly describes the main difference between permanent and cloud agents in Jenkins?

A Permanent agents are always online and managed manually, while cloud agents are created and destroyed automatically as needed.

B Permanent agents are created on-demand in the cloud, while cloud agents are physical machines always connected.

C Permanent agents run only on Windows, cloud agents run only on Linux.

D Permanent agents require no configuration, cloud agents require manual setup.

💡 Hint

Think about how Jenkins manages resources for builds in different environments.

Permanent agents are fixed machines or servers always connected to Jenkins. Cloud agents are temporary, created dynamically in cloud environments to handle workload and then removed.

💻 Command Output

intermediate

Jenkins agent status command output

What is the output of the Jenkins CLI command java -jar jenkins-cli.jar -s http://jenkins.example.com list-agents when there is one permanent agent named build-node-1 online and one cloud agent named docker-agent-xyz offline?

A No agents found

B

build-node-1 (offline)
docker-agent-xyz (online)

C

build-node-1 - cloud agent
docker-agent-xyz - permanent agent

D

build-node-1 (online)
docker-agent-xyz (offline)

💡 Hint

Check the status labels Jenkins uses for agents.

The command lists agents with their names and status. The permanent agent is online, cloud agent is offline, so output shows their names with correct statuses.

❓ Configuration

advanced

Jenkins cloud agent configuration snippet

Which Jenkins pipeline snippet correctly requests a cloud agent with label docker for a build step?

A

pipeline {
  agent { cloud { label 'docker' } }
  stages { stage('Build') { steps { echo 'Building...' } } }
}

B

pipeline {
  agent { label 'docker' }
  stages { stage('Build') { steps { echo 'Building...' } } }
}

C

pipeline {
  agent { docker { image 'jenkins/agent' } }
  stages { stage('Build') { steps { echo 'Building...' } } }
}

D

pipeline {
  agent any
  stages { stage('Build') { steps { echo 'Building...' } } }
}

💡 Hint

Look for the correct syntax to specify an agent by label.

The agent { label 'docker' } syntax requests an agent with the label 'docker', which can be a cloud agent if configured. Other options are invalid syntax or do not specify label correctly.

❓ Troubleshoot

advanced

Troubleshooting cloud agent connection failure

A Jenkins cloud agent fails to connect and shows the error Connection refused. Which is the most likely cause?

A The Jenkins user password is expired.

B The Jenkins master is offline.

C The cloud agent's firewall is blocking the Jenkins master port.

D The cloud agent has no disk space left.

💡 Hint

Think about network connectivity between Jenkins master and agent.

Connection refused usually means network or firewall blocks. If the agent's firewall blocks the port Jenkins master uses, connection fails. Other options cause different errors.

✅ Best Practice

expert

Best practice for scaling Jenkins agents in cloud environments

What is the best practice to efficiently scale Jenkins agents in a cloud environment?

A Use ephemeral cloud agents that start on demand and terminate after the job completes.

B Use only permanent agents to avoid cloud costs.

C Manually start and stop cloud agents as needed using the Jenkins UI.

D Keep a fixed number of permanent agents running 24/7 to handle all builds.

💡 Hint

Consider cost and resource efficiency in cloud environments.

Ephemeral cloud agents optimize resource use and cost by running only when needed. Fixed permanent agents waste resources. Manual management is inefficient.

Practice

1. What is a key characteristic of a permanent agent in Jenkins?

easy

A. It runs only on cloud platforms like AWS or Azure.

B. It is always connected and ready to run jobs.

C. It starts only when a job is triggered and stops afterward.

D. It automatically scales based on job demand.

Solution

1. Step 1: Understand permanent agent behavior

   Permanent agents are set up to be always online and ready to accept jobs without delay.

2. Step 2: Compare with cloud agents

   Cloud agents start and stop dynamically, unlike permanent agents which stay connected.

3. Final Answer:

   It is always connected and ready to run jobs. -> Option B

4. Quick Check:

   Permanent agent = always connected [OK]

Hint: Permanent agents stay online; cloud agents start/stop [OK]

Common Mistakes:

• Confusing permanent agents with cloud agents
• Thinking permanent agents scale automatically
• Assuming permanent agents only run on cloud

2. Which of the following is the correct way to define a cloud agent in Jenkins pipeline syntax?

easy

A. agent { permanent { name 'agent1' } }

B. agent { cloud { cloudName 'aws' } }

C. agent { docker { image 'cloud-agent' } }

D. agent { label 'cloud' }

Solution

1. Step 1: Identify cloud agent syntax

   Jenkins pipeline uses agent { label 'cloud' } to target cloud agents provisioned with matching labels.

2. Step 2: Eliminate other options

   agent { cloud { cloudName 'aws' } } is invalid syntax; C is for Docker agents, not cloud agents; D is incorrect syntax.

3. Final Answer:

   agent { label 'cloud' } -> Option D

4. Quick Check:

   Cloud agent syntax uses label { 'cloud' } [OK]

Hint: Cloud agents use agent { label 'cloud' } [OK]

Common Mistakes:

• Using invalid 'cloud { cloudName }' syntax for cloud agents
• Confusing Docker agent syntax with cloud agent
• Trying to define permanent agents inside agent block

3. Given this Jenkinsfile snippet:

pipeline {
  agent { label 'cloud' }
  stages {
    stage('Build') {
      steps {
        echo 'Running on cloud agent'
      }
    }
  }
}

What will happen when this pipeline runs?

medium

A. It fails because 'cloud' label is invalid for agents.

B. It runs on a permanent agent labeled 'cloud'.

C. It runs on a cloud agent that starts and stops automatically.

D. It runs on the master node regardless of label.

Solution

1. Step 1: Understand label usage

   The pipeline requests an agent with label 'cloud', which typically refers to a cloud agent.

2. Step 2: Behavior of cloud agents

   Cloud agents start when needed and stop after the job finishes, matching the label usage.

3. Final Answer:

   It runs on a cloud agent that starts and stops automatically. -> Option C

4. Quick Check:

   Label 'cloud' triggers cloud agent start/stop [OK]

Hint: Label 'cloud' usually means dynamic cloud agent [OK]

Common Mistakes:

• Assuming label 'cloud' means permanent agent
• Thinking label usage causes failure
• Assuming master node runs all jobs

4. You configured a cloud agent in Jenkins, but jobs never run on it and stay queued. What is the most likely cause?

medium

A. The cloud agent label is missing or mismatched in the job configuration.

B. The permanent agent is offline, so cloud agents cannot start.

C. The Jenkins master node is overloaded and blocking all agents.

D. The cloud agent plugin is not installed, causing syntax errors.

Solution

1. Step 1: Check label matching

   Jobs must specify the correct label matching the cloud agent to run on it.

2. Step 2: Understand job-agent assignment

   If labels don't match, Jenkins queues jobs waiting for suitable agents.

3. Final Answer:

   The cloud agent label is missing or mismatched in the job configuration. -> Option A

4. Quick Check:

   Label mismatch causes jobs to queue [OK]

Hint: Always match job label with agent label [OK]

Common Mistakes:

• Assuming permanent agent status affects cloud agents
• Blaming Jenkins master overload without evidence
• Confusing plugin absence with job queuing

5. You want to optimize Jenkins to save resources by using cloud agents for most jobs but keep a permanent agent for critical builds. How should you configure labels and agents?

hard

A. Assign label 'critical' to the permanent agent and 'cloud' to cloud agents; assign jobs accordingly.

B. Use only permanent agents with label 'all' and avoid cloud agents to reduce complexity.

C. Assign all jobs to label 'cloud' and disable the permanent agent to save resources.

D. Configure cloud agents without labels and assign all jobs to the permanent agent.

Solution

1. Step 1: Separate job types by labels

   Use distinct labels like 'critical' for permanent agent and 'cloud' for cloud agents to control job assignment.

2. Step 2: Assign jobs to matching labels

   Critical builds use the permanent agent with 'critical' label; other jobs use cloud agents with 'cloud' label.

3. Final Answer:

   Assign label 'critical' to the permanent agent and 'cloud' to cloud agents; assign jobs accordingly. -> Option A

4. Quick Check:

   Use labels to separate permanent and cloud jobs [OK]

Hint: Label agents and jobs to control resource use [OK]

Common Mistakes:

• Using only one label for all agents
• Disabling permanent agent when critical builds exist
• Not assigning labels to cloud agents