CJE Distributed Builds & Agent Management 3

Question 1

What is the Kubernetes Plugin for Jenkins primarily designed to do?

Accepted Answer

Dynamically provision and deprovision pod-based build agents in a Kubernetes cluster per build

Answer

Deploy the Jenkins controller itself as a Kubernetes Deployment resource

Answer

Scan Kubernetes manifests for security vulnerabilities during pipeline runs

Answer

Manage Kubernetes namespace deployments triggered from Jenkins jobs

Question 2

When using the Kubernetes Plugin in Jenkins, what does a 'Pod Template' define?

Accepted Answer

The containers, volumes, resource requests/limits, and settings used when creating an agent pod

Answer

A Kubernetes Deployment manifest used to install Jenkins itself

Answer

A template for generating Kubernetes Secrets for pipeline credential injection

Answer

A YAML configuration file for defining Jenkins job parameters

Question 3

What is the effect of setting 'Retention Strategy: Always' for a Jenkins agent?

Accepted Answer

Jenkins keeps the agent connected and online at all times, reconnecting automatically if it disconnects

Answer

The agent runs builds in a continuous loop without idle time between jobs

Answer

Build artifacts on the agent are retained permanently and never cleaned up

Answer

The agent is always selected first when multiple agents match a job's label requirements

Question 4

What is the purpose of the 'stash' and 'unstash' steps in Jenkins Pipelines?

Accepted Answer

To save a set of files from one stage's workspace and restore them in a later stage, even on a different agent

Answer

To securely store and retrieve pipeline credentials between build runs

Answer

To permanently archive build artifacts to the Jenkins artifact store

Answer

To cache Docker image layers between pipeline runs on the same agent

Question 5

Which characteristic best describes 'cloud agents' in Jenkins agent management?

Accepted Answer

Agents dynamically provisioned on cloud infrastructure on demand and terminated after builds complete

Answer

Permanently configured agents hosted on cloud virtual machines and manually started

Answer

Agents that exclusively execute cloud service deployment tasks such as AWS CLI commands

Answer

Agents granted special permissions to access cloud storage buckets during builds

Question 6

In the Jenkins inbound agent architecture, which side initiates the TCP connection?

Accepted Answer

The agent initiates the TCP connection to the Jenkins controller

Answer

The Jenkins controller initiates the connection to the agent's listening port

Answer

A third-party load balancer brokers connections between controller and agents

Answer

Both sides simultaneously open connections that are then merged into a tunnel

Question 7

What happens to a Jenkins build if the agent it is running on becomes disconnected mid-build?

Accepted Answer

The build fails and is marked as aborted or failed; Jenkins cannot resume a build on a different agent

Answer

Jenkins automatically migrates the running build to the next available agent with a matching label

Answer

Jenkins pauses the build and automatically resumes it once the agent reconnects

Answer

Jenkins saves the build state to the controller and reassigns it to another agent