Why DTOs matter in Spring Boot - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use DTOs in Spring Boot applications?

In a Spring Boot app, what is the main reason to use Data Transfer Objects (DTOs)?

A To separate the internal data model from what is exposed to clients, improving security and flexibility.

B To replace the database entities entirely and avoid using JPA repositories.

C To automatically generate database tables without writing SQL scripts.

D To speed up the application by caching all data in memory.

💡 Hint

Think about how you protect your private information when sharing only what is needed.

DTOs act like a filter between your database entities and the outside world. They help keep internal details private and allow you to change your database without breaking clients.

❓ component_behavior

intermediate

What happens if you return entities directly from a Spring Boot REST controller?

Consider a Spring Boot REST controller that returns JPA entities directly as JSON. What is a likely problem?

A The application will run faster because no extra mapping is needed.

B The database schema will automatically update to match the JSON structure.

C The REST controller will cache the entities and never refresh data.

D The JSON may expose sensitive fields and cause infinite recursion errors due to bidirectional relationships.

💡 Hint

Think about what happens when you share your full address book with everyone, including private notes.

Returning entities directly can expose sensitive data and cause serialization problems like infinite loops when entities reference each other.

❓ state_output

advanced

What is the output of this Spring Boot controller method using a DTO?

Given the following code snippet, what JSON will the client receive?

Spring Boot

public record UserEntity(Long id, String username, String password) {}

public record UserDTO(Long id, String username) {}

@GetMapping("/user/{id}")
public UserDTO getUser(@PathVariable Long id) {
    UserEntity user = userService.findById(id);
    return new UserDTO(user.id(), user.username());
}

A {"id":1,"username":"alice","password":"secret"}

B {"id":1,"username":"alice"}

C {"username":"alice"}

D {"id":1}

💡 Hint

Look at which fields the DTO includes compared to the entity.

The DTO only includes id and username, so the password is not sent to the client.

📝 Syntax

advanced

Which code snippet correctly maps an entity to a DTO in Spring Boot?

Choose the correct Java code that converts a UserEntity to a UserDTO.

A UserDTO dto = new UserDTO(userEntity.getId());

B UserDTO dto = new UserDTO(userEntity.id, userEntity.username, userEntity.password);

C UserDTO dto = new UserDTO(userEntity.getId(), userEntity.getUsername());

D UserDTO dto = new UserDTO(userEntity.getUsername());

💡 Hint

Remember the DTO only has id and username fields.

Option C correctly passes the two required fields. Options B, C, and D either pass wrong number of arguments or include password which DTO does not have.

🔧 Debug

expert

Why does this Spring Boot app throw a StackOverflowError when returning entities directly?

Given two JPA entities User and Address with bidirectional @OneToMany and @ManyToOne relationships, returning User directly from a REST controller causes a StackOverflowError. Why?

A Because the JSON serializer tries to serialize User, then Address, then User again endlessly due to circular references.

B Because the database connection is lost during serialization.

C Because the REST controller method is missing @ResponseBody annotation.

D Because the User entity has no default constructor.

💡 Hint

Think about what happens when you look in a mirror facing another mirror.

The circular references between User and Address cause the JSON serializer to recurse infinitely, leading to StackOverflowError.

Practice

1. Why do we use DTOs (Data Transfer Objects) in a Spring Boot application?

easy

A. To make the application slower by adding extra layers

B. To increase the size of data sent over the network

C. To replace the database entities completely

D. To carry only the data we want to share and hide internal details

Solution

1. Step 1: Understand the purpose of DTOs

   DTOs are designed to carry only the necessary data between processes or layers, avoiding exposure of internal details.

2. Step 2: Analyze the options

   To carry only the data we want to share and hide internal details correctly states the purpose of DTOs. The other options describe incorrect or harmful uses.

3. Final Answer:

   To carry only the data we want to share and hide internal details -> Option D

4. Quick Check:

   DTOs protect and simplify data transfer = D [OK]

Hint: DTOs share only needed data, hiding internals [OK]

Common Mistakes:

• Thinking DTOs replace entities fully
• Assuming DTOs increase data size
• Believing DTOs slow down the app

2. Which of the following is the correct way to define a simple DTO class in Spring Boot?

easy

A. public class UserDTO { private String name; private int age; public String getName() { return name; } public void setName(String name) { this.name = name; } public int getAge() { return age; } public void setAge(int age) { this.age = age; } }

B. @Entity public class UserDTO { private String name; private int age; }

C. public interface UserDTO { String getName(); int getAge(); }

D. @Repository public class UserDTO { private String name; private int age; }

Solution

