CCJE Certified CloudBees Jenkins Engineer (CCJE) Questions and Answers

define the security settings of the Jenkins instance you are installing

define an admin user for Jenkins

define non-admin users for Jenkins

completely define the security and notification settings of the Jenkins instance you are installing

define executor agents

Outage of a master will not block flows for all products.

You can easily restrict access to a department's protects to the users within that department.

You can tailor the installed plugins to be specific to the needs of the environment.

You can more easily create pipelines covering entire products.

Builds can be triggered with millisecond granularity.

Job definition can be loaded from the Source Code Management system at build time.

Jenkins can be restarted while a build is In progress without impacting the build.

Builds can be parameterized.

No extra plugins must be installed.

Upgrade every plugin in the system to the latest available version.

Upgrade to a new version of CloudBees Core if it is available.

Upgrade every plugin In the CAP Collectionto the version defined by CAP.

Replace every plugin in the system with the version defined by CAP.

Each instance can have a different Jenkins version and a different JDK version as long as they all run on the same operating system version.

All instances must run the same JDK version.

All instances must be +/- one ma)or revision from each other.

All instances must run the same Jenkins version and the same JDK version.

All instances must run the same Jenkins version.

Builds are started on a defined cron schedule.

Builds are started immediately after changes are committed.

Avoid unnecessary overhead from polling.

The entire repository is scanned so no commits are missed.

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

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.

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

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.

It is not possible to control the effect of an operation failure. The build fails immediately.

Set the "Failure Mode" in the advanced options in a Ouster Operations Job configuration.

Create a Freestyle Job that listens to the build result of a Ouster Operations build and then dynamically sets the "Failure Mode".

With the CloudBees Monitoring plugin installed, configure an "Alert" In Jenkins global configuration (Manage Jenkins -> Configure System).

Declarative syntax can express complex flows and conditionals.

A jenkinsfile can express the entire CI/CD process as code that is stored in a Source Code Management system.

Execution can be resumed after most failures.

The Jenkinsfile can incorporate any valid Apache Groovy code.

Declarative Pipeline uses the Pipeline domain specific language (DSL) to manipulate Jenkins objects.

It makes it easy to fork and merge code.

It requires a central server and a standby server.

It requires one server in each location.

It requires fast network access for dairy work.

It operates without a central server.