Question
When should a Java developer choose Checked vs Unchecked Exceptions deliberately?
- Choose Checked vs Unchecked Exceptions mainly when you want to postpone validation and fix problems manually later.
- Use checked exceptions sparingly when the caller can make a meaningful recovery choice such as retrying, correcting input, or choosing another resource.
- Choose Checked vs Unchecked Exceptions whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Checked vs Unchecked Exceptions only to avoid modeling domain rules explicitly in Java code.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: B. Use checked exceptions sparingly when the caller can make a meaningful recovery choice such as retrying, correcting input, or choosing another resource.
Use checked exceptions sparingly when the caller can make a meaningful recovery choice such as retrying, correcting input, or choosing another resource. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java