CI/CD pipeline basics in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline stage?

Consider this Jenkins pipeline snippet for a Spring Boot project build stage. What will be the output after running the 'Build' stage?

Spring Boot

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean package'
      }
    }
  }
}

A Build successful with a generated JAR file in target/ directory

B Build fails due to missing Dockerfile

C Build successful but no JAR file generated

D Pipeline syntax error stops execution

💡 Hint

Maven's 'clean package' command compiles and packages the Spring Boot app.

The 'mvn clean package' command cleans previous builds and packages the app, producing a JAR file in the target directory if successful.

🧠 Conceptual

intermediate

Which step is essential in a CI/CD pipeline for Spring Boot to ensure code quality?

In a typical CI/CD pipeline for a Spring Boot application, which step is crucial to catch bugs early before deployment?

A Running unit and integration tests after build

B Deploying directly to production without tests

C Manual code review only without automated tests

D Skipping build and deploying source code

💡 Hint

Automated tests help catch errors early in the pipeline.

Running automated tests after building ensures code quality and prevents faulty code from progressing to deployment.

❓ Troubleshoot

advanced

Why does this Jenkins pipeline fail at the deploy stage?

Given this Jenkins pipeline snippet, why does the deploy stage fail?

Spring Boot

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean package'
      }
    }
    stage('Deploy') {
      steps {
        sh 'docker build -t springboot-app .'
        sh 'docker push springboot-app'
      }
    }
  }
}

A Deploy stage succeeds without errors

B Build fails because Maven command is incorrect

C Pipeline syntax error due to missing agent declaration

D Docker push fails because the image tag is incomplete or missing registry info

💡 Hint

Docker images usually require a full tag including registry or repository before push.

The 'docker push springboot-app' command fails because the image tag lacks registry or repository info, so Docker doesn't know where to push.

🔀 Workflow

advanced

What is the correct order of stages in a CI/CD pipeline for Spring Boot?

Arrange these stages in the correct order for a typical CI/CD pipeline:

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Tests should run after build and before deployment.

The pipeline builds the app first, then runs tests to verify it, then deploys to staging for validation, and finally to production.

✅ Best Practice

expert

Which practice improves CI/CD pipeline reliability for Spring Boot microservices?

To improve reliability and reduce downtime in CI/CD pipelines for Spring Boot microservices, which practice is best?

A Deploy all microservices simultaneously without testing

B Implement blue-green deployment to switch traffic between environments

C Skip automated tests to speed up deployment

D Manually update production servers without automation

💡 Hint

Blue-green deployment allows safe switching between versions.

Blue-green deployment reduces downtime by running two identical environments and switching traffic only after successful deployment.