Practice Free CJE Certified Jenkins Engineer (CJE) Exam Questions Answers With Explanation

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

Email

All of these

Slack

HipChat

It allows you to customize what specific IP address will never be able to trigger a build.

It allows you to trigger a build under certain conditions, such as GitHub/BitBucket push events, deployment ratifications,

It can only be configured on Freestyle projects.

It allows you to customize the mail to be sent to developers after a failing build.

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.

Because executors cannot be allocated on the master.

Because executors offloaded onto build nodes are not performant.

Because it prevents the CPU being overloaded during parallel polls.

Because it prevents builds from overloading a master's CPU/memory.

Because builds cannot be run In parallel on a master.

/build?Parameter =Value

/buiWWithParameters?Parameter=Value

/buildWithParameters

/build?Parameters=Value

A Jenkins user's username and GitHub API token.

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

A Jenkins user's username and Kerberos token.

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

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

Check the plugin wiki.

Search for the plugin in the Jenkins artifact repository.

Email the maintained

Check the Jenkins Update Center.

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.

only repositories that contain a Jenkinsfile in all their branches

only repositories that contain a Jenkinsfile in at least one branch

all repositories that contain a Jenkinsfile in at least one branch or pull request

all repositories

GIT_COMMIT

GIT_ORIGIN_URL

GIT_URL

GIT_BRANCH

/var/lib/jenkins

/etc/jenkins

With your source code

None of these

Perl

Python

Ruby

Java

You could use the Parameterized Trigger Plugin to trigger from an upstream project.

Both "Triggered by another project" and the "Parameterized Trigger Plugin"

Use the run() function passing the downstream projects name from within an upstream project build step.

In the downstream build, you can select "Triggered by another project"

All of these

Using a regular expression pattern

Explicitly set projects to view

Explicitly set recursively in sub-folders

Both the Git and GitHub Plugins

The GitHub Plugin

The Git Plugin

None of these

User tracking in Jenkins

The size of an artifact in bytes

An md5sum for an artifact that's tracked between projects

The name of a file

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.

It tests the functionality of the project as a whole.

It tests against the product specifications

It tests a small piece of functionality, usually at the class method level.

It tests components coming together.

Install a pre-defined set of recommended plugins.

Install Jenkins without any extra plugins.

Choose the version of Jenkins core to install.

Manually select plugins to install from a set of predefined plugins.

Install all existing open-source plugins for Jenkins.

CaII the fingerprintArtifact() step immediately after the archiveArtifacts( ) step.

Enable the Declarative Pipeline 'enableFingerprints' 'option' .

Set the Fingerprint Artifacts global configuration option.

Set the "fingerprint: true" argument for the archiveArtifactsQ step.

No action is required; Declarative Pipelines automatically record a fingerprint for each artifact.

agent any

agent { label 'Slave 1'}

agent none

All of these

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.

Add text to the "System Message" field on the "System Configuration" page to populate a banner displayed across the top of the master's home page.

On the "System Configuration" page, choose the "Maintenance Alerts" option from the "Alerts" dropdown menu and populate the box with a message to be added to all build logs.

Populate the "Email Notifications" section of the "System Configuration" page with a message to be sent as email to all registered Jenkins users.

On the master's dashboard, dick "add description" or "edit description" to populate a banner displayed across the top of the master's home page.

jcli

There is no Jenkins CLI

java -jar /var/lib/jenkins/jenkins-cli.jar -s http://:8080/

jenkins

Build times decrease.

User interface becomes slower as resources on the master run out.

The builds share SCM checkouts

Masters are more highly available.

Continuous Integration

Continuous Deployment

Continuous Delivery

Infrastructure as Code

Manage credentials for Jenkins

All of these

Add a build step option to Jenkins

Provide backup functionality to Jenkins

emailext

notice

email

alert

http://:8080/job/My%20Freestyle%20Project/config.xml

http://:8080/job/Freestyles/job/My%20Freestyle%20Project/config.xml

http://:8080/job/Freestyles/job/My%20Freestyle%20Project/project.xml

http://:8080/job/My%20Freestyle%20Project/project.xml

There is no graphical Plugin Manager

Dashboard Left Panel -> Manage Jenkins -> Configure System -> Manage Plugins

None of these

Dashboard Left Panel -> Manage Jenkins -> Manage Plugins

Add SSH Credentials

Add specific plugins

Create an Admin user with username and password

Add common plugins

None of these

junit-report "path to xml file"

generate "junit-report"

junit "path to xml file"

START_TIME

JOB_NAME

NODE_NAME

BUILD_NUMBER

email

Slack

Jira

SMS messaging

All of the above

.NET

Ruby

Python

Java

Credentials

My Views

New Item

Manage Jenkins

Aborted

Success

Unstable

Failure

Not Built

config {..}

project {..}

pipeline {..}

test {..}

apache agent

agent { label 'apache' }

agent( 'apache' )

apache' { agent }

The default number of executors on a node is 4.

You can run many of them in parallel.

They can run on the master.

It runs projects dictated by Jenkins.

db-dump

restart

who-am-i

shutdown

The Workspace directory.

The Builds directory in the Job.

The JENKINS_HOME directory.

The user's home directory.

Folders

Relational databases

Folders and views

Views

@daily

H H * * *

30 12 * * *

All of these

Tune the "timer" section for the project.

Choose not to use a clean checkout.

There's no way to reduce the time

Use a clean checkout.

Add or change tests as necessary

Checkout from an SCM.

Update with latest code from the mainline.

Ask your manager for permission to commit code.

ephemeral and replaceable

tailored to specific builds

on-master

static

Both "Triggered by another project" and the "Parameterized Trigger Plugin"

You could use the Parameterized Trigger Plugin to trigger from an upstream project.

In the downstream build, you can select "Triggered by another project."

Use the run() function passing the downstream projects name from within an upstream project build step.

No default administrator account is created; you have to configure security manually.

A default administrator account is created with username "admin" and password "ad

A default administrator account is created with username "admin" and password from the file

JENKINS_HOME/secrets/initialAdminPassword

A default administrator account is created and you cannot re-enable security.