Why DTO validation in Spring Boot? - Purpose & Use Cases

The Big Idea

What if your app could catch bad data before it even reaches your code?

The Scenario

Imagine building a web app where users submit forms with their data. You manually check every field in your code to see if it's correct, like making sure emails look right or numbers are positive.

The Problem

Manually checking each input is slow and easy to forget. If you miss a check, bad data sneaks in, causing bugs or crashes. It's like proofreading a long letter without spellcheck--tiring and error-prone.

The Solution

DTO validation lets you declare rules for your data in one place. The framework automatically checks inputs before your app uses them, catching errors early and keeping your code clean and safe.

Before vs After

✗ Before

if(email == null || !email.contains("@")) { throw new Exception("Invalid email"); }

✓ After

@Email
private String email;

What It Enables

It makes your app trust user data confidently and reduces bugs by automating input checks.

Real Life Example

When a user signs up, DTO validation ensures their email and password meet rules before saving, preventing invalid accounts.

Key Takeaways

Manual input checks are slow and risky.

DTO validation automates and centralizes data rules.

This keeps apps safer and code simpler.

Practice

1. What is the main purpose of using DTO validation in a Spring Boot application?

easy

A. To handle user authentication and login

B. To speed up database queries automatically

C. To generate HTML pages from data

D. To check and ensure input data meets rules before processing

Solution

1. Step 1: Understand DTO role

   A DTO (Data Transfer Object) carries data between processes and needs validation to ensure data is correct.

2. Step 2: Purpose of validation

   Validation checks input data early to prevent bad data from reaching business logic or database.

3. Final Answer:

   To check and ensure input data meets rules before processing -> Option D

4. Quick Check:

   DTO validation = input data check [OK]

Hint: Validation means checking input data early [OK]

Common Mistakes:

• Confusing validation with database optimization
• Thinking validation generates UI
• Mixing validation with authentication

2. Which annotation is used on a DTO field to require that it must not be empty or null?

easy

A. @Size(min = 1)

B. @NotEmpty

C. @NotNull

D. @Valid

Solution

1. Step 1: Understand annotations meaning

   @NotNull only checks for null, but allows empty strings. @NotEmpty checks for both null and empty strings.

2. Step 2: Choose correct annotation

   To ensure a field is neither null nor empty, @NotEmpty is the best choice.

3. Final Answer:

   @NotEmpty -> Option B

4. Quick Check:

   @NotEmpty = no null or empty [OK]

Hint: Use @NotEmpty to block null and empty strings [OK]

Common Mistakes:

• Using @NotNull but allowing empty strings
• Confusing @Valid with field validation
• Using @Size without min value

3. Given this DTO class snippet:

public class UserDTO {
  @NotNull
  private String username;

  @Min(18)
  private int age;

  // getters and setters
}

What happens if a request sends username=null and age=16 when validated with @Valid?

medium

A. Validation fails for both username and age fields

B. Validation passes because age is int and can't be null

C. Validation fails only for age field

D. Validation passes because @NotNull is ignored on String

Solution

1. Step 1: Check username validation

   @NotNull on username means null value is invalid, so username=null fails validation.

2. Step 2: Check age validation

   @Min(18) means age must be at least 18. Given age=16, this fails validation.

3. Final Answer:

   Validation fails for both username and age fields -> Option A

4. Quick Check:

   @NotNull + @Min(18) fail for null and age 16 [OK]

Hint: Check each annotation rule against input values [OK]

Common Mistakes:

• Assuming int fields can't fail validation
• Ignoring @NotNull effect on String
• Thinking validation passes if one field is valid

4. Identify the error in this controller method for validating a DTO:

@PostMapping("/users")
public ResponseEntity<String> addUser(UserDTO user) {
  // save user
  return ResponseEntity.ok("User added");
}

medium

A. Missing @Validated annotation on controller class

B. Method should return void instead of ResponseEntity

C. Missing @RequestBody annotation on UserDTO parameter

D. No error, code is correct

Solution

1. Step 1: Check parameter annotations

   To validate JSON input as DTO, @RequestBody is needed to bind request body to UserDTO.

2. Step 2: Check validation annotation

   @Valid is also needed to trigger validation, but missing @RequestBody causes binding failure first.

3. Final Answer:

   Missing @RequestBody annotation on UserDTO parameter -> Option C

4. Quick Check:

   @RequestBody needed for JSON binding [OK]

Hint: Use @RequestBody to bind JSON to DTO [OK]

Common Mistakes:

• Forgetting @RequestBody causes no binding
• Thinking @Valid alone binds JSON
• Assuming return type must be void

5. You want to validate a DTO with a nested object, where the nested object also needs validation. Which is the correct way to enable validation on the nested DTO field?

hard

A. Add @Valid annotation on the nested DTO field inside the parent DTO

B. Add @NotNull on the nested DTO field only

C. Add @Valid on the parent DTO class only

D. No annotation needed, nested DTOs are validated automatically

Solution

1. Step 1: Understand nested validation

   Spring Boot requires @Valid on nested DTO fields to trigger validation of inner objects.

2. Step 2: Why @Valid on nested field

   @NotNull only checks presence, but @Valid triggers validation of nested object's fields.

3. Final Answer:

   Add @Valid annotation on the nested DTO field inside the parent DTO -> Option A

4. Quick Check:

   @Valid on nested field triggers inner validation [OK]

Hint: Use @Valid on nested DTO fields for full validation [OK]

Common Mistakes:

• Using only @NotNull on nested DTO
• Assuming parent @Valid covers nested fields
• Skipping @Valid and expecting automatic nested validation