Question
When should a Java developer choose Interface vs Abstract Class deliberately?
- Choose Interface vs Abstract Class mainly when you want to postpone validation and fix problems manually later.
- Choose Interface vs Abstract Class whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Interface vs Abstract Class only to avoid modeling domain rules explicitly in Java code.
- Use interfaces for service boundaries, policies, and pluggable behavior across unrelated types.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Use interfaces for service boundaries, policies, and pluggable behavior across unrelated types.
Use interfaces for service boundaries, policies, and pluggable behavior across unrelated types. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java