Deployment pipelines (dev, staging, prod) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline Stage Execution Order

Given this Jenkins pipeline snippet, what will be the order of stage execution?

pipeline {
  agent any
  stages {
    stage('Dev') {
      steps { echo 'Deploying to Dev' }
    }
    stage('Staging') {
      steps { echo 'Deploying to Staging' }
    }
    stage('Prod') {
      steps { echo 'Deploying to Prod' }
    }
  }
}

Jenkins

pipeline {
  agent any
  stages {
    stage('Dev') {
      steps { echo 'Deploying to Dev' }
    }
    stage('Staging') {
      steps { echo 'Deploying to Staging' }
    }
    stage('Prod') {
      steps { echo 'Deploying to Prod' }
    }
  }
}

A 1,3,2

B 3,2,1

C 2,1,3

D 1,2,3

💡 Hint

Stages run in the order they are defined in the Jenkinsfile.

Jenkins executes pipeline stages sequentially in the order they appear in the Jenkinsfile unless parallel is used.

❓ Configuration

intermediate

Correct Jenkinsfile Syntax for Conditional Deployment

Which Jenkinsfile snippet correctly deploys to Prod only if the branch is main?

A

stage('Prod') {
  when {
    branch 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

B

stage('Prod') {
  when {
    branch == 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

C

stage('Prod') {
  when {
    branch = 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

D

stage('Prod') {
  when {
    branch != 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

💡 Hint

Check the correct syntax for the when condition in Jenkins declarative pipeline.

The when { branch 'main' } syntax is the correct way to conditionally run a stage only on the main branch.

❓ Troubleshoot

advanced

Jenkins Pipeline Fails on Staging Deployment

A Jenkins pipeline deploys successfully to Dev but fails at the Staging stage with this error:

ERROR: script returned exit code 1

Which option is the most likely cause?

A The Staging deployment script has a command that returns a non-zero exit code.

B The Jenkinsfile syntax is invalid causing the pipeline to fail before Staging.

C The Dev stage is skipped, so Staging cannot run.

D The Prod stage is running before Staging causing a conflict.

💡 Hint

Non-zero exit codes usually indicate a failure in shell commands.

The error means a command in the Staging deployment script failed and returned exit code 1, causing the pipeline to stop.

🔀 Workflow

advanced

Jenkins Pipeline with Manual Approval Before Production

Which Jenkins pipeline snippet correctly adds a manual approval step before deploying to Production?

A

stage('Prod') {
  steps {
    input 'Approve Production Deployment?'
    echo 'Deploying to Prod'
  }
}

B

stage('Prod') {
  steps {
    echo 'Deploying to Prod'
    input 'Approve Production Deployment?'
  }
}

C

stage('Prod') {
  steps {
    timeout(time: 1, unit: 'MINUTES') {
      input 'Approve Production Deployment?'
    }
    echo 'Deploying to Prod'
  }
}

D

stage('Prod') {
  when {
    input 'Approve Production Deployment?'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

💡 Hint

Manual approval uses input step, and timeout is good practice to avoid hanging.

Option C correctly uses input with a timeout to wait for manual approval before deploying.

✅ Best Practice

expert

Best Practice for Managing Secrets in Jenkins Pipelines

What is the best practice for handling sensitive credentials like API keys in Jenkins pipelines for deployment to multiple environments?

A Store secrets directly in the Jenkinsfile as plain text variables.

B Use Jenkins Credentials Plugin to securely store and inject secrets during pipeline execution.

C Commit secrets encrypted in the source code repository and decrypt them in the pipeline.

D Ask users to input secrets manually every time the pipeline runs.

💡 Hint

Think about security and automation in pipelines.

Using Jenkins Credentials Plugin is the recommended way to securely manage secrets without exposing them in code or logs.

Practice

1. What is the main purpose of having separate dev, staging, and prod stages in a Jenkins deployment pipeline?

easy

A. To deploy only to production without checks

B. To run the same tests multiple times unnecessarily

C. To test and verify code in different environments before final release

D. To slow down the deployment process

Solution

1. Step 1: Understand pipeline stages

   Each stage (dev, staging, prod) represents a different environment for testing and validation.

2. Step 2: Purpose of separate environments

   Separate environments help catch issues early and ensure stability before production deployment.

3. Final Answer:

   To test and verify code in different environments before final release -> Option C

4. Quick Check:

   Separate stages = safer deployment [OK]

Hint: Remember: dev, staging, prod = test, verify, release [OK]

Common Mistakes:

• Thinking all stages do the same thing
• Assuming staging is optional
• Believing deployment skips testing

2. Which of the following is the correct syntax to define a stage named "Staging" in a Jenkins declarative pipeline?

easy

A. stage 'Staging' steps { echo 'Deploying to staging' }

B. stage: Staging { steps: { echo 'Deploying to staging' } }

C. stage { name: 'Staging' steps { echo 'Deploying to staging' } }

D. stage('Staging') { steps { echo 'Deploying to staging' } }

Solution

1. Step 1: Recall Jenkins declarative syntax

   Stages are defined with stage('Name') { steps { ... } } blocks.

2. Step 2: Check each option

   stage('Staging') { steps { echo 'Deploying to staging' } } matches correct syntax; others have invalid syntax or missing braces.

3. Final Answer:

   stage('Staging') { steps { echo 'Deploying to staging' } } -> Option D

4. Quick Check:

   Correct stage syntax = stage('Staging') { steps { echo 'Deploying to staging' } } [OK]

Hint: Use parentheses and braces exactly as in official docs [OK]

Common Mistakes:

• Missing braces or parentheses
• Using colons instead of braces
• Incorrect keyword order

3. Given this Jenkins pipeline snippet, what will be the output if the staging stage fails?

pipeline {
  agent any
  stages {
    stage('Dev') {
      steps { echo 'Deploying to dev' }
    }
    stage('Staging') {
      steps { error 'Staging deployment failed' }
    }
    stage('Prod') {
      steps { echo 'Deploying to prod' }
    }
  }
}

medium

A. Deploying to dev\nError: Staging deployment failed\nProd stage skipped

B. Deploying to dev\nError: Staging deployment failed\nProd stage runs

C. Only Prod stage runs

D. Pipeline completes successfully without errors

Solution

1. Step 1: Understand pipeline flow

   Pipeline runs stages in order: Dev, Staging, Prod.

2. Step 2: Effect of error in Staging stage

   Error in Staging stops pipeline; Prod stage does not run.

3. Final Answer:

   Deploying to dev\nError: Staging deployment failed\nProd stage skipped -> Option A

4. Quick Check:

   Error in stage stops later stages [OK]

Hint: Error in a stage stops pipeline unless handled [OK]

Common Mistakes:

• Assuming Prod runs after Staging error
• Ignoring error messages
• Thinking pipeline completes despite errors

4. You have this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Dev') {
      steps { echo 'Deploying to dev' }
    }
    stage('Staging') {
      steps { sh 'deploy.sh' }
    }
    stage('Prod') {
      steps { echo 'Deploying to prod' }
    }
  }
}

The deploy.sh script is missing execute permission. What will happen when the pipeline runs the Staging stage?

medium

A. The Staging stage will succeed without running the script

B. The Staging stage will fail with a permission denied error

C. The pipeline will skip the Staging stage and continue to Prod

D. The pipeline will automatically fix permissions and run the script

Solution

1. Step 1: Understand shell script execution in Jenkins

   Jenkins runs shell commands as is; missing execute permission causes failure.

2. Step 2: Effect of missing execute permission

   Shell returns 'permission denied' error; stage fails and pipeline stops.

3. Final Answer:

   The Staging stage will fail with a permission denied error -> Option B

4. Quick Check:

   Missing execute permission = stage failure [OK]

Hint: Scripts must be executable before Jenkins runs them [OK]

Common Mistakes:

• Assuming Jenkins fixes permissions automatically
• Thinking stage will skip on error
• Believing script runs without execute permission

5. You want to create a Jenkins pipeline that deploys to dev automatically, but requires manual approval before deploying to staging and prod. Which pipeline snippet correctly implements this?

hard

A. pipeline {
agent any
stages {
stage('Dev') {
steps { echo 'Deploying to dev' }
}
stage('Staging') {
steps {
input 'Approve Staging?'
echo 'Deploying to staging'
}
}
stage('Prod') {
steps {
input 'Approve Prod?'
echo 'Deploying to prod'
}
}
}
}

B. pipeline {
agent any
stages {
stage('Dev') {
steps { echo 'Deploying to dev' }
}
stage('Staging') {
steps { echo 'Deploying to staging' }
}
stage('Prod') {
steps { echo 'Deploying to prod' }
}
}
}

C. pipeline {
agent any
stages {
stage('Dev') {
steps {
input 'Approve Dev?'
echo 'Deploying to dev'
}
}
stage('Staging') {
steps { echo 'Deploying to staging' }
}
stage('Prod') {
steps { echo 'Deploying to prod' }
}
}
}

D. pipeline {
agent any
stages {
stage('Dev') {
steps { echo 'Deploying to dev' }
}
stage('Staging') {
steps {
input 'Approve Prod?'
echo 'Deploying to staging'
}
}
stage('Prod') {
steps {
input 'Approve Staging?'
echo 'Deploying to prod'
}
}
}
}

Solution

1. Step 1: Identify manual approval usage

   Jenkins input step pauses pipeline for manual approval.

2. Step 2: Check stages with input

   pipeline { agent any stages { stage('Dev') { steps { echo 'Deploying to dev' } } stage('Staging') { steps { input 'Approve Staging?' echo 'Deploying to staging' } } stage('Prod') { steps { input 'Approve Prod?' echo 'Deploying to prod' } } } } uses input before staging and prod deployments, dev runs automatically.

3. Final Answer:

   Pipeline with input steps before staging and prod deployments -> Option A

4. Quick Check:

   Manual approval = input step before stage [OK]

Hint: Use input step to pause for approval in Jenkins [OK]

Common Mistakes:

• Adding input to dev instead of staging/prod
• Skipping input steps entirely
• Mixing approval prompts between stages