Cloud agent provisioning (EC2, Azure) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins EC2 Plugin: Agent Launch Output

You configure Jenkins to launch EC2 agents using the EC2 plugin. After triggering a build, which output indicates the agent was successfully launched?

A INFO: Launching a new EC2 instance for agent 'build-agent-1' succeeded

B ERROR: EC2 instance launch failed due to invalid credentials

C WARN: Agent 'build-agent-1' disconnected unexpectedly

D INFO: Jenkins master started without EC2 agent configuration

💡 Hint

Look for messages indicating success in launching EC2 instances.

The message 'Launching a new EC2 instance for agent ... succeeded' confirms the agent was started correctly. Errors or warnings indicate failure or unrelated events.

❓ Configuration

intermediate

Azure VM Agent Configuration in Jenkins

Which Jenkins pipeline snippet correctly provisions an Azure VM agent using the Azure VM Agents plugin?

A

agent {
  azure {
    vmImage 'UbuntuLTS'
    vmAgentName 'azure-agent-01'
  }
}

B

agent {
  label 'azure-vm-agent'
}

C

agent {
  docker {
    image 'mcr.microsoft.com/azure-cli'
  }
}

D

agent {
  node {
    cloud 'Azure'
    vmName 'agent-01'
  }
}

💡 Hint

Azure VM Agents plugin uses the 'azure' agent block with vmImage and vmAgentName.

Option A uses the correct syntax for Azure VM Agents plugin in Jenkins pipeline. Other options use docker or generic labels which do not provision Azure VMs.

❓ Troubleshoot

advanced

EC2 Agent Fails to Connect: Cause Identification

A Jenkins EC2 agent instance launches but fails to connect back to the master. Which is the most likely cause?

A Agent label does not match any job

B Jenkins master is offline

C EC2 instance type is too small

D Security group does not allow inbound traffic on the Jenkins agent port

💡 Hint

Think about network connectivity between the agent and master.

If the security group blocks inbound traffic on the required port (usually 50000), the agent cannot connect back. Other options do not directly cause connection failure.

🔀 Workflow

advanced

Azure VM Agent Provisioning Workflow

What is the correct order of steps Jenkins follows to provision an Azure VM agent?

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about provisioning before configuration and job assignment.

Jenkins first requests VM creation, waits for readiness, configures the agent, then assigns it to jobs.

✅ Best Practice

expert

Secure Credentials Management for EC2 Agent Provisioning

Which method is the most secure and recommended way to manage AWS credentials for Jenkins EC2 agent provisioning?

A Store AWS access keys directly in Jenkins global credentials with restricted permissions

B Embed AWS access keys in Jenkins pipeline scripts as environment variables

C Use IAM roles assigned to the Jenkins master EC2 instance with least privilege

D Hardcode AWS credentials in the EC2 plugin configuration file on Jenkins master

💡 Hint

Consider AWS best practices for credential management and least privilege.

Using IAM roles assigned to the Jenkins master EC2 instance avoids storing static credentials and follows AWS security best practices.