DTO vs entity separation benefit in Spring Boot - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a simple DTO class field.

Spring Boot

private [1] name;

Drag options to blanks, or click blank then click option'

Aint

BString

CEntity

DList

Attempts:

3 left

💡 Hint

Common Mistakes

Using entity class type instead of simple data type.

Using numeric types for text fields.

The DTO field for a name is typically a String to hold text data.

2fill in blank

medium

Complete the code to convert an entity to a DTO in a method.

Spring Boot

return new UserDTO(entity.get[1]());

Drag options to blanks, or click blank then click option'

AId

BList

CDate

DName

Attempts:

3 left

💡 Hint

Common Mistakes

Using getId() when the DTO expects a name.

Using unrelated getters like getDate().

The method getName() retrieves the name from the entity to pass to the DTO.

3fill in blank

hard

Fix the error in the DTO constructor parameter type.

Spring Boot

public UserDTO([1] name) { this.name = name; }

Drag options to blanks, or click blank then click option'

AString

BEntity

Cint

DObject

Attempts:

3 left

💡 Hint

Common Mistakes

Using Entity type instead of String.

Using generic Object type.

The constructor should accept a String for the name, not an Entity or other type.

4fill in blank

hard

Fill both blanks to map entity fields to DTO fields correctly.

Spring Boot

dto.setName(entity.get[1]());
dto.setEmail(entity.get[2]());

Drag options to blanks, or click blank then click option'

AName

BEmail

CId

DDate

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up field names like using getId() instead of getEmail().

Using setters with wrong getter calls.

Mapping entity's getName() and getEmail() to DTO fields ensures data separation.

5fill in blank

hard

Fill all three blanks to create a DTO from entity fields with proper types.

Spring Boot

public record UserDTO([1] name, [2] email, [3] age) {}

Drag options to blanks, or click blank then click option'

AString

Bint

Dlong

Attempts:

3 left

💡 Hint

Common Mistakes

Using long for age when int is sufficient.

Mixing types between name and email.

UserDTO uses String for name and email, and int for age to keep simple data types.

Practice

1. Why is it beneficial to separate DTOs from entities in a Spring Boot application?

easy

A. It allows direct modification of database tables from the UI.

B. It makes the application run faster by skipping database calls.

C. It keeps the database structure hidden and improves security.

D. It reduces the number of classes in the project.

Solution

1. Step 1: Understand the role of entities

   Entities represent the database structure and are tightly linked to how data is stored.

2. Step 2: Understand the role of DTOs

   DTOs are used to transfer data safely between layers or systems, hiding internal details.

3. Final Answer:

   It keeps the database structure hidden and improves security. -> Option C

4. Quick Check:

   DTOs separate data transfer from entities = A [OK]

Hint: DTOs hide database details from outside layers [OK]

Common Mistakes:

• Thinking DTOs speed up database calls
• Believing entities should be exposed directly
• Confusing DTOs with database tables

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

easy

A. public class UserDTO { private String name; public String getName() { return name; } }

B. public record UserDTO(String name) {}

C. public enum UserDTO { NAME; }

D. public interface UserDTO { String name; }

Solution

1. Step 1: Review DTO class options

   DTOs are simple data carriers. Java records provide a concise way to define immutable DTOs.

2. Step 2: Identify the correct syntax

   public record UserDTO(String name) {} uses a record, which is modern and recommended for DTOs in Java 17+.

3. Final Answer:

   public record UserDTO(String name) {} -> Option B

4. Quick Check:

   Use records for simple DTOs = D [OK]

Hint: Use Java records for simple DTOs in Spring Boot [OK]

Common Mistakes:

• Using interfaces without methods for DTOs
• Using enums instead of classes or records
• Not providing getters for DTO fields

3. Given this code snippet, what will be the output when converting an entity to a DTO?

record UserDTO(String name) {}
class UserEntity { String name; UserEntity(String name) { this.name = name; } }

UserEntity entity = new UserEntity("Alice");
UserDTO dto = new UserDTO(entity.name);
System.out.println(dto.name());

medium

A. Alice

B. null

C. Compilation error

D. Empty string

Solution

1. Step 1: Understand entity to DTO conversion

   The entity has a name "Alice" which is passed to the DTO constructor.

2. Step 2: Check the output of dto.name()

   Since dto stores "Alice", printing dto.name() outputs "Alice".

3. Final Answer:

   Alice -> Option A

4. Quick Check:

   Entity name passed to DTO = Alice [OK]

Hint: DTO fields hold entity data passed in constructor [OK]

Common Mistakes:

• Assuming dto.name() returns null
• Confusing record syntax causing errors
• Expecting entity and DTO to be the same object

4. Identify the problem in this code snippet that mixes entity and DTO responsibilities:

public class UserEntity {
  private String name;
  public String getName() { return name; }
  public void setName(String name) { this.name = name; }
  public String toJson() { return "{\"name\":\"" + name + "\"}"; }
}

medium

A. The toJson method should return XML instead.

B. Getter and setter methods are missing.

C. The name field should be public.

D. Entity class should not handle JSON formatting.

Solution

1. Step 1: Analyze entity responsibilities

   Entities should focus on data storage and mapping, not formatting or presentation.

2. Step 2: Identify separation violation

   toJson mixes data with presentation logic, which belongs in DTO or service layers.

3. Final Answer:

   Entity class should not handle JSON formatting. -> Option D

4. Quick Check:

   Keep entity and presentation separate = A [OK]

Hint: Entities store data; DTOs handle data format [OK]

Common Mistakes:

• Allowing entities to format output
• Making entity fields public
• Confusing DTO and entity roles

5. You have a UserEntity with sensitive fields like password and internal IDs. How does using a separate UserDTO improve your Spring Boot API's security and maintainability?

hard

A. By exposing only necessary fields and hiding sensitive data from API responses.

B. By allowing direct database updates from the API without validation.

C. By merging all entity fields into one large DTO for simplicity.

D. By removing the need for service layers in the application.

Solution

1. Step 1: Recognize sensitive data risks

   Entities contain all data, including sensitive info like passwords, which should not be exposed.

2. Step 2: Understand DTO role in security

   DTOs can include only safe fields, preventing accidental exposure in API responses.

3. Step 3: Consider maintainability benefits

   Separating DTOs allows easier changes to API without affecting database structure.

4. Final Answer:

   By exposing only necessary fields and hiding sensitive data from API responses. -> Option A

5. Quick Check:

   DTOs protect sensitive data and ease maintenance = B [OK]

Hint: DTOs hide sensitive entity fields from API output [OK]

Common Mistakes:

• Exposing all entity fields directly
• Skipping validation by merging DTO and entity
• Removing service layers causing tight coupling