Spring Boot - Exception Handling
Why does Spring Boot prefer returning a 400 Bad Request status for validation errors instead of 422 Unprocessable Entity by default?
Why does Spring Boot prefer returning a 400 Bad Request status for validation errors instead of 422 Unprocessable Entity by default?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand HTTP status code semantics
400 Bad Request means the client sent invalid or malformed data, which fits validation failure.Step 2: Clarify 422 status meaning
422 Unprocessable Entity is valid but less commonly used; Spring Boot chooses 400 for simplicity and clarity.Final Answer:
Because 400 indicates client sent invalid data, matching validation failure semantics -> Option BQuick Check:
400 = client error for invalid input [OK]
Quick Trick: 400 means client sent bad data; 422 less common for validation [OK]
Common Mistakes:
- Thinking 422 is not standard
- Confusing 422 with server errors
- Believing 400 triggers retries
Master "Exception Handling" in Spring Boot
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Spring Boot Quizzes