Agent connection methods (SSH, JNLP) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Jenkins Agent Connection Methods

Which statement correctly describes the difference between SSH and JNLP agent connection methods in Jenkins?

A JNLP agents require Jenkins to have SSH access to the agent machine, but SSH agents do not require any network connection.

B SSH agents use a Java Web Start protocol, while JNLP agents use direct SSH commands to connect.

C SSH agents connect by Jenkins initiating an SSH session to the agent machine, while JNLP agents connect by the agent machine initiating a connection to Jenkins.

D Both SSH and JNLP agents require the agent machine to open port 22 for Jenkins to connect.

💡 Hint

Think about who starts the connection in each method.

SSH agents connect by Jenkins initiating an SSH session to the agent machine, requiring Jenkins to access the agent's SSH port. JNLP agents run a Java process on the agent machine that connects back to Jenkins, so the agent initiates the connection.

💻 Command Output

intermediate

Output of Starting a JNLP Agent Manually

What is the expected output when running the following command on the agent machine to start a JNLP agent?

Jenkins

java -jar agent.jar -jnlpUrl http://jenkins.example.com/computer/agent1/slave-agent.jnlp -secret 1234567890abcdef

A

INFO: Connecting to Jenkins at http://jenkins.example.com
INFO: Connected
INFO: Agent started successfully

B

ERROR: Could not find agent.jar file
Exception in thread "main" java.lang.NoClassDefFoundError

C

INFO: SSH connection established
INFO: Agent ready

D

ERROR: Invalid secret key
Connection refused

💡 Hint

JNLP agents connect using Java and a secret key.

The command runs the Java agent jar with the JNLP URL and secret key. It connects to Jenkins and starts the agent process, showing connection info messages.

❓ Configuration

advanced

Configuring SSH Agent in Jenkins

Which SSH configuration snippet correctly sets up a Jenkins agent to connect via SSH with a private key located at /home/jenkins/.ssh/id_rsa?

A

Host agent1
  HostName agent1.example.com
  User jenkins
  IdentityFile /home/jenkins/.ssh/id_rsa
  StrictHostKeyChecking no

B

Host agent1
  HostName agent1.example.com
  User jenkins
  PasswordAuthentication yes
  IdentityFile /home/jenkins/.ssh/id_rsa

C

Host agent1
  HostName agent1.example.com
  User root
  IdentityFile /root/.ssh/id_rsa
  StrictHostKeyChecking no

D

Host agent1
  HostName agent1.example.com
  User jenkins
  IdentityFile /home/jenkins/.ssh/id_rsa
  Port 8080

💡 Hint

Check the user, key file path, and SSH options for security.

Option A correctly uses the Jenkins user, the correct private key path, and disables strict host key checking for easier connection. Option A incorrectly enables password authentication which is not needed. Option A uses root user and wrong key path. Option A sets a wrong port for SSH.

❓ Troubleshoot

advanced

Troubleshooting SSH Agent Connection Failure

A Jenkins SSH agent fails to connect with the error: Permission denied (publickey). Which is the most likely cause?

A The Jenkins master is not running the Java agent jar.

B The agent machine's firewall is blocking port 8080.

C The JNLP secret key is incorrect.

D The private key on Jenkins master does not match the public key on the agent machine.

💡 Hint

Think about SSH authentication errors.

Permission denied (publickey) means SSH authentication failed because the private key Jenkins uses does not match any authorized public key on the agent machine. Firewall blocking port 8080 or JNLP secret key issues relate to JNLP agents, not SSH. The Java agent jar is unrelated to SSH connection.

✅ Best Practice

expert

Choosing Agent Connection Method for Security and Scalability

For a Jenkins setup with many dynamic cloud agents behind firewalls, which agent connection method is best practice and why?

A Use JNLP agents because they require Jenkins to open SSH ports on all agents.

B Use JNLP agents because they initiate the connection to Jenkins, avoiding firewall inbound rules.

C Use SSH agents because Jenkins can directly connect to all agents via SSH without extra setup.

D Use SSH agents because they are easier to configure on cloud providers.

💡 Hint

Consider firewall and network restrictions for cloud agents.

JNLP agents connect by the agent initiating the connection to Jenkins, which works well behind firewalls and NATs common in cloud environments. SSH agents require Jenkins to connect inbound to agents, which is often blocked. Thus, JNLP is preferred for dynamic cloud agents.

Practice

1. Which statement correctly describes the difference between SSH and JNLP agent connection methods in Jenkins?

easy

A. SSH agents connect by Jenkins initiating the connection; JNLP agents connect by the agent initiating the connection.

B. JNLP agents connect by Jenkins initiating the connection; SSH agents connect by the agent initiating the connection.

C. Both SSH and JNLP agents require Jenkins to initiate the connection.

D. Both SSH and JNLP agents require the agent to initiate the connection.

Solution

1. Step 1: Understand SSH agent connection

   SSH agents connect by Jenkins server initiating an SSH connection to the agent machine.

2. Step 2: Understand JNLP agent connection

   JNLP agents connect by the agent itself initiating a connection back to the Jenkins server.

