What is Continuous Delivery vs Continuous Deployment in Jenkins - Practice Questions & Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between Continuous Delivery and Continuous Deployment

Which statement correctly describes the difference between Continuous Delivery and Continuous Deployment in a Jenkins pipeline?

A Continuous Delivery automatically deploys every change to production without manual approval, while Continuous Deployment requires manual approval before production deployment.

B Continuous Delivery skips automated testing and deploys code directly to production; Continuous Deployment includes automated testing before deployment.

C Continuous Delivery ensures code changes are automatically tested and ready for deployment, but deployment to production requires manual approval; Continuous Deployment automatically deploys every change to production without manual approval.

D Continuous Delivery and Continuous Deployment are the same and both require manual approval before production deployment.

💡 Hint

Think about whether production deployment happens automatically or needs a manual step.

Continuous Delivery means the code is always ready to deploy after automated tests, but a human decides when to deploy. Continuous Deployment means every change that passes tests is automatically deployed to production.

🔀 Workflow

intermediate

Jenkins Pipeline Step for Continuous Delivery

In a Jenkins pipeline, which step best represents the manual approval process typical in Continuous Delivery before deploying to production?

A stage('Deploy to Production') { steps { sh 'deploy.sh' } }

B input 'Approve deployment to production?'; stage('Deploy to Production') { steps { sh 'deploy.sh' } }

C stage('Deploy to Production') { steps { sh 'deploy.sh' } } post { always { input 'Approve deployment?' } }

D stage('Deploy to Production') { steps { input 'Approve deployment?'; sh 'deploy.sh' } }

💡 Hint

Look for the step that pauses the pipeline and waits for manual approval before deployment.

The input step pauses the pipeline and waits for a user to approve before continuing to the deployment stage, which is typical in Continuous Delivery.

💻 Command Output

advanced

Jenkins Pipeline Output for Continuous Deployment

Given this Jenkins pipeline snippet for Continuous Deployment, what will be the output after a successful build and test?

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { echo 'Building...' }
    }
    stage('Test') {
      steps { echo 'Testing...' }
    }
    stage('Deploy') {
      steps { echo 'Deploying to production...' }
    }
  }
}

A

Building...
Testing...
Deploying to production...

B

Building...
Testing...
Pipeline paused for manual approval

C

Building...
Testing...
Deployment skipped

D Build failed, deployment not started

💡 Hint

Continuous Deployment means deployment happens automatically after tests pass.

The pipeline runs build, test, and deploy stages automatically without manual approval, so all echo statements appear in order.

❓ Troubleshoot

advanced

Pipeline Stuck Waiting for Approval

A Jenkins pipeline configured for Continuous Delivery is stuck and not progressing past the deployment stage. The pipeline script includes an input step before deployment. What is the most likely cause?

A The <code>input</code> step is waiting for manual approval which has not been given yet.

B The deployment script has a syntax error causing the pipeline to hang.

C The Jenkins agent is offline, so the pipeline cannot continue.

D The pipeline is missing the <code>stage</code> keyword before deployment.

💡 Hint

Think about what the input step does in a pipeline.

The input step pauses the pipeline and waits for a user to approve. If no one approves, the pipeline stays stuck at that point.

✅ Best Practice

expert

Best Practice for Safe Continuous Deployment

Which Jenkins pipeline practice best supports safe Continuous Deployment to production?

A Deploy to production only once a month to reduce risk.

B Require manual approval for every deployment to production to avoid mistakes.

C Deploy to production immediately after build without running tests to save time.

D Run automated tests and deploy only if all tests pass, with monitoring and rollback steps included.

💡 Hint

Consider automation combined with safety measures in Continuous Deployment.

Safe Continuous Deployment automates deployment after successful tests and includes monitoring and rollback to quickly fix issues.