CJE Certified Jenkins Engineer (CJE) Questions and Answers

The changes the team makes will be released to production at any time.

The software development team will increase the frequency at which code changes are committed to the build, test, and deployment cycles.

Software changes will now be added to an automated pipeline.

Build time objectives will be targeted to take less than 60 minutes.

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.

All of the others

Parameterized Trigger

Pipeline

Credentials

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.

Java

Perforce

Subversion

Git

Maven

.rb

.hpi

.groovy

.java

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.

It ensures the working directory is clean and not tampered with

None of these

It's faster

It ensures there are no mistakes

/opt/jenkins/

/var/lib/jenkins/secrets/

/tmp/Jenkins/

/usr/lib/jenkins/password/

None of these

Infrastructure is defined in source code, like the Jenkinsfile for a pipeline.

There's no hardware

Source code is hosted in your Infrastructure

Automate only when necessary

Making sure a manager approves every line of code

Fixing broken builds

Making sure everyone gets to contribute the exact same amount

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"

Acceptance testing

Smoke testing

Unit testing

Integration testing

Permissions to run jobs and Pipeline

Credentials

View definitions

Plugins

Pipeline shared libraries

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.

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.

Set the "GitHub hook trigger for GITScm polling" trigger

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

None of these

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

email

Slack

Jira

SMS messaging

All of the above

It shows items that match a filter regular expression.

It shows all items configured in Jenkins.

It shows all items a user has permission to view in Jenkins.

None of these

None of these

An option that doesn't come with Jenkins by default

An option that doesn't allow user specific permissions

Allows the administrator to grant very specific permissions to users and groups.

emailext

notice

email

alert

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

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.

True

False