Why JPA matters for database access in Spring Boot - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use JPA instead of plain SQL in Spring Boot?

Which of the following best explains why JPA is preferred over writing plain SQL queries directly in Spring Boot applications?

A JPA only works with NoSQL databases, so it is not suitable for relational databases.

B JPA requires writing more SQL queries manually, giving developers full control over database access.

C JPA disables transaction management, making database operations faster but less safe.

D JPA automatically maps Java objects to database tables, reducing boilerplate code and improving maintainability.

💡 Hint

Think about how JPA helps connect Java code with database tables.

JPA helps by automatically linking Java objects to database tables. This means developers write less SQL and focus more on Java code, making the app easier to maintain.

❓ component_behavior

intermediate

JPA Entity Behavior in Spring Boot

Given a JPA entity with a field annotated as @Id and @GeneratedValue, what happens when you save a new entity instance using a Spring Data JPA repository?

Spring Boot

import jakarta.persistence.*;

@Entity
public class Product {
  @Id
  @GeneratedValue(strategy = GenerationType.IDENTITY)
  private Long id;
  private String name;

  // getters and setters
}

// In a Spring Boot service:
Product p = new Product();
p.setName("Book");
productRepository.save(p);

Long savedId = p.getId();

A The id field remains null because JPA does not generate IDs automatically.

B The id field is automatically assigned a unique value by the database after saving.

C An exception is thrown because the id field must be set manually before saving.

D The id field is set to zero by default after saving.

💡 Hint

Consider what @GeneratedValue does in JPA.

The @GeneratedValue annotation tells JPA to let the database generate a unique ID when the entity is saved. After saving, the entity's id field is updated with this value.

📝 Syntax

advanced

Correct JPQL Query Syntax in Spring Data JPA

Which of the following JPQL queries correctly selects all users with the last name 'Smith' using Spring Data JPA?

Spring Boot

public interface UserRepository extends JpaRepository<User, Long> {
  @Query("?1")
  List<User> findByLastName();
}

A "SELECT u FROM User u WHERE u.lastName = 'Smith'"

B "SELECT * FROM users WHERE lastName = 'Smith'"

C "FROM User WHERE lastName = 'Smith'"

D "SELECT u FROM User u WHERE lastName = 'Smith'"

💡 Hint

JPQL uses entity names and fields, not table names or *.

JPQL queries use entity class names and their fields. Option A correctly uses 'SELECT u FROM User u WHERE u.lastName = 'Smith''.

❓ state_output

advanced

Effect of Transactional Annotation on JPA Repository Save

In a Spring Boot service method annotated with @Transactional, what happens if an exception is thrown after saving an entity with a JPA repository?

Spring Boot

@Service
public class UserService {
  @Autowired
  private UserRepository userRepository;

  @Transactional
  public void createUser(String name) {
    User user = new User();
    user.setName(name);
    userRepository.save(user);
    if (true) {
      throw new RuntimeException("Fail");
    }
  }
}

A The save operation is rolled back, so the user is not saved in the database.

B The user is saved despite the exception because save() commits immediately.

C The exception is ignored and the transaction commits normally.

D The database connection is closed but the user is saved.

💡 Hint

Think about what @Transactional does when exceptions occur.

The @Transactional annotation rolls back the entire transaction if a RuntimeException occurs, so the save is undone.

🔧 Debug

expert

Diagnosing LazyInitializationException in JPA

A Spring Boot application using JPA throws a LazyInitializationException when accessing a collection property of an entity outside a transaction. Which option best explains why this happens?

A The entity class is missing the @Entity annotation, so JPA does not manage it.

B The entity was saved without an ID, causing the collection to be null.

C The collection was not fetched eagerly and the session is closed when accessed, so JPA cannot load it lazily.

D The database connection was lost, so JPA cannot fetch any data.

💡 Hint

LazyInitializationException usually relates to session and fetching strategy.

LazyInitializationException occurs when JPA tries to load a lazy collection but the session (transaction) is closed. The collection was not loaded eagerly, so it cannot be accessed outside the transaction.

Practice

1.

Why is JPA important when working with databases in Spring Boot?

easy

A. It requires you to write all SQL queries manually.

B. It lets you work with database data as Java objects instead of SQL.

C. It only works with NoSQL databases.

D. It replaces the need for a database entirely.

Solution

1. Step 1: Understand JPA's role in database access

   JPA maps database tables to Java objects, so you can use Java code to handle data instead of SQL.

2. Step 2: Compare options to JPA's purpose

   JPA does not require manual SQL for all queries (many are auto-generated), works primarily with relational databases, and does not eliminate the need for a database.