3. Final Answer:

   SSH agents connect by Jenkins initiating the connection; JNLP agents connect by the agent initiating the connection. -> Option A

4. Quick Check:

   SSH = Jenkins initiates, JNLP = Agent initiates [OK]

Hint: Remember: SSH = Jenkins connects out, JNLP = agent connects in [OK]

Common Mistakes:

• Confusing which side initiates the connection
• Thinking both methods work the same way
• Assuming JNLP requires SSH protocol

2. Which of the following is the correct syntax to configure a Jenkins SSH agent in the Jenkins UI?

easy

A. Provide Jenkins server IP and SSH port only.

B. Provide Jenkins server URL and agent secret key only.

C. Provide only the agent's IP address without credentials.

D. Provide agent's hostname, SSH credentials, and remote root directory.

Solution

1. Step 1: Identify SSH agent configuration requirements

   SSH agents require hostname, SSH credentials (username/key), and remote root directory to connect properly.

2. Step 2: Eliminate incorrect options

   Options A, B, and C miss essential details like credentials or directory, so they are incorrect.

3. Final Answer:

   Provide agent's hostname, SSH credentials, and remote root directory. -> Option D

4. Quick Check:

   SSH agent needs hostname + credentials + directory [OK]

Hint: SSH agent setup needs hostname, credentials, and directory [OK]

Common Mistakes:

• Skipping SSH credentials in configuration
• Confusing JNLP secret with SSH setup
• Providing incomplete connection details

3. Given a Jenkins agent configured with JNLP, what will happen if the agent machine cannot reach the Jenkins server URL?

medium

A. The agent will connect using SSH fallback automatically.

B. The agent will connect successfully because Jenkins initiates the connection.

C. The agent will fail to connect because it initiates the connection to Jenkins.

D. The Jenkins server will push jobs to the agent regardless.

Solution

1. Step 1: Understand JNLP connection direction

   JNLP agents initiate the connection to the Jenkins server URL, so the agent must reach the server.

2. Step 2: Analyze network failure impact

   If the agent cannot reach the Jenkins server URL, the connection attempt fails and the agent cannot connect.

3. Final Answer:

   The agent will fail to connect because it initiates the connection to Jenkins. -> Option C

4. Quick Check:

   JNLP agent needs network access to Jenkins [OK]

Hint: JNLP agent must reach Jenkins URL to connect [OK]

Common Mistakes:

• Assuming Jenkins initiates JNLP connection
• Thinking SSH fallback is automatic
• Believing Jenkins can push jobs without agent connection

4. You configured an SSH agent in Jenkins but the connection keeps failing with authentication errors. What is the most likely cause?

medium

A. Agent machine cannot reach Jenkins server URL.

B. Incorrect SSH credentials or missing SSH key on the agent machine.

C. JNLP agent secret key is invalid.

D. Jenkins server firewall blocks outgoing SSH connections.

Solution

1. Step 1: Identify cause of SSH authentication failure

   Authentication errors usually mean wrong username/password or missing SSH key on the agent side.

2. Step 2: Eliminate other options

   Agent machine cannot reach Jenkins server URL. relates to JNLP, not SSH. JNLP agent secret key is invalid. is about JNLP secret. Jenkins server firewall blocks outgoing SSH connections. is unlikely as Jenkins initiates SSH outbound.

3. Final Answer:

   Incorrect SSH credentials or missing SSH key on the agent machine. -> Option B

4. Quick Check:

   SSH auth errors = bad credentials or missing key [OK]

Hint: Check SSH credentials and keys first for connection errors [OK]

Common Mistakes:

• Confusing JNLP secret with SSH credentials
• Ignoring network reachability issues
• Assuming firewall blocks inbound SSH to Jenkins

5. You need to connect Jenkins agents located behind strict firewalls that block incoming connections to the agent machines. Which connection method should you choose and why?

hard

A. Use JNLP because agents initiate connections to Jenkins, bypassing firewall restrictions.

B. Use SSH because Jenkins can initiate connections to agents behind firewalls.

C. Use SSH with VPN to bypass firewall restrictions.

D. Use JNLP but disable agent authentication for easier connection.

Solution

1. Step 1: Analyze firewall impact on connection methods

   Firewalls blocking incoming connections to agents prevent Jenkins from initiating SSH connections.

2. Step 2: Choose method allowing agent-initiated connection

   JNLP agents initiate connection to Jenkins server, so they can connect despite firewall restrictions on incoming traffic.

3. Step 3: Evaluate other options

   SSH requires Jenkins to connect in, VPN adds complexity, disabling authentication is insecure and not recommended.

4. Final Answer:

   Use JNLP because agents initiate connections to Jenkins, bypassing firewall restrictions. -> Option A

5. Quick Check:

   Firewall blocks incoming? Choose agent-initiated JNLP [OK]

Hint: Firewalls blocking incoming? Pick JNLP agent connection [OK]

Common Mistakes:

• Choosing SSH despite firewall inbound block
• Disabling authentication for convenience
• Ignoring VPN complexity and security