CJE Certified Jenkins Engineer (CJE) Questions and Answers

tests an Individual unit a component

verifies cross-functionalities

verifies that the complete software matches the specifications it was written to fulfill

is written when an Integration or multi-environment bog is fixed

Build times decrease.

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

The builds share SCM checkouts

Masters are more highly available.

Overwrite the hpi file on the file system

Click the "Downgrade to" button in the Plugin Manager

All of these

Use the advanced install option in the Plugin Manager to install an older hpi file than the plugin already installed.

Ant

Excel

Docker

Gradle

From "Project Configuration," select "This project is parameterized."

Freestyle projects don't accept parameters

Choose the project from the parameterized list in the "Configure System" section.

All freestyle projects are parameterized

emailext

notice

email

alert

/var/lib/jenkins/secrets/InitialAdminPassword

/var/lib/jenkins/adminPassword

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

/home/jenkins/secrets/InitialAdminPassword

Set the "Build Periodically" trigger, but you don't have to specify an interval

None of these

Set the "GitHub hook trigger for GITScm polling" trigger

Set the "Poll scm" trigger, but you don't have to specify an interval

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' } }

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.

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.

None of these

It's only used for freestyle projects

It contains the definition for a pipeline

It contains the basic configuration for Jenkins

Credentials

My Views

New Item

Manage Jenkins

agent any

agent { label 'Slave 1'}

agent none

All of these

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.

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.

Building in 60 minutes or less.

A software development practice where contributors are integrating their work very frequently to production in an automated fashion.

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

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

True

False

If you check the "Enable rollbacks when upgrading" box, future updates to an the plugin can easily be rolled back when necessary.

The previous public release of a plugin is installed for reliability instead of Installing the most recent public release.

Most plugins can be Installed without stopping and starting Jenkins.

You must install all required and optional dependencies before Installing the plugin with the plugin manager.

If you are running Jenkins under an HTTP proxy, you must configure HTTP proxy access for the plugin manager before Installing or updating plugins.

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.

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.

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

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.

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

Automated deployment to the production environment.

Collaboration among Dev, QA and Ops.

Automated tests after each commit

Automated builds after each commit.

Frequent commits to source code repository.

email

notice

emailext

alert