POM.xml and dependencies in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Dependency Scope in POM.xml

In a Spring Boot project, what is the effect of setting a dependency's scope to provided in the POM.xml?

A The dependency is included in the final build artifact and available at runtime.

B The dependency is only available during compilation but not included in the final artifact.

C The dependency is excluded from compilation and runtime but used for testing only.

D The dependency is downloaded but never used in the project.

💡 Hint

Think about dependencies provided by the runtime environment like a servlet container.

Dependencies with provided scope are needed to compile the project but are expected to be supplied by the runtime environment, so they are not packaged in the final artifact.

❓ component_behavior

intermediate

Effect of Missing Spring Boot Starter Dependency

What happens if you omit the spring-boot-starter-web dependency in your Spring Boot POM.xml but try to create a REST controller?

A The application starts normally but REST endpoints return 404 errors.

B The application starts and REST endpoints work without issues.

C The application fails to start due to missing web server classes.

D The application starts but logs warnings about missing dependencies.

💡 Hint

Consider what the starter web dependency provides.

The spring-boot-starter-web includes embedded Tomcat and Spring MVC. Without it, the app lacks web server classes and fails to start.

📝 Syntax

advanced

Identify the Correct Dependency Declaration

Which POM.xml dependency snippet correctly adds the Spring Boot Starter Data JPA dependency?

A

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>

B

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-data-jpa</artifactId>
</dependency>

C

<dependency>
  <groupId>springframework.boot</groupId>
  <artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>

D

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-data-jpa</artifactId>
  <version>2.7.0</version>
</dependency>

💡 Hint

Check groupId spelling and if version is needed explicitly.

Spring Boot manages versions for starters, so version tag is optional if using parent POM. GroupId must be exactly org.springframework.boot.

🔧 Debug

advanced

Diagnose Dependency Conflict in POM.xml

You added two dependencies: spring-boot-starter-web and spring-boot-starter-webflux. Your app fails to start with a bean creation error. What is the likely cause?

A Both starters provide conflicting web server implementations causing bean conflicts.

B You forgot to add <code>spring-boot-starter-data-jpa</code> dependency.

C The POM.xml is missing the <code>spring-boot-maven-plugin</code>.

D The Java version is incompatible with Spring Boot starters.

💡 Hint

Think about the difference between traditional MVC and reactive web frameworks.

spring-boot-starter-web uses Spring MVC, while spring-boot-starter-webflux uses reactive programming. Including both causes conflicts in web server beans.

❓ state_output

expert

Resulting Dependency Tree Size

If your Spring Boot POM.xml includes only spring-boot-starter-web and spring-boot-starter-data-jpa, approximately how many direct and transitive dependencies will Maven download?

A About 10 dependencies total

B About 30 dependencies total

C More than 100 dependencies total

D About 60 dependencies total

💡 Hint

Consider that starters bring many libraries transitively.

Each Spring Boot starter pulls many dependencies transitively. Together, these two starters typically bring around 60 dependencies.

Practice

1. What is the main purpose of the pom.xml file in a Spring Boot project?

easy

A. To configure the web server settings

B. To manage project configuration and dependencies

C. To store database records

D. To write Java code for the application

Solution

1. Step 1: Understand the role of pom.xml

   The pom.xml file is used to organize project settings and list needed libraries.

2. Step 2: Identify what pom.xml does not do

   It does not contain Java code, database data, or server settings directly.

3. Final Answer:

   To manage project configuration and dependencies -> Option B

4. Quick Check:

   Project setup = Manage dependencies [OK]

Hint: Think of pom.xml as your project's shopping list [OK]

Common Mistakes:

• Confusing pom.xml with Java source files
• Thinking it stores runtime data
• Assuming it configures server directly

2. Which of the following is the correct way to add the Spring Boot starter web dependency in pom.xml?

easy

A. \n org.springframework.boot\n spring-boot-starter-web\n

