OOP & Design Patterns - Abstraction - Abstract Class vs Interface - When to Use Which
When architecting a large system, what is the primary limitation of using abstract classes instead of interfaces in terms of system extensibility?
When architecting a large system, what is the primary limitation of using abstract classes instead of interfaces in terms of system extensibility?
medium💡 Conceptual Thinking Q5 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand abstract class constraints
Abstract classes support single inheritance only.Step 2: Impact on extensibility
Single inheritance limits ability to extend multiple behaviors, reducing flexibility.Final Answer:
Option B -> Option BQuick Check:
Abstract classes limit inheritance, interfaces allow multiple [OK]
Quick Trick: Abstract classes limit inheritance to one parent [OK]
Common Mistakes:
MISTAKES- Believing abstract classes cannot have implemented methods
- Confusing static method allowance with abstraction
- Assuming all methods must be implemented immediately
Trap Explanation:
PITFALL- Incorrectly thinking abstract classes cannot have implemented methods or static methods.
Interviewer Note:
CONTEXT- Evaluates knowledge of inheritance limitations affecting system design.
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