Which two statements are true regarding a Spring Boot "fat" JAR? (Choose two.)

Question

Options

• AThe "fat" JAR contains both the class files and the source files for your project.
• BThe "fat" JAR requires an external Servlet container.
• CThe "fat" JAR contains compiled classes and dependencies that your code needs to run.
• DThe "fat" JAR can contain multiple embedded application servers.
• EThe "fat" JAR is created by the Spring Boot Maven plugin or Gradle plugin.

• B
  6% (1)
• C
  94% (15)

Explanation

A Spring Boot "fat" JAR (also called an "uber JAR") packages your compiled application classes together with all runtime dependencies (C), making it fully self-contained - you can run it with just java -jar app.jar. This artifact is produced by the Spring Boot Maven or Gradle plugin (E), which rewrites the standard JAR packaging process to bundle everything needed.

Why the distractors are wrong:

• A is wrong because fat JARs contain compiled .class files, not source files (.java) - source code is not needed at runtime.
• B is the opposite of the truth: fat JARs embed a Servlet container (like Tomcat or Jetty), eliminating the need for an external one.
• D is wrong because a fat JAR embeds exactly one application server - you configure which one (Tomcat, Jetty, or Undertow), but not multiple simultaneously.

Memory tip: Think of a fat JAR as a "meals included" hotel - everything you need (compiled code + dependencies + embedded server) is packed in, and the Spring Boot build plugin is the chef who prepares it. No external reservations (Servlet containers) required.

No community discussion yet for this question.