Cheat sheet & self-check

Pick an answer to see if you got it, and why.

1. Q1. What does Jenkins Configuration as Code (JCasC) give you?

   1. AFaster builds
   2. BThe whole controller configuration in reviewed YAML, so a controller can be rebuilt or changed reproducibly instead of by clicking
   3. CEncrypted jobs
   4. DFree plugins
   Show answer

   B. With JCasC, plugins pinned in a file and Jenkinsfiles in repos, the controller becomes rebuildable from Git.

   From lesson 07 · Security and operations

2. Q2. How should team credentials be scoped?

   1. AAll global
   2. BIn each team's folder, so only that team's jobs can use them; global only for truly shared, low-risk credentials
   3. CIn Jenkinsfiles
   4. DIn agent images
   Show answer

   B. Folder-scoped credentials limit what a compromised or careless pipeline can reach.

   From lesson 07 · Security and operations

3. Q3. Why are plugin updates a security task, not just maintenance?

   1. AThey aren't
   2. BPlugins run inside the controller with full privileges, and Jenkins publishes regular security advisories for them; outdated plugins are a common way in
   3. CUpdates add features only
   4. DPlugins are sandboxed
   Show answer

   B. Track advisories, update on a routine, test in staging, and remove plugins you don't use.

   From lesson 07 · Security and operations

4. Q4. Why set the built-in (controller) node to 0 executors?

   1. ATo save money
   2. BBuilds on the controller can read its files, including credentials and configuration; run builds only on agents
   3. CIt's faster
   4. DJenkins requires it
   Show answer

   B. The controller holds secrets for every job. Isolating builds to agents limits what a malicious build can reach.

   From lesson 08 · Jenkins in the real world

5. Q5. What problem do Jenkins shared libraries solve?

   1. APlugin updates
   2. BCopy-pasted pipeline logic across many Jenkinsfiles; common steps live in one versioned library
   3. CDisk space
   4. DUser login
   Show answer

   B. Like reusable workflows in Actions (lesson 02): one place to fix and improve, versioned so teams upgrade deliberately.

   From lesson 08 · Jenkins in the real world

6. Q6. Your single Jenkins controller dies in the middle of a release. What design would have reduced the impact?

   1. ANothing
   2. BConfig as code + pinned plugins in an image + backed-up JENKINS_HOME for fast rebuild, builds that are reproducible outside CI, and a documented manual release path
   3. CMore plugins
   4. DA bigger VM only
   Show answer

   B. CI is a dependency of every release. It needs a tested recovery path and a fallback, like any production system.

   From lesson 08 · Jenkins in the real world