CloudBees CCJE Certified CloudBees Jenkins Engineer (CCJE) Exam Practice Test

Building, testing, and deploying the selected files to production environment.

Creating an archive file of the selected artifacts.

Recording the MD5 checksum of the selected artifacts.

Enabling access passwords for the selected artifacts.

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.

Build parameters

Matrix based security

Job Configuration Restriction plugin

Declarative Pipeline

System environment variables

Users will notice that builds in progress on the failed node are lost but they will not notice any downtime on the service because the sessions and workload are shared between participating Client Master nodes; we have an active-active HA setup.

Users will not notice anything because participating Master nodes share workloads together; we have an active-active HA setup.

Users will experience a brief downtime, comparable to the time required to reboot a Jenkins master in a non-HA setup. Freestyle builds that were in progress are lost, but Pipeline builds will resume when the secondary master is online; we have an active passive setup.

Users will not notice anything because the sessions are shared between participating Client Masters and the $JE NKINS HOME directory of the failed Client Master Is copied to resume the failed master's work; we have an active passive setup.

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.

explicitlydefine the user name and password for the admin user

select from a set of community-chosen plugins to be included on the Instance being installed

define an admin user for Jenkins

skip the creation of an admin user and use a default user instead

define the avatar for the admin user

The JENKINS.HOME directory.

The user's home directory.

The Workspace directory.

The Builds directory in the job.

If an environment variable b enclosed In single quotes, the Pipeline DSL dereferences the variable on the master's JVM and passes the calculated

string to the sh or bat step; If the environment variable Is enclosed In double quotes, the name of the environment variable Itself Is passed to the "sh" or "baT step and the she! Interpreter on the agent dereferences the variable.

An environment variable can be specified globally (to apply to all steps In the pipeline), for an individual step, or for one or more specified steps In the Pipeline.

If an environment variable Is enclosed In double quotes, the Pipeline DSL dereferences the variable on the master's JVM and passes the calculated string to the sh or bat step; If the environment variable Is enclosed In single quotes, the name of the environment variable Itself Is passed to the "sh" or "bat" step and the shell Interpreter on the agent dereferences the variable.

A Declarative Pipeline can use environment variables defined in Jenkins itself (such as BUILD.NUMBER and JENKINS_URL), environment variables defined in an installed plugin (such as GIT_COMMIT or GIT.BRANCH, defined m the Git plugin), or environment variables that are coded as directives In the Pipeline Itself: the semantics are identical for all environment variables.

Log in without entering a password.

Share a user/password pair between jobs.

Define what jobs a user can see.

Generate random passwords to use with third-party integrations.

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

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

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

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

It allows jobs to have dedicated machines tailored to specialized needs.

It improves the throughput of master executors.

It reduces the impact on productivity if there is an outage of a build node.

It decreases the load on the network.

A plugin downgrade will fall if the Installed version is needed by an installed plugin outside the CAP Collection.

Plugins outside the CAP Collection will be downgraded If needed to maintain the system consistency.

Plugins will be downgraded even if there are other plugins that have an optional dependency on the installed version.

Plugin downgrades are very safe operations, so no backups are needed.

Only plugins inside the CAP Collection can be downgraded.

In the Updates tab of the Plugin Manager, offered updates of plugins outside the CAP Collection are always the latest version.

Plugins in the CAP Collection can only be installed In the Initial Setup Wizard.

In the Updates tab of the Plugin Manager, no updates are offered for plugins In the CAP Collection.

In the Available tab of the Plugin Manager, only the plugins in the CAP Collection are offered.