CJE Practice Exam Questions with Answers Certified Jenkins Engineer (CJE) Certification

All of these

Using a regular expression pattern

Explicitly set projects to view

Explicitly set recursively in sub-folders

START_TIME

JOB_NAME

NODE_NAME

BUILD_NUMBER

Use the pluginManager.downgrade method in the script console.

Select the version you want to use in the global configuration section for this plugin.

Select one of the previous versions in the Plugin Manager.

Manually download and install the previously installed version.

Use the "downgradeplugin" command In the Jenkins CI I

Use the button on the Plugin Manager that allows a downgrade to the previously installed version.

Maintain a single source repository.

Do everything manually with great care.

Build every commit.

Make the build self-testing.

Permissions to run jobs and Pipeline

Credentials

View definitions

Plugins

Pipeline shared libraries

Add SSH Credentials

Add specific plugins

Create an Admin user with username and password

Add common plugins

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

You should configufe Global Pipeline Libraries at the Pipeline level: The libraries are running as "untrusted" code, allowing developers to run code 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.

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.

It will not be triggered.

It will be triggered if the polling detects a change In any git branch.

It will be triggered if the polling detects a change In the git branch "master".

It will be triggered if the polling detects a change in the git branch "development".

Continuous delivery means code will be tested and promoted to production environment automatically

Continuous delivery is magic, and Jenkins will make everything work without having to worry about it much.

You're right. Give me the on-call schedule.

Continuous delivery is a software development discipline where software is built so that it can be released to production at any time, while continuous deployment means it is released into production continuously. CI/CD is meant to shorten the amount of time needed for QA while empowering developers to keep code as up-to-date as possible

A groovy script needs to be approved.

A build is waiting for Input.

The build is waiting for an executor to be available.

An agent is being spawned.

agent {docker ‘openjdk’}

deploy { docker 'openjdk' }

docker 'openjdk' { install: true }

docker { agent 'openjdk:latest' }

Ruby

Python

Java

.NET

Manage plugins

Define views

Configure credentials

Open Blue Ocean

Configure Global Security

All of the others

SSH

Docker

JNLP

None of these

A pioneer in education

An organizational culture where developers and operations are working in harmony

The practice of developing optimal work practices

Nothing happens. The data remains on the persisted form of the configuration until the next save of that Rem (job, etc.).

It is deleted on the next restart of Jenkins.

It Is deleted on the next configuration reload.

It Is deleted Immediately.

The data is backed up and then deleted from the live configuration.

Email

All of these

Slack

HipChat

A Pipeline job must contain at least three stages.

It is not possible to call a Freestyle Job from within a Pipeline Job.

The Pipeline syntax supports running steps in parallel on different agents.

When using a Multibranch Pipeline, Jenkins can automatically create Jobs for each branch in the source code repository.

Pipeline jobs survive master restarts only If the Pipeline definition script Is checked into an SCM.

/var/lib/jenkins/secrets/InitialAdminPassword

/var/lib/jenkins/adminPassword

/var/lib/jenkins/workspace/secrets/InitialAdminPassword

/home/jenkins/secrets/InitialAdminPassword

Ensuring licenses have been paid for and allocated appropriately

Tracking system resources

Tracking who did what on your Jenkins server

Reviewing Build Failure rate

Run all builds on agents and never on the master itself.

Use the maximum number of executors at all times and avoid using labels.

Avoid modifying Java parameters that control heap size and garbage collection.

Use plugins as much as possible.

Allocate specific masters for different build types and teams.

agent { label 'docker'}

None of these

agent { docker 'openjdk'}

agent docker