Question
When should a Java developer choose Abstraction deliberately?
- Choose Abstraction mainly when you want to postpone validation and fix problems manually later.
- Use abstraction when multiple implementations should satisfy the same business capability or service boundary.
- Choose Abstraction whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Abstraction 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 abstraction when multiple implementations should satisfy the same business capability or service boundary.
Use abstraction when multiple implementations should satisfy the same business capability or service boundary. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java