Validation error response formatting in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Spring Boot validation error handler?

Given this controller advice method handling validation errors, what JSON response will it produce when a field "username" is empty?

@ExceptionHandler(MethodArgumentNotValidException.class)
@ResponseStatus(HttpStatus.BAD_REQUEST)
public Map handleValidationExceptions(MethodArgumentNotValidException ex) {
  Map errors = new HashMap<>();
  ex.getBindingResult().getAllErrors().forEach(error -> {
    String fieldName = ((FieldError) error).getField();
    String errorMessage = error.getDefaultMessage();
    errors.put(fieldName, errorMessage);
  });
  return errors;
}

A {"username": "must not be empty"}

B {"error": "Validation failed"}

C {"username": ""}

D {"message": "Field error"}

💡 Hint

Look at how the errors map is built from field names and messages.

The method collects all field errors and maps each field name to its error message. For an empty username, the message is typically "must not be empty".

📝 Syntax

intermediate

Which option correctly formats a validation error response with a timestamp?

You want to include a timestamp and error details in your validation error response. Which code snippet correctly creates a JSON response with keys "timestamp" and "errors"?

A

Map<String, Object> body = new HashMap<>();
body.put("timestamp", LocalDateTime.now());
body.put("errors", errorsList);
return ResponseEntity.badRequest().body(body);

B

Map<String, Object> body = new HashMap<>();
body.put(timestamp, LocalDateTime.now());
body.put(errors, errorsList);
return ResponseEntity.badRequest().body(body);

C

Map<String, String> body = new HashMap<>();
body.put("timestamp", LocalDateTime.now().toString());
body.put("errors", errorsList.toString());
return ResponseEntity.ok().body(body);

D

Map body = new HashMap();
body.put("timestamp", LocalDateTime.now());
body.put("errors", errorsList);
return ResponseEntity.badRequest().body(body);

💡 Hint

Check for correct key quoting and response status.

Option A uses quoted keys, correct types, and returns a 400 Bad Request with the body map. Option A misses quotes causing compile errors. Option A returns 200 OK and uses string conversions which is less ideal. Option A uses raw types which is discouraged.

🔧 Debug

advanced

Why does this validation error handler cause a ClassCastException?

Consider this code snippet:

@ExceptionHandler(MethodArgumentNotValidException.class)
public Map handleErrors(MethodArgumentNotValidException ex) {
  Map errors = new HashMap<>();
  for (Object error : ex.getBindingResult().getAllErrors()) {
    String field = ((FieldError) error).getField();
    String message = error.getDefaultMessage();
    errors.put(field, message);
  }
  return errors;
}

What is the most likely cause of a ClassCastException here?

A The error.getDefaultMessage() returns null causing NullPointerException.

B The map is declared with wrong generic types causing casting issues.

C Some errors in getAllErrors() are not FieldError instances, so casting fails.

D The exception handler method lacks @ResponseStatus annotation causing runtime error.

💡 Hint

Not all errors are field errors in validation results.

getAllErrors() returns ObjectError instances, some of which may not be FieldError. Casting all to FieldError causes ClassCastException.

❓ state_output

advanced

What is the JSON output of this custom validation error response?

Given this code snippet in a Spring Boot controller advice:

@ExceptionHandler(MethodArgumentNotValidException.class)
@ResponseStatus(HttpStatus.BAD_REQUEST)
public Map handleValidationErrors(MethodArgumentNotValidException ex) {
  List errors = ex.getBindingResult().getFieldErrors().stream()
    .map(err -> err.getField() + ": " + err.getDefaultMessage())
    .toList();
  Map response = new HashMap<>();
  response.put("status", 400);
  response.put("errors", errors);
  return response;
}

What will the JSON response look like if the "email" field is invalid with message "must be a valid email"?

A {"status":400,"error":"email must be a valid email"}

B {"status":400,"errors":{"email":"must be a valid email"}}

C {"status":"400","errors":["email must be a valid email"]}

D {"status":400,"errors":["email: must be a valid email"]}

💡 Hint

Look at how errors list is built with field and message concatenated with colon.

The errors list contains strings like "field: message". The status is an integer 400. So the JSON has a numeric status and an array of error strings.

🧠 Conceptual

expert

Which approach best supports internationalized validation error responses in Spring Boot?

You want your validation error messages to appear in the user's language automatically. Which approach below best supports this in Spring Boot?

A Hardcode error messages in English inside the exception handler and translate manually before sending response.

B Use MessageSource with locale resolver and call messageSource.getMessage() inside the exception handler to get localized messages.

C Use @ResponseStatus with fixed messages on exception classes without localization support.

D Return raw default messages from validation annotations without any localization logic.

💡 Hint

Spring Boot supports message localization via MessageSource and locale resolvers.

Using MessageSource with locale resolver allows fetching messages in the user's language dynamically. Hardcoding or ignoring localization does not support internationalization.