OOP & Design Patterns - Decorator Pattern - Wrapping Behaviour Without Subclassing
To support undoing the last added decorator at runtime in a Decorator Pattern implementation, which design modification is most suitable?
To support undoing the last added decorator at runtime in a Decorator Pattern implementation, which design modification is most suitable?
hard🧠 Feature Understanding Q10 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand undo requirement
Undo means removing the last added decorator dynamically.Step 2: Identify suitable structure
A stack data structure naturally supports push/pop operations for decorators.Step 3: Evaluate options
Using inheritance or modifying base object breaks dynamic behavior; singleton is unrelated.Final Answer:
Option B -> Option BQuick Check:
Stack supports last-in-first-out removal [OK]
Quick Trick: Undo last decorator? Use stack to push/pop decorators [OK]
Common Mistakes:
MISTAKES- Trying to use subclassing which is static and inflexible.
- Modifying base object breaks open/closed principle.
- Singleton pattern unrelated to undoing decorators.
Trap Explanation:
PITFALL- Subclassing or modifying base object does not allow dynamic undo at runtime.
Interviewer Note:
CONTEXT- Tests understanding of dynamic decorator management and undo capability.
Master "Decorator Pattern - Wrapping Behaviour Without Subclassing" in OOP & Design Patterns
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore OOP & Design Patterns Quizzes