OOP & Design Patterns - Abstraction - Abstract Class vs Interface - When to Use Which
You want to provide some default behavior for subclasses but also require them to implement certain methods. Which abstraction pattern fits best?
You want to provide some default behavior for subclasses but also require them to implement certain methods. Which abstraction pattern fits best?
easy🔍 Pattern Recognition Q2 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand the need for partial implementation
Default behavior implies some methods have implementation, while others must be implemented by subclasses.Step 2: Evaluate options
Interfaces traditionally cannot have implementations (except default methods in some languages, but limited). Concrete classes do not enforce required methods. Multiple interfaces separate contracts but do not provide default behavior.Step 3: Abstract class fits best
Abstract classes allow partial implementation and enforce subclasses to implement abstract methods.Final Answer:
Option B -> Option BQuick Check:
Abstract class supports partial implementation and required methods [OK]
Quick Trick: Abstract classes allow partial implementation with enforced methods [OK]
Common Mistakes:
MISTAKES- Assuming interfaces can fully provide default behavior
- Thinking concrete classes enforce required methods
- Believing multiple interfaces can provide default implementations
Trap Explanation:
PITFALL- Candidates confuse interface default methods with abstract class partial implementation, missing enforcement nuances.
Interviewer Note:
CONTEXT- Checks understanding of partial implementation vs pure contracts.
Master "Abstraction - Abstract Class vs Interface - When to Use Which" in OOP & Design Patterns
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore OOP & Design Patterns Quizzes