Question
When should a Java developer choose Comparable vs Comparator deliberately?
- Choose Comparable vs Comparator mainly when you want to postpone validation and fix problems manually later.
- Choose Comparable vs Comparator whenever you want the code to look more advanced, even if the design gets less clear.
- Use Comparator when different screens or workflows need different sort criteria for the same domain type.
- Choose Comparable vs Comparator 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: C. Use Comparator when different screens or workflows need different sort criteria for the same domain type.
Use Comparator when different screens or workflows need different sort criteria for the same domain type. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java