CCJE Practice Exam Questions with Answers Certified CloudBees Jenkins Engineer (CCJE) Certification

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).

Wait for existing builds to complete and then shut down Jenkins.

Wait for existing builds to complete and then restart Jenkins.

Cancel the effect of the "quiet-down" command if Jenkins is already in Quiet Down mode.

None of the above.

Manage plugins

Open Blue Ocean

Define views

Configure credentials

Configure Global Security

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 "Fingerprint" feature.

The "Archive the artifacts" post-build action.

The Jenkins Blueprint feature.

The can only be done if you install the Build Analysis plugin.

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.

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.

Scripted Pipelines usually execute significantly faster than the comparable Declarative Pipeline.

Declarative Pipelines usually use the "agent" section to define the node where the code should execute but the "node" parameter can be used instead and allows for additional options such as "customWorkspace’’.

Scripted Pipelines require extensive knowledge of the Apache Groovy syntax wher ease Declarative Pipelines can be implemented with minimal understanding of Groovy and so have a lower risk of syntax errors than Scripted Pipelines.

You can use the Declarative Directive Generator to help structure statements for Declarative Pipelines and use the Snippet Generator to help structure statements for Scripted Pipelines.

Scripted Pipelines can implement some functionality that Declarative Pipeline syntax does not support, although small bits of scripted syntax can be included In a Declarative Pipeline by using the "script" step.

superset

consolidation

process definition

requirement

subset

No default administrator account Is created; you have to configure security manually.

A default administrator account is created with username "admin" and password from the fie

JENKINS_HOME/secret/initialAdminPassword.

A default administrator account is created with user name "admin" and password "admin".

A default administrator account Is created and you cannot re-enable security.

To allow continuing the build on another agent.

To avoid having to rerun the entire Pipeline If a transient error occurs.

To visually separate stages.

To run additional tests.

To configure pipelines to send a progress report by email when a checkpoint is reached.

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.

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.

Polling can introduce additional delays.

A post-commit trigger build includes all dependencies.

Polling may consume unnecessary resources.

Poling will not check out the latest revision.

A post commit trigger build is more reliable.

Each build in the build queue must be manually attached to an available executor.

There are not enough Idle executors available on agent A.

The "Execute concurrent builds if necessary" option in the Job configuration has reached its user-defined maximum.

Changes were made to this Job's conjuration while this Job had builds in the build queue.

unit build data using the job setting "Discard old builds".

Change the order of jobs in the pipeline.

Gear the Jenkins cache.

Increase the size of the JENKINS.HOME partition/logical volume.

Make sure you regularly delete unused views.

M1 can only perform builds on S1.

M3 can only perform builds on S2.

M4 can perform builds on any shared agent.

M3 can only perform builds on S2 and S3.

M4 can only perform builds on S3.

--logfile -- Specify the path for the Jenkins log fie.

--installPlugin - Install a new plugin.

--Idap -- Specify an LDAP server location to use for user authentication.

-prefix - Spedfy a string to be added at the end of the URL for this instance.

--httpPort -- Specify the port on which Jenkins Iistens.

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.

Check the Jenkins Update Center.

Search for the plugin in the Jenkins artifact repository.

Email the maintainer.

Check the plugin wiki

The build has been skipped, and tests for all publishers have been skipped

The build has failed, and tests for all publishers have succeeded.

The build has succeeded, and tests for all publishers have been skipped.

The build has succeeded, and some tests for publishers have failed.