DTO pattern for data transfer in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the main purpose of a DTO in Spring Boot?

In a Spring Boot application, why do developers use a Data Transfer Object (DTO)?

A To handle HTTP requests directly from the client

B To transfer data between layers without exposing the entity directly

C To store data permanently in the database

D To replace the service layer logic

💡 Hint

Think about how data is shared safely between parts of the app.

A DTO is used to safely transfer data between layers, like from the controller to the service, without exposing the full entity or database structure.

📝 Syntax

intermediate

Which DTO declaration is syntactically correct in Spring Boot?

Choose the correct way to declare a simple DTO class in Spring Boot.

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

B public class UserDTO { String name; getName() { return name; } setName(String name) { this.name = name; } }

C class UserDTO { private String name; public String getName() { return name; } public void setName(String name) { this.name = name; } }

D public UserDTO { private String name; public String getName() { return name; } public void setName(String name) { this.name = name; } }

💡 Hint

Remember Java class syntax requires access modifiers and method return types.

Option A correctly declares a public class with private field and public getter/setter methods with proper syntax.

❓ state_output

advanced

What will be the output of this DTO mapping code?

Given this code snippet in a Spring Boot service, what will be the value of userDTO.getEmail() after execution?

Spring Boot

User user = new User("Alice", "[e-mail]");
UserDTO userDTO = new UserDTO();
userDTO.setName(user.getName());
// Note: Email is not set in userDTO

String email = userDTO.getEmail();

A Throws NullPointerException

B "[e-mail]"

C Empty string ""

D null

💡 Hint

Check which fields are assigned values in the DTO.

The email field in userDTO was never set, so calling getEmail() returns null by default.

🔧 Debug

advanced

Why does this DTO cause a JSON serialization error?

Consider this DTO class used in a Spring Boot REST controller. Why does it cause a JSON serialization error?

Spring Boot

public class ProductDTO {
  private String name;
  private CategoryDTO category;
  // getters and setters
}

public class CategoryDTO {
  private String name;
  private ProductDTO product;
  // getters and setters
}

A Because of circular reference between ProductDTO and CategoryDTO causing infinite recursion

B Because fields are private without public getters and setters

C Because DTO classes must be annotated with @Entity

D Because JSON serialization requires fields to be static

💡 Hint

Think about what happens when JSON tries to convert linked objects referencing each other.

The circular reference between ProductDTO and CategoryDTO causes infinite recursion during JSON serialization, leading to an error.

🧠 Conceptual

expert

Which statement best describes the advantage of using DTOs in microservices?

In a microservices architecture, why is using DTOs beneficial when services communicate?

A DTOs allow direct database sharing between microservices

B DTOs automatically encrypt data between microservices for security

C DTOs reduce data transfer size by including only needed fields, improving performance and decoupling services

D DTOs replace the need for API gateways in microservices

💡 Hint

Consider how data is shared efficiently and safely between independent services.

DTOs help by sending only necessary data, reducing payload size and keeping services independent by not exposing internal entities.

Practice

1. What is the main purpose of using a DTO (Data Transfer Object) in a Spring Boot application?

easy

A. To manage application configuration settings

B. To store data permanently in the database

C. To handle user authentication and authorization

D. To safely transfer only necessary data between different parts of the application

Solution

1. Step 1: Understand the role of DTOs

   DTOs are simple objects designed to carry data between layers or parts of an application without exposing sensitive or unnecessary details.

2. Step 2: Identify the correct purpose

   Unlike entities or configuration classes, DTOs focus on safe and clean data transfer, not storage or security management.

3. Final Answer:

   To safely transfer only necessary data between different parts of the application -> Option D

4. Quick Check:

   DTO purpose = safe data transfer [OK]

Hint: DTOs move data safely without exposing all details [OK]

Common Mistakes:

• Confusing DTOs with database entities
• Thinking DTOs handle security
• Assuming DTOs store data permanently

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

