You've just become the administrator for the Jenkins server, and the feedback you've received from the users is they're having trouble locating their jobs to run them. You've determined that folders are the most logical solution and wish to move the jobs into the new folders you've created. How would you accomplish this?

• A. Hover and click arrow on existing item, choose "move", select target folder.
• B. Click existing item; in the item view page, select "move" on the left panel; select target folder.
• C. All of these
• D. For new items, click folder; in the folder view, select new item; it will automatically be added to that folder.

You've been promoted at work and are now in charge of the system administrators that look after the Jenkins platform for your company. You no longer want to get notifications from Jenkins, but your subordinates don't know what settings to change in a Jenkinsfile. You give them a look, and say one of the following is what needs to be changed:

• A. alert
• B. emailext
• C. email
• D. notice

You are interested in integrating CI/CD in your work environment, but your team lead and several of your team members do not understand the concept. Your boss believes that continuous delivery will mean that someone (namely, you) will need to be on-call around the clock for constant monitoring and deployment of new code. You have a two-minute window to quickly explain what continuous delivery means. Out of the following answers, what is the clearest and most succinct correct answer?

• A. Continuous delivery means code will be tested and promoted to production environment automatically
• B. Continuous delivery is a software development discipline where software is built so that it can be released to production at any time, while continuous deployment means it is released into production continuously. CI/CD is meant to shorten the amount of time needed for QA while empowering developers to keep code as up-to-date as possible
• C. You're right. Give me the on-call schedule.
• D. Continuous delivery is magic, and Jenkins will make everything work without having to worry about it much.

Pipelines often require access to protected resources such as servers, databases, and SCMs. Without using an external credentials manager, which of the following provides the most secure centralized mechanism for managing the "secrets" that Jenkins requires to login/authenticate (for example: keys, tokens, passwords)?

• A. Store the secrets as Node Properties for each agent definition.
• B. Store the secrets required in the SCM alongside the application source code.
• C. Store the secrets on the Jenkins master using the Credentials plugin.
• D. Embed secrets into the build and deployment scripts invoked by the job.
• E. Include the secrets In the home directory of the Jenkins agent account.