Initial admin setup wizard in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start Jenkins with the setup wizard enabled.

Jenkins

java -jar jenkins.war --[1]

Drag options to blanks, or click blank then click option'

Aenable-setup-wizard

BhttpPort=8080

Cdisable-setup-wizard

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Using --disable-setup-wizard disables the wizard, which is not what we want.

Using httpPort=8080 sets the port but does not affect the wizard.

Using --version only shows the version and exits.

The --enable-setup-wizard option starts Jenkins with the initial admin setup wizard enabled.

2fill in blank

medium

Complete the code to unlock Jenkins by providing the initial admin password file path.

Jenkins

cat [1]

Drag options to blanks, or click blank then click option'

A/var/log/jenkins/jenkins.log

B/var/lib/jenkins/secrets/initialAdminPassword

C/etc/jenkins/config.xml

D/usr/share/jenkins/jenkins.war

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to read the config.xml file instead of the password file.

Looking in the wrong directory for the password.

Reading the Jenkins log file instead of the password.

The initial admin password is stored in /var/lib/jenkins/secrets/initialAdminPassword. Reading this file lets you unlock Jenkins during setup.

3fill in blank

hard

Fix the error in the command to disable the Jenkins setup wizard.

Jenkins

java -jar jenkins.war --[1]

Drag options to blanks, or click blank then click option'

Adisable-setup-wizard

Bdisable_setup_wizard

CdisableSetupWizard

Ddisable-setupwizard

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores instead of hyphens.

Using camelCase instead of hyphen-separated words.

Missing hyphen between 'setup' and 'wizard'.

The correct option to disable the setup wizard is --disable-setup-wizard with hyphens.

4fill in blank

hard

Complete the code to create a dictionary comprehension that maps plugin names to their versions, filtering only plugins with version greater than 1.0.

Jenkins

{plugin: version for plugin, version in plugins.items() if version [1] '1.0'}

Drag options to blanks, or click blank then click option'

B>

C<

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Putting an operator in BLANK_1 which breaks the syntax.

Using < or == instead of > for filtering versions.

The dictionary comprehension maps each plugin to its version without modification (empty string for BLANK_1). The filter keeps plugins with version greater than '1.0' using >.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps plugin names in uppercase to their versions, filtering only plugins with version equal to '2.0'.

Jenkins

{ [1]: [2] for plugin, version in plugins.items() if version [3] '2.0' }

Drag options to blanks, or click blank then click option'

Aplugin.upper()

Bversion

C==

Dplugin

Attempts:

3 left

💡 Hint

Common Mistakes

Using the plugin name without uppercasing.

Using wrong comparison operators like < or >.

Swapping key and value positions.

The dictionary comprehension uses plugin.upper() as the key, version as the value, and filters plugins where version == '2.0'.

Practice

1. What is the main purpose of the Jenkins initial admin setup wizard?

easy

A. To deploy Jenkins jobs automatically

B. To configure Jenkins system settings like memory and CPU usage

C. To guide users through installing plugins and creating the first admin user

D. To backup Jenkins data to the cloud

Solution

1. Step 1: Understand the wizard's role

   The initial admin setup wizard helps new Jenkins users start quickly by guiding them through essential setup steps.

2. Step 2: Identify key tasks of the wizard

   It installs recommended plugins and creates the first admin user to secure Jenkins access.

3. Final Answer:

   To guide users through installing plugins and creating the first admin user -> Option C

4. Quick Check:

   Wizard purpose = guide setup [OK]

Hint: Wizard sets up plugins and admin user first [OK]

Common Mistakes:

• Thinking it configures system resources
• Assuming it deploys jobs automatically
• Believing it handles backups

2. Which of the following commands is used to unlock Jenkins during the initial admin setup?

easy

A. cat /var/lib/jenkins/secrets/initialAdminPassword

B. jenkins unlock --start

C. sudo service jenkins unlock

D. unlock-jenkins --password

Solution

1. Step 1: Identify the unlock method

   Jenkins stores the initial admin password in a file named initialAdminPassword inside the secrets directory.

2. Step 2: Use the correct command to read the password

   The cat command displays the password content to unlock Jenkins.

3. Final Answer:

   cat /var/lib/jenkins/secrets/initialAdminPassword -> Option A

4. Quick Check:

   Unlock command = cat password file [OK]

Hint: Use cat on initialAdminPassword file to unlock [OK]

Common Mistakes:

• Using non-existent Jenkins unlock commands
• Trying to unlock via service commands
• Confusing unlock with start or restart commands

3. After completing the initial admin setup wizard, what will Jenkins display when you access the dashboard for the first time?

medium

A. A prompt to create a new admin user

B. The Jenkins dashboard with default plugins installed

C. An error message about missing plugins

D. A blank page with no content

Solution

1. Step 1: Understand wizard completion effects

   Completing the wizard installs recommended plugins and sets up the admin user.

2. Step 2: Identify the dashboard state after setup

   Jenkins shows the dashboard with default plugins ready for use, not an error or blank page.

3. Final Answer:

   The Jenkins dashboard with default plugins installed -> Option B

4. Quick Check:

   Dashboard after setup = plugins installed [OK]

Hint: Dashboard shows plugins after setup wizard completes [OK]

Common Mistakes:

• Expecting a prompt to create admin again
• Thinking an error appears about plugins
• Assuming the page is blank initially

4. You ran the initial admin setup wizard but Jenkins still asks for the unlock password repeatedly. What is the most likely cause?

medium

A. The initialAdminPassword file was deleted or inaccessible

B. The Jenkins service is not running

C. The plugins failed to install

D. The admin user was created twice

Solution

1. Step 1: Identify why unlock repeats

   Jenkins requires the initial admin password from the initialAdminPassword file to unlock.

2. Step 2: Understand impact of missing password file

   If the file is deleted or unreadable, Jenkins cannot verify unlock and keeps asking for the password.

3. Final Answer:

   The initialAdminPassword file was deleted or inaccessible -> Option A

4. Quick Check:

   Unlock repeats if password file missing [OK]

Hint: Check if initialAdminPassword file exists and is readable [OK]

Common Mistakes:

• Assuming Jenkins service stopped causes unlock loop
• Blaming plugin installation failure for unlock issue
• Thinking duplicate admin users cause unlock prompt

5. You want to automate Jenkins initial setup without manual unlock. Which approach correctly achieves this?

hard

A. Pre-create the initialAdminPassword file with a known password before Jenkins starts

B. Install Jenkins plugins manually after first login

C. Use Jenkins CLI to skip the unlock step after startup

D. Disable the initial admin setup wizard in Jenkins configuration files

Solution

1. Step 1: Understand automation goal

   To avoid manual unlock, the initial setup wizard must be disabled or bypassed.

2. Step 2: Identify correct method

   Disabling the wizard in Jenkins configuration allows automated startup without unlock prompts.

3. Step 3: Evaluate other options

   Pre-creating password file is insecure and unreliable; CLI cannot skip unlock; manual plugin install is after unlock.

4. Final Answer:

   Disable the initial admin setup wizard in Jenkins configuration files -> Option D

5. Quick Check:

   Disable wizard to automate setup [OK]

Hint: Disable wizard in config to skip manual unlock [OK]

Common Mistakes:

• Trying to pre-create password file manually
• Assuming CLI can skip unlock step
• Thinking manual plugin install automates unlock