Rest API - HTTP Status Codes
In a REST API, a client sends a request with a field 'age' set to -5. The server responds with status 422. What is the likely cause?
In a REST API, a client sends a request with a field 'age' set to -5. The server responds with status 422. What is the likely cause?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand semantic validation
Negative age is invalid logically, so the server rejects it with 422 indicating semantic error.Step 2: Eliminate other options
Field is present, so not missing; server supports field; authorization unrelated to 422.Final Answer:
The 'age' value is semantically invalid despite correct syntax -> Option BQuick Check:
Invalid field value triggers 422 semantic error [OK]
Quick Trick: 422 means data invalid, not missing or unauthorized [OK]
Common Mistakes:
- Thinking 422 means missing field
- Confusing 422 with 403 Forbidden
- Assuming server error instead of validation error
Master "HTTP Status Codes" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes