CJE Certified Jenkins Engineer (CJE) Questions and Answers

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.

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

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.

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

Create additional Jenkins Masters and deploy the job to each one. Schedule the job staggered by 30 minutes on each one so that the additional master servers won’t be busy if the first job runs long.

Add one or more slave nodes to the environment, this will allow us to deploy code to multiple end points at one time. Break up the single job into multiple jobs so that each one can be triggered by the successful completion of the previous job to eliminate scheduling problems on beginning a new build in the event subsequent steps run longer than the intended time period.

None of these

Remove the performance testing from the build. Schedule performance testing as a separate job 30 minutes after the build runs and trigger a rollback if the performance testing fails at this point.

A username and password configured for the slave node

SSH keys with the Master's pub key set as an authorized key on the agent node

No special authorization setup

None of these

Boolean

File

String

md5

If your Jenkinsfile specifies parameters with the "parameters'' directive, those are the only parameters recognized when the Pipeline executes; any parameters that were specified In the "Project is parameterized" section of the Job configuration are cleared.

Use the "params" object to reference parameters that are defined on "The project is parameterized" section of the job configuration.

Use the "parameters" directive to define parameters for your Pipeline Inside your Pipeline code.

If you configure a build parameter of type File, then users can specify a file on the server as build input.

Add or change tests as necessary

Checkout from an SCM.

Update with latest code from the mainline.

Ask your manager for permission to commit code.

Continuous Integration

Continuous Deployment

Continuous Delivery

Infrastructure as Code

Manage credentials for Jenkins

All of these

Add a build step option to Jenkins

Provide backup functionality to Jenkins

Jenkins

Subversion

Git

Both Git and Subversion

config {..}

project {..}

pipeline {..}

test {..}

Store the secrets on the Jenkins master using the Credentials plugin.

Include the secrets In the home directory of the Jenkins agent account.

Store the secrets required in the SCM alongside the application source code.

Embed secrets into the build and deployment scripts invoked by the job.

Store the secrets as Node Properties for each agent definition.

Building in 60 minutes or less.

A software development discipline where software is built so that it can be released to production at any time.

A software development discipline where software is released continuously as part of an automated pipeline.

A software development practice where contributors are integrating their work very frequently.

Maximum number of jobs which can be run concurrently on attached agents.

Number of Java threads that can run Jenkins jobs.

Number of external build agents that can be used for jobs run on this Jenkins master.

Number of CPU cores configured for this master.

Number of jobs that can execute simultaneously on the Jenkins master

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.

Ant project

Make project

Grade project

Pipeline project

Freestyle project

Beekeeper Upgrade Assistant if you are running CloudBees Jenkins Distribution or CloudBees Core.

An email message that is automatically sent to all users who have registered with the mailing list at Jenklnssd-advisories@googlegroups.com.

A banner displayed in the upper right section of the master's home page.

An email message sent to all users who are listed in the "Send security notifications'' field of the "Extended E-mail Notification" configuration.

Jenkins logs.

archiveArtifacts = 'build/mybuilt.jar', fingerprint: true

archiveArtifacts artifacts: ''build/mybuilt.jar'

archiveArtifacts artifacts: 'build/mybuilt.jar', fingerprint: false

archiveArtifacts artifacts: 'build/mybuilt.jar', fingerprint: true

agent any

agent { label 'Slave 1'}

agent none

All of these

Feature branching and release branching, but not developer branching, are common branching strategies.

Developer branching and feature branching, but not release branching, are common branching strategies.

Developer branching, feature branching, and release branching are common branching strategies.

Release branching and developer branching, but not feature branching, are common branching strategies.

None of these

It's only used for freestyle projects

It contains the definition for a pipeline

It contains the basic configuration for Jenkins

Any Pipeline DSL code that Implements complex computational tasks must be located outside any stage block.

Steps are the logical segmentation of a Pipeline; they contain stages that define actual tasks.

Stages are the logical segmentation of a Pipeline; they contain steps that define actual tasks.

Each pipeline must have a global agent specification.

All stages in a Pipeline must execute on the same type of agent.

It tests components coming together

It tests against the product specifications.

It tests a small piece of functionality, usually at the class method level.

It tests how well your code is tested.

It reports its health as "failed" {"Raining Cloud" weather icon), because that is the "worst health of the sub-items".

It reports its health as "success" ("Sunny" weather icon), because that is the health of the "latest built item."

It must be configured with a dedicated "Health Metric" setting before it can report its health with weather icons.

It does not report its health on the folder level; only Jobs report health.

Use an input step just before the deploy stage.

This is not possible using Pipeline, because a Pipeline must run from start to finish without human interaction.

Create a separate Pipeline to run the deploy stage.

Use a stage step just before the deploy stage.