CJE Certified Jenkins Engineer (CJE) Questions and Answers

Declarative Pipelines cab be restarted after a Jenkins failure but not after a transient outage (such as a network failure or disk space exhaustion).

Declarative Pipelines can be resumed only after a transient outage (such as a network failure or disk space exhaustion).

All Declarative Pipelines are restartable by default, with the same inputs (commit to build, parameters, etc) as the original run. Any data that was built In the original run Is available only If the preserveStashes() option Is specified In the Jenkinsfile

Declarative Pipelines that use Docker containers can not be resumed because the docker APIs that Jenkins calls to create the container are not serialized

A Declarative Pipeline can be restarted only If the preserveStashes() option Is set In the pipeline.

Both the Git and GitHub Plugins

The GitHub Plugin

The Git Plugin

None of these

Acceptance testing

Smoke testing

Unit testing

Integration testing

Maintain a single source repository.

Do everything manually with great care.

Build every commit.

Make the build self-testing.

Click "New Item" in the left dashboard panel, then select "Folder"

None of these

Add a folder on the Jenkins master file system in /var/lib/jenkins

You can add one from another project's "Configuration" view

Ant

Excel

Docker

Gradle

Validate with the CI system, write the new functional code, and then verify that the test passes.

Write a new test, validate with the a system, and then write the new functional code.

Write a new falling unit test, write the new functional code to fix the test, verify that the test passes, and then refactor the code.

Write a new failing unit test, write the new functional code to fix the test, and then verify that the test passes.

Manage Jenkins -> Configure Global Security

Manage Jenkins -> Configure System

None of these

Manage Jenkins -> Configure Global Options

environment(MAJOR_VERSION = 1)

environment { steps { sh " export MAJOR_VERSION=1" }}

environment { MAJOR_VERSION = 1 }

environment [MAJOR_VERSION=1]

The job must be configured to send email.

Jenkins must be successfully configured to point to a mail server.

Jenkins must be directly connected to the Internet.

Jenkins must have a unique email address.

Sendmail must be Installed and running on the same machine as Jenkins.

False

True

Ensuring licenses have been paid for and allocated appropriately

Tracking system resources

Tracking who did what on your Jenkins server

Reviewing Build Failure rate

START_TIME

JOB_NAME

NODE_NAME

BUILD_NUMBER

Manage credentials for Jenkins

All of these

Add a build step option to Jenkins

Provide backup functionality to Jenkins

None of these

Using an expression that matches a node's name or label

Select the node from the "Project Configuration" view

Set the projects in the "Manage Node" view

Use an input step just before the deploy stage.

This is not possible using Pipeline, because a Pipeline must run from start to finish without human interaction.

Create a separate Pipeline to run the deploy stage.

Use a stage step just before the deploy stage.

Either creating a group or reassigning the user will work.

Create a group, add an existing user to the task, and grant permissions to that group

Set permissions in Jenkins to allow anonymous users to run the command

Change the workflow to require an existing user to run the task, and assign permissions to that user.

/opt/jenkins/

/var/lib/jenkins/secrets/

/tmp/Jenkins/

/usr/lib/jenkins/password/

None of these

It's only used for freestyle projects

It contains the definition for a pipeline

It contains the basic configuration for Jenkins

Building in 60 minutes or less.

A software development discipline where software is built so that it can be released to production at any time.

A software development practice where contributors are integrating their work very frequently.

A software development discipline where software is released continuously as part of an automated pipeline.

Boolean

File

String

md5

step('build') { sh 'ant -f build.xml -v' } }

stage('build') { sh 'ant -f build.xml -v' }

stage('build') { steps { sh 'ant -f build-tools/build.xml -v' } }

stage('build') { steps { sh 'ant -f build.xml -v' } }

All credential bindings support the "Secret Text" and "Standard username and password" credential types.

Credential IDs are case Insensitive.

The credential types supported are defined by the binding plugin (or the resource being accessed.

Most credentials called from a pipeline have Global scope, not System scope.