CCJE Sample Questions Answers

Any Pipeline DSL code that implements complex computational tasks must be located outside any stage block.

All stages in a Pipeline must execute on the same type of agent.

Steps are the logical segmentation of a Pipeline; they contain stages that define actual tasks.

Each pipeline must have a global agent specification.

Stages are the logical segmentation of a Pipeline; they contain steps that define actual tasks.

Upgrade every plugin in the system to the latest available version.

Upgrade to a new version of CloudBees Core if it is available.

Upgrade every plugin In the CAP Collectionto the version defined by CAP.

Replace every plugin in the system with the version defined by CAP.

Automatically install new CloudBees Core releases as soon as they are available.

Provide information on the current status and configuration options of the CloudBees Assurance Program.

Enforce and lock a specific configuration in the CloudBees Core instance defined by the administrator.

Notify the user when a new CloudBees Core release is available.

starts the build of a job

updates plugins

sends notification once the build is completed

detects code changes in the repository

Number of plugins instated on the Jenkins instance.

The number of users registered on the Jenkins instance.

The memory used to run the Jenkins instance.

Number of Jobs in the build queue.

HTTP requests received by the Jenkins instance.

unit build data using the job setting "Discard old builds".

Change the order of jobs in the pipeline.

Gear the Jenkins cache.

Increase the size of the JENKINS.HOME partition/logical volume.

Make sure you regularly delete unused views.

It makes it easy to fork and merge code.

It requires a central server and a standby server.

It requires one server in each location.

It requires fast network access for dairy work.

It operates without a central server.

Builds to controlled agents (slaves).

Total number of jobs.

Maximum number of failed jobs allowed.

Job types that are allowed.

Available plugins.

Manage Jenkins -> Global Tool Configuration

Build tools need to be configured manually on each agent.

Jenkins Nodes -> Install Tools

Manage Jenkins -> Configure System

Manage plugins

Open Blue Ocean

Define views

Configure credentials

Configure Global Security

Associate the agent with a folder using the Controlled Agents feature, to limit the builds the agent will run to those in that folder.

Enable the Managed Agents feature for the folder containing the jobs the agent is allowed to run.

Create a folder with the same name as the agent, and check "Limit execution of builds on agent [NAME] to jobs in this folder".

Remove the users' permission to change the label expression of the jobs.

Define team specific folders and restrict edit access to team members.

You cannot. Each team must use a separate master.

You do not need to do anything. Job editing is restricted to team members by default.

Define team-specific views and set the initial view to the team-specific view.

Use a credential "SSH Username with private key", restricted to the Scope "Agents", for the node's SSH authentication.

Use a credential "SSH Username with private key", restricted to the Scope "System", for the node's SSH authentication.

You cannot use an SSH key pair. Configure a password for the agent's SSH user, and create a credential of type "Username with password" for the node's SSH authentication.

The SSH key will be stored in the )ENKINS_HOME/.ssh folder. Configure the agent to use a key from the "standard" SSH folder.

You should configure Global Pipeline Libraries at the Github Organization level: The libraries are running as "untrusted" code, allowing developer to run code on the Groovy sandbox.

You should not configure any Global Pipeline Libraries at the folder level: The libraries are running as "trusted" code, allowing all developers to execute privileged methods.

You should configure Global Pipeline Libraries at the Pipeline level: The libraries are running as "untrusted" code, allowing developers to run cod on the Groovy sandbox.

You should not configure any Global Pipeline Libraries at all: The libraries are running as "trusted" code, allowing all developers to execute privileged methods.

Download the value from a URL during the build itself.

Define the environment variable in a shared library function that each Job calls.

Set the environment variable on each pipeline or Job.

Define the environment variable on the Operations Center so it is available to all pipelines and Jobs, whereever they run in the duster.

Put all the pipelines and Jobs on one master or in one folder and set the environment variable in that master or folder.

Modifying the authorization strategy configuration.

Administering Jenkins' global configuration.

Creating/copying jobs.

Triggering a new build.

Retrieving information from Jenkins for programmatic consumption

Provide environment variables that will be available during builds.

Display the worst status for a job inside the folder.

Provide an icon for the folder using a URL.

Count jobs with different statuses.

OpenSSL must be instated on the agent.

The agent's SSH Public Key must be in the master's authorized keys.

The pubic key of the credential that is used for the agent must be installed on the agent.

You must log into the agent with SSH and start the agent.

SSHD must be installed on the agent.

Each instance can have a different Jenkins version and a different JDK version as long as they all run on the same operating system version.

All instances must run the same JDK version.

All instances must be +/- one ma)or revision from each other.

All instances must run the same Jenkins version and the same JDK version.

All instances must run the same Jenkins version.

They can be stored on an NFS shared folder of your infrastructure.

They can be stored on the Jenkins master, inside the JENKINS.HOME/.globallibrary folder.

They can be stored by the Jenkins administrators, using a custom Job manager.

They can be stored on a git repository hosted by the Jenkins master.

They can be stored on an external SVN repository.

Maximum number of Jobs which can be run concurrently on attached agents.

Number of CPU cores configured for this master.

Number of Java threads that can run Jenkins Jobs.

Number of Jobs that can execute simultaneously on the Jenkins master.

Number of external build agents that can be used for Jobs run on this Jenkins master.

agent {dockerfile {filename * Dockerfile' }}

agent docker

agent none

agent { label " linux }

agent { docker ' centos: latest ' }

Building, testing, and deploying the selected files to production environment.

Creating an archive file of the selected artifacts.

Recording the MD5 checksum of the selected artifacts.

Enabling access passwords for the selected artifacts.