[Solved] In a large-scale system where behaviors need to be dynamically changed at runtime, what is a key design consideration when using composition to avoid pitfalls that inheritance-based designs face? | OOP & Design Patterns

OOP & Design Patterns - Composition vs Inheritance - Favour Composition, Why & When

In a large-scale system where behaviors need to be dynamically changed at runtime, what is a key design consideration when using composition to avoid pitfalls that inheritance-based designs face?

AUse deep inheritance hierarchies to capture all behavior variations upfront.

BEnsure that composed behavior objects are immutable to prevent side effects.

CAvoid using interfaces and rely on concrete classes to reduce complexity.

DDesign behavior interfaces and use delegation so behaviors can be swapped without modifying the main object.

Step-by-Step Solution

Step 1: Understand dynamic behavior change
To change behaviors at runtime, the design must support swapping behavior implementations easily.
Step 2: Analyze options
Ensure that composed behavior objects are immutable to prevent side effects. is not practical; immutability limits dynamic changes. Avoid using interfaces and rely on concrete classes to reduce complexity. increases coupling and reduces flexibility. Use deep inheritance hierarchies to capture all behavior variations upfront. contradicts favoring composition and leads to rigid designs.
Step 3: Confirm best practice
Design behavior interfaces and use delegation so behaviors can be swapped without modifying the main object. promotes defining behavior interfaces and delegating calls, enabling runtime swapping without modifying main objects.
Final Answer:
Option D -> Option D
Quick Check:
Delegation with interfaces is key to flexible, dynamic composition.

Quick Trick: Use interfaces and delegation to swap behaviors dynamically, not inheritance or concrete classes.

Common Mistakes:

MISTAKES

Thinking immutability aids dynamic behavior changes
Relying on inheritance for runtime flexibility

Trap Explanation:

PITFALL

Candidates often confuse immutability with flexibility or think inheritance can handle dynamic behavior changes well.

Interviewer Note:

CONTEXT

Tests deep understanding of composition design for runtime flexibility beyond static inheritance.

Master "Composition vs Inheritance - Favour Composition, Why & When" in OOP & Design Patterns

2 interactive learning modes - each teaches the same concept differently

Solution Trace

More OOP & Design Patterns Quizzes

In a large-scale system where behaviors need to be dynamically changed at runtime, what is a key design consideration when using composition to avoid pitfalls that inheritance-based designs face?

Step 1: Understand dynamic behavior change

Step 2: Analyze options

Step 3: Confirm best practice

Final Answer:

Quick Check:

Want More Practice?