Bird
Raised Fist0
Jenkinsdevops~10 mins

Cloud agent provisioning (EC2, Azure) in Jenkins - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to specify the AWS region for the EC2 agent.

Jenkins
pipeline {
  agent {
    ec2 {
      label 'my-agent'
      region '[1]'
    }
  }
  stages {
    stage('Build') {
      steps {
        echo 'Building on EC2 agent'
      }
    }
  }
}
Drag options to blanks, or click blank then click option'
Aeu-central-1
Bazure-eastus
Cus-west-2
Dasia-south1
Attempts:
3 left
💡 Hint
Common Mistakes
Using an Azure region name instead of AWS region.
2fill in blank
medium

Complete the code to specify the Azure cloud for the agent.

Jenkins
pipeline {
  agent {
    azure {
      cloudName '[1]'
      label 'azure-agent'
    }
  }
  stages {
    stage('Test') {
      steps {
        echo 'Running tests on Azure agent'
      }
    }
  }
}
Drag options to blanks, or click blank then click option'
Aazure-cloud
Baws-cloud
Cgcp-cloud
Dlocal-cloud
Attempts:
3 left
💡 Hint
Common Mistakes
Using AWS or GCP cloud names in Azure agent configuration.
3fill in blank
hard

Fix the error in the EC2 agent label configuration.

Jenkins
pipeline {
  agent {
    ec2 {
      label '[1]'
      region 'us-east-1'
    }
  }
  stages {
    stage('Deploy') {
      steps {
        echo 'Deploying on EC2 agent'
      }
    }
  }
}
Drag options to blanks, or click blank then click option'
Aec2-agent
Bazure-agent
Cdocker-agent
Dlocal-agent
Attempts:
3 left
💡 Hint
Common Mistakes
Using Azure or Docker labels for EC2 agents.
4fill in blank
hard

Fill both blanks to configure the Azure agent with correct cloud name and label.

Jenkins
pipeline {
  agent {
    azure {
      cloudName '[1]'
      label '[2]'
    }
  }
  stages {
    stage('Integration') {
      steps {
        echo 'Running integration tests on Azure agent'
      }
    }
  }
}
Drag options to blanks, or click blank then click option'
Aazure-cloud
Bec2-agent
Cazure-agent
Dgcp-cloud
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing AWS and Azure names in the same config.
5fill in blank
hard

Fill all three blanks to create an EC2 agent with label, region, and AMI ID.

Jenkins
pipeline {
  agent {
    ec2 {
      label '[1]'
      region '[2]'
      ami '[3]'
    }
  }
  stages {
    stage('Package') {
      steps {
        echo 'Packaging on EC2 agent'
      }
    }
  }
}
Drag options to blanks, or click blank then click option'
Aec2-agent
Bus-east-1
Cami-0abcdef1234567890
Dazure-agent
Attempts:
3 left
💡 Hint
Common Mistakes
Using Azure labels or regions in EC2 config.

Practice

(1/5)
1. What is the main purpose of cloud agent provisioning in Jenkins?
easy
A. To dynamically create and use cloud machines as Jenkins agents
B. To manually configure Jenkins agents on local machines
C. To backup Jenkins configuration files to the cloud
D. To monitor Jenkins job execution times

Solution

  1. Step 1: Understand Jenkins agent provisioning

    Jenkins can create agents dynamically in the cloud to run jobs without manual setup.
  2. Step 2: Identify the purpose of cloud provisioning

    Cloud agent provisioning automates creating cloud machines (like EC2 or Azure VMs) as Jenkins agents.
  3. Final Answer:

    To dynamically create and use cloud machines as Jenkins agents -> Option A
  4. Quick Check:

    Cloud agent provisioning = dynamic cloud agents [OK]
Hint: Cloud provisioning means automatic cloud agent creation [OK]
Common Mistakes:
  • Confusing provisioning with manual setup
  • Thinking it is for backup or monitoring
  • Assuming it only works on local machines
