Question
When should a Java developer choose Optional deliberately?
- Use Optional when absence is expected and callers should deal with that absence explicitly at the call site.
- Choose Optional mainly when you want to postpone validation and fix problems manually later.
- Choose Optional whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Optional 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: A. Use Optional when absence is expected and callers should deal with that absence explicitly at the call site.
Use Optional when absence is expected and callers should deal with that absence explicitly at the call site. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java