easy

A. public record UserDTO(String name, String email) {}

B. public class UserDTO { private String name; private String email; }

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

D. public enum UserDTO { NAME, EMAIL }

Solution

1. Step 1: Recognize Java record syntax

   Java records provide a concise way to create immutable data carriers with automatic getters and constructors.

2. Step 2: Match the correct syntax

   public record UserDTO(String name, String email) {} uses the correct record declaration with fields inside parentheses and empty body braces.

3. Final Answer:

   public record UserDTO(String name, String email) {} -> Option A

4. Quick Check:

   Java record syntax = public record UserDTO(String name, String email) {} [OK]

Hint: Java records use 'record Name(fields) {}' syntax [OK]

Common Mistakes:

• Using class without constructors/getters
• Confusing interface with DTO class
• Using enum for data transfer

3. Given this Spring Boot code snippet, what will be the output when the getUserDTO() method is called?

public record UserDTO(String name, int age) {}

public UserDTO getUserDTO() {
    UserDTO user = new UserDTO("Alice", 30);
    return new UserDTO(user.name(), user.age() + 5);
}

medium

A. UserDTO[name=Alice, age=5]

B. UserDTO[name=Alice, age=35]

C. UserDTO[name=Alice, age=30]

D. Compilation error due to missing constructor

Solution

1. Step 1: Understand record instantiation and methods

   The record UserDTO has fields name and age with automatic accessor methods name() and age().

2. Step 2: Analyze the returned object

   The method creates a UserDTO with name "Alice" and age 30, then returns a new UserDTO with the same name and age increased by 5 (30 + 5 = 35).

3. Final Answer:

   UserDTO[name=Alice, age=35] -> Option B

4. Quick Check:

   Age incremented by 5 = 35 [OK]

Hint: Records have automatic getters like name() and age() [OK]

Common Mistakes:

• Forgetting to add 5 to age
• Confusing method calls with field access
• Assuming default toString format

4. Identify the error in this DTO usage code snippet:

public record ProductDTO(String name, double price) {}

public ProductDTO createProduct() {
    ProductDTO product = new ProductDTO("Book");
    return product;
}

medium

A. Missing second argument for price in ProductDTO constructor

B. Records cannot be used as DTOs

C. Method createProduct should return void

D. ProductDTO fields must be private

Solution

1. Step 1: Check record constructor parameters

   The ProductDTO record requires two parameters: a String name and a double price.

2. Step 2: Identify constructor call mistake

   The constructor call provides only one argument "Book", missing the price argument, causing a compile-time error.

3. Final Answer:

   Missing second argument for price in ProductDTO constructor -> Option A

4. Quick Check:

   Constructor args must match record fields [OK]

Hint: Record constructors need all fields in order [OK]

Common Mistakes:

• Passing fewer arguments than fields
• Thinking records can't be DTOs
• Ignoring method return types

5. You want to create a DTO that hides the user's password when sending data to the client. Given the entity:

public class User {
    private String username;
    private String password;
    private String email;
    // getters and setters
}

Which DTO definition best achieves this goal?

hard

A. public class UserDTO { private String password; }

B. public record UserDTO(String username, String password, String email) {}

C. public record UserDTO(String username, String email) {}

D. public record UserDTO(String password) {}

Solution

1. Step 1: Understand the goal to hide password

   The DTO should exclude the password field to avoid exposing it to clients.

2. Step 2: Choose DTO fields accordingly

   public record UserDTO(String username, String email) {} includes only username and email, omitting password, which meets the requirement.

3. Final Answer:

   public record UserDTO(String username, String email) {} -> Option C

4. Quick Check:

   Exclude sensitive fields in DTO [OK]

Hint: Exclude sensitive fields from DTO to hide them [OK]

Common Mistakes:

• Including password in DTO fields
• Using DTO with only password
• Confusing entity with DTO