B. \n springframework.boot\n spring-web-starter\n

C. \n org.springframework\n boot-starter-web\n

D. \n org.boot.spring\n starter-web\n

Solution

1. Step 1: Check the correct groupId and artifactId for Spring Boot web starter

   The official groupId is org.springframework.boot and artifactId is spring-boot-starter-web.

2. Step 2: Compare options to official naming

   Only \n org.springframework.boot\n spring-boot-starter-web\n matches the exact correct groupId and artifactId.

3. Final Answer:

   Correct dependency XML with org.springframework.boot and spring-boot-starter-web -> Option A

4. Quick Check:

   Correct groupId/artifactId = \n org.springframework.boot\n spring-boot-starter-web\n [OK]

Hint: Remember exact spelling of groupId and artifactId [OK]

Common Mistakes:

• Swapping groupId and artifactId
• Misspelling 'spring-boot-starter-web'
• Using wrong groupId like 'springframework.boot'

3. Given this pom.xml snippet, what will happen when you run mvn clean install?

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>

medium

A. Only the JPA API will be included, no implementation

B. The project will fail because version is missing

C. The project will include JPA support and related libraries automatically

D. The dependency will be ignored without a scope tag

Solution

1. Step 1: Understand Spring Boot starter dependencies

   Spring Boot starters manage versions internally, so explicit version is not needed if parent is set.

2. Step 2: Recognize what spring-boot-starter-data-jpa provides

   It includes JPA API and an implementation like Hibernate automatically.

3. Final Answer:

   The project will include JPA support and related libraries automatically -> Option C

4. Quick Check:

   Spring Boot starters handle versions and implementations [OK]

Hint: Spring Boot starters bundle needed libs and versions [OK]

Common Mistakes:

• Thinking version tag is always required
• Assuming only API without implementation
• Believing scope tag is mandatory for dependencies

4. You added this dependency to your pom.xml but get a build error:

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-web</artifactId>
  <version>2.3.0.RELEASE</version>
</dependency>

What is the likely cause?

medium

A. Incorrect groupId spelling

B. Missing scope tag causes build failure

C. Dependency must be in build section, not dependencies

D. Version conflicts because Spring Boot parent manages versions

Solution

1. Step 1: Understand Spring Boot parent version management

   Spring Boot starter parent manages dependency versions automatically.

2. Step 2: Identify problem with manually specifying version

   Manually adding version can cause conflicts and build errors.

3. Final Answer:

   Version conflicts because Spring Boot parent manages versions -> Option D

4. Quick Check:

   Let parent manage versions to avoid conflicts [OK]

Hint: Avoid manual versions if using Spring Boot starter parent [OK]

Common Mistakes:

• Adding version manually when parent manages it
• Thinking scope is required for starters
• Misplacing dependencies outside dependencies

5. You want to add a custom library that is not in Maven Central to your Spring Boot project. Which is the best way to include it in your pom.xml?

hard

A. Upload the library to a remote repository and add its repository URL and dependency with version

B. Install the library in your local Maven repository and add a dependency without version

C. Add the library jar directly to your project and reference it in pom.xml with system scope

D. Add the dependency with a fake groupId and artifactId to trick Maven

Solution

1. Step 1: Understand how Maven resolves dependencies

   Maven downloads dependencies from repositories defined in pom.xml or local repo.

2. Step 2: Identify best practice for custom libraries

   Uploading to a remote repository and adding its URL in pom.xml is clean and maintainable.

3. Step 3: Why other options are less ideal

   Local install requires manual setup; system scope is discouraged; fake IDs cause errors.

4. Final Answer:

   Upload the library to a remote repository and add its repository URL and dependency with version -> Option A

5. Quick Check:

   Use remote repo for custom libs [OK]

Hint: Use remote repo URLs for custom dependencies [OK]

Common Mistakes:

• Using system scope which is deprecated
• Skipping repository URL for custom libs
• Not specifying version for custom dependencies