2. Which of the following is the correct way to specify an EC2 AMI ID in Jenkins cloud agent configuration?
easy
A. ami-0abcdef1234567890
B. ec2-ami-123456
C. AMI:1234567890
D. image-ec2-abcdef

Solution

  1. Step 1: Recognize EC2 AMI ID format

    EC2 AMI IDs start with 'ami-' followed by alphanumeric characters, e.g., 'ami-0abcdef1234567890'.
  2. Step 2: Match the correct format

    ami-0abcdef1234567890 matches the standard EC2 AMI ID format exactly.
  3. Final Answer:

    ami-0abcdef1234567890 -> Option A
  4. Quick Check:

    EC2 AMI ID starts with 'ami-' [OK]
Hint: EC2 AMI IDs always start with 'ami-' [OK]
Common Mistakes:
  • Using incorrect prefixes like 'ec2-ami-'
  • Confusing AMI ID with image names
  • Adding extra labels or colons
3. Given this Jenkins EC2 cloud agent snippet:
instanceCapStr: '3',
idleTerminationMinutes: 10,
ami: 'ami-0abc123def456',
remoteFS: '/home/jenkins'

What happens when 4 jobs are triggered simultaneously?
medium
A. Jenkins throws an error due to instance cap mismatch
B. 4 agents will be created ignoring the instance cap
C. All 4 jobs run on a single agent
D. Only 3 agents will be created; the 4th job waits in queue

Solution

  1. Step 1: Understand instanceCapStr meaning

    The 'instanceCapStr' limits the max number of EC2 agents Jenkins can create to 3.
  2. Step 2: Analyze job triggering behavior

    When 4 jobs start, Jenkins creates only 3 agents due to the cap; the 4th job waits in the queue.
  3. Final Answer:

    Only 3 agents will be created; the 4th job waits in queue -> Option D
  4. Quick Check:

    Instance cap limits agents = jobs queue if exceeded [OK]
Hint: Instance cap limits agents; extra jobs queue [OK]
Common Mistakes:
  • Assuming Jenkins ignores instance cap
  • Thinking all jobs run on one agent
  • Expecting an error when cap exceeded
4. You configured an Azure cloud agent in Jenkins but agents never start. Which is the most likely cause?
medium
A. Instance cap set to zero
B. Jenkins master is offline
C. Incorrect Azure VM image name or ID
D. Idle timeout set too high

Solution

  1. Step 1: Check Azure VM image configuration

    If the VM image name or ID is wrong, Jenkins cannot provision agents on Azure.
  2. Step 2: Evaluate other options

    Jenkins master offline stops all jobs, but question focuses on agent provisioning. Instance cap zero means no agents, but usually agents would not start at all. Idle timeout affects termination, not start.
  3. Final Answer:

    Incorrect Azure VM image name or ID -> Option C
  4. Quick Check:

    Wrong VM image blocks agent start [OK]
Hint: Check VM image name first if agents don't start [OK]
Common Mistakes:
  • Ignoring VM image correctness
  • Blaming idle timeout for start issues
  • Assuming Jenkins master offline without checking
5. You want to optimize Jenkins cloud agents on EC2 to reduce cost. Which combination of settings is best?
hard
A. Set instance cap high and idle termination to 60 minutes
B. Set instance cap low and idle termination to 5 minutes
C. Disable instance cap and idle termination
D. Set instance cap low and disable idle termination

Solution

  1. Step 1: Understand instance cap effect

    A low instance cap limits max running agents, controlling cloud costs.
  2. Step 2: Understand idle termination effect

    Setting idle termination to 5 minutes stops unused agents quickly, saving cost.
  3. Step 3: Evaluate other options

    High cap or disabling termination increases cost. Disabling termination wastes resources.
  4. Final Answer:

    Set instance cap low and idle termination to 5 minutes -> Option B
  5. Quick Check:

    Low cap + quick termination = cost saving [OK]
Hint: Low cap + short idle timeout saves cloud cost [OK]
Common Mistakes:
  • Setting high caps wastes money
  • Disabling idle termination keeps idle agents running
  • Ignoring cost impact of settings
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard