[Solved] Consider two approaches to extending behavior: (1) Brute Force subclassing for every feature combination, and (2)... When is the Decorator Pattern approach better than brute force subclassing? | OOP & Design Patterns

OOP & Design Patterns - Decorator Pattern - Wrapping Behaviour Without Subclassing

Consider two approaches to extending behavior: (1) Brute Force subclassing for every feature combination, and (2) Decorator Pattern using composition. When is the Decorator Pattern approach better than brute force subclassing?

AWhen runtime performance is critical and must be O(1)

BWhen you need flexible, dynamic feature addition without subclass explosion

CWhen the number of feature combinations is small and fixed

DWhen inheritance hierarchies are preferred for clarity

Step-by-Step Solution

Solution:

Step 1: Compare approaches
Brute force creates many subclasses, Decorator composes features dynamically.
Step 2: Identify trade-offs
Decorator is better when features combine in many ways and must be added dynamically.
Final Answer:
Option B -> Option B
Quick Check:
Decorator avoids subclass explosion and supports runtime flexibility [OK]

Quick Trick: Decorator excels with many dynamic feature combinations [OK]

Common Mistakes:

MISTAKES

Assuming brute force is always faster
Preferring inheritance for dynamic behavior
Ignoring subclass explosion problem

Trap Explanation:

PITFALL

Candidates often overlook dynamic flexibility benefits of Decorator over subclassing.

Interviewer Note:

CONTEXT

Tests understanding of trade-offs between inheritance and composition.

Master "Decorator Pattern - Wrapping Behaviour Without Subclassing" in OOP & Design Patterns

2 interactive learning modes - each teaches the same concept differently

Solution Trace

More OOP & Design Patterns Quizzes

When is the Decorator Pattern approach better than brute force subclassing?

Step 1: Compare approaches

Step 2: Identify trade-offs

Final Answer:

Quick Check:

Want More Practice?