Question
When should a Java developer choose Inheritance vs Composition deliberately?
- Choose Inheritance vs Composition mainly when you want to postpone validation and fix problems manually later.
- Choose Inheritance vs Composition whenever you want the code to look more advanced, even if the design gets less clear.
- Prefer composition when behavior should vary independently of the concrete type identity.
- Choose Inheritance vs Composition 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. Prefer composition when behavior should vary independently of the concrete type identity.
Prefer composition when behavior should vary independently of the concrete type identity. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java