CloudBees CJE Certified Jenkins Engineer (CJE) Exam Practice Test

smoke tests

acceptance tests

functional tests

non-regression tests

@daily

H H * * *

30 12 * * *

All of these

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

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

No extra plugins must be installed.

Builds can be parameterized.

Builds can be triggered with millisecond granularity.

tests an Individual unit a component

verifies cross-functionalities

verifies that the complete software matches the specifications it was written to fulfill

is written when an Integration or multi-environment bog is fixed

None of these

junit-report "path to xml file"

generate "junit-report"

junit "path to xml file"

Continuous deployment means the code CAN be released at any time, while continuous integration means it is released continuously.

Continuous delivery means the code CAN be released at any time, while continuous integration means it is released continuously

Continuous integration is just the practice of integrating code continuously. It doesn't necessarily mean that it can be released at any time like continuous delivery

Continuous delivery and continuous integration are the same thing.

Manage credentials for Jenkins

All of these

Add a build step option to Jenkins

Provide backup functionality to Jenkins

The job must be configured to send email.

Jenkins must be successfully configured to point to a mail server.

Jenkins must be directly connected to the Internet.

Jenkins must have a unique email address.

Sendmail must be Installed and running on the same machine as Jenkins.

True

False

step('build') { sh 'ant -f build.xml -v' } }

stage('build') { sh 'ant -f build.xml -v' }

stage('build') { steps { sh 'ant -f build-tools/build.xml -v' } }

stage('build') { steps { sh 'ant -f build.xml -v' } }

Build times decrease.

User interface becomes slower as resources on the master run out.

The builds share SCM checkouts

Masters are more highly available.

Tune the "timer" section for the project.

Choose not to use a clean checkout.

There's no way to reduce the time

Use a clean checkout.

updates plugins

starts the build of a job

sends notification once the build is completed

detects code changes in the repository

Ant project

Make project

Grade project

Pipeline project

Freestyle project

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

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

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

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

agent any

agent { label 'Slave 1'}

agent none

All of these

A groovy script needs to be approved.

A build is waiting for Input.

The build is waiting for an executor to be available.

An agent is being spawned.

email

notice

emailext

alert

Source Code (or Control) Management

Structural Code Machine

Super Core Management

None of the above

None of these

An option that doesn't come with Jenkins by default

An option that doesn't allow user specific permissions

Allows the administrator to grant very specific permissions to users and groups.

when { branch 'development' }

when { branch 'master' }

when( $branch == 'development')

when 'development'

emailext

notice

email

alert

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.

Builds should be self-testing. That allows us maximum flexibility in spotting breaking changes and prevents a lot of staff time spent trying to both integrate a change and determine why it broke the build.

We should really use a single source repository. That makes it easier for us to manage what gets into the build pipeline.

Build everything manually, because that prevents errors.

Every commit should be built. That ensures we don't wind up with a lot of stray code and that any future change will be testable.

notice

alert

email

emailext

GIT_COMMIT

GIT_ORIGIN_URL

GIT_URL

GIT_BRANCH

Continuous Integration

Continuous Deployment

Continuous Delivery

Infrastructure as Code