3. Final Answer:

   It lets you work with database data as Java objects instead of SQL. -> Option B

4. Quick Check:

   JPA = Java objects for database [OK]

Hint: JPA means Java objects, not raw SQL [OK]

Common Mistakes:

• Thinking JPA eliminates the database
• Believing JPA only works with NoSQL
• Assuming you must write all SQL manually

2.

Which of the following is the correct way to declare a JPA entity class in Spring Boot?

?

easy

A. @Entity public class User { private Long id; private String name; }

B. public class User { @Entity private Long id; private String name; }

C. @Table public class User { private Long id; private String name; }

D. @Entity public interface User { Long getId(); String getName(); }

Solution

1. Step 1: Identify correct JPA entity annotation usage

   The @Entity annotation must be placed on the class to mark it as a JPA entity.

2. Step 2: Check class structure

   @Entity public class User { private Long id; private String name; } correctly uses @Entity on a class with fields. public class User { @Entity private Long id; private String name; } misplaces @Entity on a field, @Table is for table naming rather than marking an entity, and an interface is not valid for JPA entities.

3. Final Answer:

   @Entity public class User { private Long id; private String name; } -> Option A

4. Quick Check:

   @Entity on class = correct entity [OK]

Hint: @Entity goes on class, not fields or interfaces [OK]

Common Mistakes:

• Putting @Entity on fields instead of class
• Using interface instead of class for entity
• Confusing @Entity with @Table annotation

3.

Given this Spring Data JPA repository interface:

public interface UserRepository extends JpaRepository<User, Long> {}

What happens when you call userRepository.findAll()?

medium

A. It returns null because no query is written.

B. It throws a compile-time error because findAll() is not defined.

C. It deletes all User records from the database.

D. It returns a list of all User objects from the database.

Solution

1. Step 1: Understand JpaRepository methods

   JpaRepository provides built-in methods like findAll() that return all records as Java objects.

2. Step 2: Analyze the method call

   Calling findAll() returns a list of all User entities from the database, no error or deletion occurs.

3. Final Answer:

   It returns a list of all User objects from the database. -> Option D

4. Quick Check:

   findAll() = list of all entities [OK]

Hint: JpaRepository has findAll() ready to use [OK]

Common Mistakes:

• Thinking findAll() needs manual query
• Confusing findAll() with delete methods
• Expecting null instead of empty list

4.

What is wrong with this JPA entity code snippet?

@Entity
public class Product {
  @Id
  private Long id;
  private String name;

  public Product(String name) {
    this.name = name;
  }
}

medium

A. The class should be abstract to be a JPA entity.

B. The @Id annotation should be on the class, not the field.

C. Missing no-argument constructor required by JPA.

D. The field 'name' must be annotated with @Column.

Solution

1. Step 1: Recall JPA entity constructor rules

   JPA requires a public or protected no-argument constructor to create entity instances.

2. Step 2: Check the provided constructors

   The class only has a constructor with a parameter, so the no-argument constructor is missing.

3. Final Answer:

   Missing no-argument constructor required by JPA. -> Option C

4. Quick Check:

   No-arg constructor needed for JPA [OK]

Hint: Always add a no-arg constructor for JPA entities [OK]

Common Mistakes:

• Thinking @Id goes on class
• Believing @Column is mandatory for all fields
• Assuming abstract class is needed

5.

You want to fetch all users whose name starts with 'A' using Spring Data JPA. Which repository method signature should you add?

hard

A. List<User> findByNameStartingWith(String prefix);

B. List<User> findAllByNameContains(String prefix);

C. List<User> findUsersByNameLike(String prefix);

D. List<User> getUsersWhereNameStartsWith(String prefix);

Solution

1. Step 1: Understand Spring Data JPA query method naming

   Spring Data JPA supports method names like findByNameStartingWith to generate queries automatically.

2. Step 2: Evaluate method signatures

   List<User> findByNameStartingWith(String prefix); uses the correct 'findByNameStartingWith' pattern. List<User> findAllByNameContains(String prefix); uses 'Contains' which matches anywhere, 'Like' is not a valid method keyword, and getUsersWhereNameStartsWith uses an invalid naming pattern.

3. Final Answer:

   List<User> findByNameStartingWith(String prefix); -> Option A

4. Quick Check:

   Method name pattern = findByNameStartingWith [OK]

Hint: Use 'findByNameStartingWith' for prefix queries [OK]

Common Mistakes:

• Using invalid method names not supported by Spring Data
• Confusing 'Contains' with 'StartingWith'
• Trying to write custom queries instead of method names