CCJE Practice Exam Questions with Answers Certified CloudBees Jenkins Engineer (CCJE) Certification

Build parameters

Matrix based security

Job Configuration Restriction plugin

Declarative Pipeline

System environment variables

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.

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.

A Jenkins user's username and password or API token.

A Jenkins user's username and GitHub API token.

A Jenkins user's username and Kerberos token.

An SSH key matching an entry in the authorized_keys file of the user account that the Jenkins master process runs "as".

An SSH key matching a Jenkins user's public key.

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.

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.

Encapsulate common Jenkins logic within shared Iibraries when leveraging Declarative Pipelines.

Use the pipeline DSL to implement Intricate networking and computational tasks that your Pipeline needs to do.

Simplify the test/debug process and improve performance of your pipeline by defining separate steps for each Important task performed by the pipeline.

Use toots such as Maven, Gradle, NPM, Ant, and Make to define most of the build work; call these executables as steps in your pipeline.

Call scripts written in Shell, Batch, Groovy, or Python to implement any complex logic required for your pipeline; call these scripts as steps in your pipeline.