1. Step 1: Identify correct DTO structure

   A DTO is a simple class with private fields and public getters/setters, without annotations like @Entity or @Repository.

2. Step 2: Evaluate each option

   public class UserDTO { private String name; private int age; public String getName() { return name; } public void setName(String name) { this.name = name; } public int getAge() { return age; } public void setAge(int age) { this.age = age; } } correctly defines a DTO class with fields and accessors. @Entity public class UserDTO { private String name; private int age; } wrongly uses @Entity, which is for database entities. public interface UserDTO { String getName(); int getAge(); } defines an interface, not a DTO class. @Repository public class UserDTO { private String name; private int age; } wrongly uses @Repository, which is for data access layers.

3. Final Answer:

   public class UserDTO { private String name; private int age; public String getName() { return name; } public void setName(String name) { this.name = name; } public int getAge() { return age; } public void setAge(int age) { this.age = age; } } -> Option A

4. Quick Check:

   DTO = simple class with getters/setters = B [OK]

Hint: DTOs are plain classes with getters/setters, no @Entity [OK]

Common Mistakes:

• Adding @Entity annotation to DTO
• Using interfaces instead of classes for DTO
• Marking DTO as @Repository

3. Given this Spring Boot controller method, what will be the output JSON when calling /user?

@GetMapping("/user")
public UserDTO getUser() {
    UserDTO dto = new UserDTO();
    dto.setName("Alice");
    dto.setAge(30);
    return dto;
}

medium

A. {"name":"Alice"}

B. {"UserDTO":{"name":"Alice","age":30}}

C. {"name":"Alice","age":30}

D. Error: Cannot serialize UserDTO

Solution

1. Step 1: Understand default JSON serialization in Spring Boot

   Spring Boot uses Jackson to convert returned objects to JSON, serializing all public getters by default.

2. Step 2: Analyze the returned UserDTO object

   UserDTO has name and age fields with getters, so JSON will include both as simple key-value pairs.

3. Final Answer:

   {"name":"Alice","age":30} -> Option C

4. Quick Check:

   DTO fields serialize as JSON keys = A [OK]

Hint: Returned DTO converts to JSON with all getters [OK]

Common Mistakes:

• Expecting nested JSON with class name
• Assuming partial fields serialize
• Thinking serialization causes error

4. What is wrong with this DTO class that causes a runtime error when Spring Boot tries to deserialize it?

public class ProductDTO {
    private String name;
    private int price;
    public ProductDTO(String name, int price) {
        this.name = name;
        this.price = price;
    }
}

medium

A. Fields should be public, not private

B. Missing default no-argument constructor

C. Constructor parameters should be annotated with @Autowired

D. Class should be annotated with @Entity

Solution

1. Step 1: Identify deserialization requirements

   Jackson requires a default no-argument constructor to create an instance before setting fields via setters or reflection.

2. Step 2: Check the DTO class

   This class only has a parameterized constructor and no default constructor, causing Jackson to fail during deserialization.

3. Final Answer:

   Missing default no-argument constructor -> Option B

4. Quick Check:

   Jackson needs no-arg constructor = A [OK]

Hint: DTOs need no-arg constructor for JSON serialization [OK]

Common Mistakes:

• Thinking fields must be public
• Adding @Autowired to constructor parameters
• Confusing DTO with entity needing @Entity

5. You have an entity class User with many fields, but you want to expose only id and email in your API response. How should you use a DTO to achieve this cleanly?

hard

A. Create a UserDTO with only id and email fields, map User to UserDTO before returning

B. Return the User entity directly and ignore unwanted fields in the frontend

C. Add @JsonIgnore to all unwanted fields in the User entity

D. Use the User entity but rename unwanted fields to empty strings

Solution

1. Step 1: Understand data exposure risks

   Returning the full User entity exposes all fields, risking sensitive data leaks.

2. Step 2: Use DTO to control data

   Creating a UserDTO with only id and email fields and mapping User to UserDTO ensures only desired data is sent.

3. Step 3: Evaluate other options

   Return the User entity directly and ignore unwanted fields in the frontend risks exposing all data. Add @JsonIgnore to all unwanted fields in the User entity mixes entity with serialization concerns and can be error-prone. Use the User entity but rename unwanted fields to empty strings is a bad practice and confusing.

4. Final Answer:

   Create a UserDTO with only id and email fields, map User to UserDTO before returning -> Option A

5. Quick Check:

   DTOs control exposed data = C [OK]

Hint: Use DTO to expose only needed fields safely [OK]

Common Mistakes:

• Returning full entity directly
• Using @JsonIgnore on entity fields
• Modifying entity fields to hide data