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

Specify a target "label’’ on the Ouster Operations job configuration screen, restricting al operations to Masters and Update Centers with that label.

Specify a target "label" on each operation on the Ouster Operations job configuration screen, restricting that operation to masters and Update Centers with that label.

Specify a target "source" and "filter" on the operation on the Cluster Operations Job configuration screen.

It is not possible to limit steps to specific targets.

Operations Center enables you to interconnect different CI systems, such as CloudBees CodeShip and Jenkins

It is easier to share resources among Jenkins masters that are connected to the same Operations Center.

It is easier to run Pipelines on the Operations Center because it can retrieve resources from all connected masters.

Operations Center handles the build toad more efficiently by scheduling tasks on idle Jenkins masters.

It Is easier to perform administration tasks (such as upgrading a plugin) on a group of masters that are attached to the same Operations Center.

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.

starts the build of a job

updates plugins

sends notification once the build is completed

detects code changes in the repository

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.

superset

consolidation

process definition

requirement

subset

Number of plugins instated on the Jenkins instance.

The number of users registered on the Jenkins instance.

The memory used to run the Jenkins instance.

Number of Jobs in the build queue.

HTTP requests received by the Jenkins instance.

non regression tests

acceptance tests

smoke tests

functional tests

Purchase the fingerprint license and install the Jenkins fingerprint service pack.

Enable "record fingerprints of files" in the post-build actions section of a Job to track usage.

Use a laptop or personal computer with an integrated fingerprint scanner.

All of the above.

Define team specific folders and restrict edit access to team members.

You cannot. Each team must use a separate master.

You do not need to do anything. Job editing is restricted to team members by default.

Define team-specific views and set the initial view to the team-specific view.

transfers artifacts to a staging server for testing

can be used to group a number of other steps into a logical unit for display

prepares a test environment in Jenkins

collects a set of artifacts that can be referenced in a later Pipeline step

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.

Restrict an agent to a folder.

Assign an administrator to a folder.

Enable logging for a folder.

Restrict which kinds of items may be created in a folder.