Blue-green deployment pattern in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Blue-Green Deployment Basics

What is the main advantage of using the blue-green deployment pattern in Jenkins pipelines?

A It merges code branches automatically before deployment.

B It allows zero downtime by switching traffic between two identical environments.

C It encrypts all deployment artifacts for security.

D It automatically scales the application based on user load.

💡 Hint

Think about how user traffic is managed during deployment.

Blue-green deployment uses two identical environments (blue and green). One serves live traffic while the other is updated. Switching traffic avoids downtime.

💻 Command Output

intermediate

Jenkins Pipeline Step Output

Given this Jenkins pipeline snippet for blue-green deployment, what will be the output of the sh step?

stage('Switch Traffic') {
  steps {
    sh 'echo Switching traffic to green environment'
  }
}

A Switching traffic to green environment

B Error: Unknown command 'echo Switching traffic to green environment'

C No output, the step is skipped

D Switching traffic to blue environment

💡 Hint

What does the sh step do in Jenkins pipelines?

The sh step runs shell commands and prints their output. Here it echoes the message about switching traffic.

❓ Configuration

advanced

Correct Jenkinsfile Snippet for Blue-Green Deployment

Which Jenkinsfile snippet correctly implements switching traffic from blue to green environment using environment variables?

A

environment {
  ACTIVE_ENV = 'green'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl set image deployment/myapp myapp-container=myapp:${ACTIVE_ENV}"
  }
}

B

environment {
  ACTIVE_ENV = 'blue'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl set image deployment/myapp myapp-container=myapp:${ACTIVE_ENV}"
  }
}

C

environment {
  ACTIVE_ENV = 'red'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl set image deployment/myapp myapp-container=myapp:${ACTIVE_ENV}"
  }
}

D

environment {
  ACTIVE_ENV = 'green'
}
stage('Switch Traffic') {
  steps {
    sh "kubectl rollout restart deployment/myapp"
  }
}

💡 Hint

Focus on the environment variable value that matches the target environment for traffic switch.

Setting ACTIVE_ENV to 'green' and updating the deployment image to use that environment switches traffic correctly. 'red' is invalid and 'blue' would switch back.

❓ Troubleshoot

advanced

Troubleshooting Traffic Switch Failure

After running a blue-green deployment pipeline, users report downtime. Which Jenkins pipeline issue is the most likely cause?

A The pipeline used the correct environment variable for switching traffic.

B The pipeline skipped the deployment stage entirely.

C The pipeline switched traffic before the green environment was fully ready.

D The pipeline used a shell command to echo status messages.

💡 Hint

Think about what happens if traffic is switched too early.

If traffic switches before the new environment is ready, users experience downtime or errors. Proper readiness checks prevent this.

🔀 Workflow

expert

Blue-Green Deployment Workflow Steps

Arrange the following steps in the correct order for a blue-green deployment pipeline in Jenkins.

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about deploying first, then testing, then switching traffic, then monitoring.

The correct order is to deploy to the inactive environment, test it, switch traffic, then monitor for issues to ensure smooth deployment.