← All CJE Flashcard Decks

Distributed Builds & Agent Management Flashcards

7 cards from real CJE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Distributed Builds & Agent Management flashcards as text
  1. What is the default TCP port used by Jenkins agents when connecting to the controller via the inbound agent (JNLP) protocol?

    Answer: 50000

    Jenkins agents using the JNLP/TCP inbound protocol connect to the Jenkins controller on port 50000 by default, separate from the web UI port 8080.

  2. What is the primary purpose of assigning a 'label' to a Jenkins agent?

    Answer: To group agents so that jobs can target nodes with specific capabilities or OS types

    Labels allow jobs to specify which agents they can run on using the 'node' or 'agent' directive, enabling routing to agents with specific capabilities such as 'linux', 'docker', or 'gpu'.

  3. Which Jenkins agent connection method should be used when a firewall prevents the controller from initiating a connection to the agent?

    Answer: Launch agent by connecting it to the controller (Inbound/JNLP)

    The inbound/JNLP method allows the agent to initiate the TCP connection to the controller, bypassing firewall rules that block inbound connections from the controller to the agent.

  4. What does the '# of executors' setting on a Jenkins node control?

    Answer: The number of concurrent builds that can run simultaneously on that node

    The number of executors defines how many concurrent build processes can run simultaneously on a specific node, directly controlling its parallel build capacity.

  5. What is the 'Remote root directory' setting when configuring a Jenkins agent?

    Answer: The directory on the agent machine where Jenkins stores workspaces, caches, and build data

    The remote root directory is the working directory on the agent machine where Jenkins creates per-job workspaces and stores temporary files needed during builds.

  6. What does the 'Availability' setting for a Jenkins agent control?

    Answer: When the agent should be online — always, on a schedule, or on demand

    The Availability setting determines the agent's online policy: options include keeping it online at all times, bringing it online according to a schedule, or only when build demand requires it.

  7. Which plugin enables Jenkins to dynamically provision and terminate Amazon EC2 instances as build agents?

    Answer: Amazon EC2 Plugin

    The Amazon EC2 Plugin allows Jenkins to automatically start EC2 instances as agents when build demand increases and terminate them when they are no longer needed.