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.