Why containerization matters in Spring Boot - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use containerization with Spring Boot?

Which of the following best explains why containerization is important when deploying Spring Boot applications?

A It allows the application to run only on the developer's local machine.

B It packages the application with all dependencies, ensuring it runs the same everywhere.

C It replaces the need for a database by storing data inside the container.

D It automatically converts Java code into native machine code for faster execution.

💡 Hint

Think about how containerization helps with consistency across different environments.

Containerization bundles the Spring Boot app with everything it needs, so it behaves the same on any system.

❓ component_behavior

intermediate

Spring Boot app behavior inside a container

What happens when you run a Spring Boot application inside a Docker container on a different machine?

A The app runs slower because containers add heavy overhead.

B The app fails because Docker containers cannot run Java applications.

C The app runs but requires manual installation of dependencies on the new machine.

D The app runs exactly as on the original machine because the container includes all dependencies.

💡 Hint

Consider what a container includes when it runs an app.

Containers include the app and all needed parts, so the app runs the same on any machine with Docker.

📝 Syntax

advanced

Dockerfile for Spring Boot app

Which Dockerfile snippet correctly builds a container image for a Spring Boot application packaged as a jar?

A

FROM openjdk:8
COPY app.war /app.war
ENTRYPOINT ["java", "-war", "app.war"]

B

FROM node:latest
COPY app.jar /app.jar
CMD java -jar /app.jar

C

FROM openjdk:17-jdk
COPY target/app.jar app.jar
ENTRYPOINT ["java", "-jar", "app.jar"]

D

FROM python:3.9
COPY target/app.jar app.jar
RUN java -jar app.jar

💡 Hint

Look for the correct base image and command to run a jar file.

Option C uses the correct Java base image and runs the jar with the right ENTRYPOINT syntax.

🔧 Debug

advanced

Fixing container startup failure

A Spring Boot app container fails to start with error 'Could not find or load main class'. Which Dockerfile mistake causes this?

A

COPY target/app.jar /app.jar
ENTRYPOINT ["java", "-jar", "app.jar"]

B

COPY target/app.jar app.jar
ENTRYPOINT ["java", "-jar", "app.jar"]

C

COPY target/app.jar app.jar
ENTRYPOINT ["java", "-jar", "/app.jar"]

D

COPY target/app.jar /app.jar
ENTRYPOINT ["java", "-jar", "/app.jar"]

💡 Hint

Check if the path in ENTRYPOINT matches the copied file location.

Option A copies the jar to /app.jar but tries to run 'app.jar' without the leading slash, causing the error.

❓ state_output

expert

Container resource limits effect on Spring Boot app

If you limit CPU and memory for a Spring Boot container, what is the most likely effect on the app's behavior?

A The app may slow down or crash if it exceeds the limits, but it stays isolated from other system processes.

B The app will automatically optimize its code to use less memory and CPU.

C The app will ignore the limits and use all system resources available.

D The container will restart infinitely without running the app.

💡 Hint

Think about what resource limits do to processes inside containers.

Resource limits restrict CPU and memory usage, so the app may slow or crash if it needs more, but it won't affect other system apps.