Bird
Raised Fist0

You are designing a plugin system where plugins can be added or removed at runtime, each providing different behaviors to a core application. Which approach is better and why?

hard⚖️ Approach Comparison Q8 of Q15
OOP & Design Patterns - Composition vs Inheritance - Favour Composition, Why & When
You are designing a plugin system where plugins can be added or removed at runtime, each providing different behaviors to a core application. Which approach is better and why?
AComposition, because plugins can be composed dynamically with the core application.
BGlobal variables to track plugin states, because they centralize control.
CStatic methods in utility classes, because they simplify plugin invocation.
DInheritance, because plugins can subclass the core application to add behaviors.
Step-by-Step Solution
Solution:

  1. Step 1: Understand runtime behavior changes

    Plugins must be added/removed dynamically without recompilation.

  2. Step 2: Evaluate inheritance limitations

    Inheritance is static and fixed at compile time, unsuitable for dynamic plugins.

  3. Step 3: Composition supports dynamic behavior

    Composition allows attaching/detaching plugin objects at runtime, enabling flexibility.

  4. Step 4: Assess other options

    Static methods and global variables reduce modularity and encapsulation, increasing coupling.

  5. Final Answer:

    Option A -> Option A

  6. Quick Check:

    Composition supports dynamic plugin management better than inheritance [OK]
Quick Trick: Dynamic behavior favors composition over static inheritance [OK]
Common Mistakes:
MISTAKES
  • Assuming inheritance supports runtime behavior changes
  • Using global state instead of modular design
Trap Explanation:
PITFALL
  • Candidates often pick inheritance due to familiarity, ignoring dynamic flexibility needs.
Interviewer Note:
CONTEXT
  • Tests application of composition in dynamic, modular systems.
Master "Composition vs Inheritance - Favour Composition, Why & When" in OOP & Design Patterns

2 interactive learning modes - each teaches the same concept differently

SolutionTrace

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More OOP & Design Patterns Quizzes
Abstraction - Abstract Class vs Interface - When to Use Which - Abstraction - Abstract Class vs Interface - When to Use Which - Quiz 15hard Design a Library Management System - LLD with Relationships & Edge Cases - Design a Library Management System - LLD with Relationships & Edge Cases - Quiz 2easy Encapsulation - Data Hiding, Getters/Setters & Access Modifiers - Encapsulation - Data Hiding, Getters/Setters & Access Modifiers - Quiz 10hard Factory vs Abstract Factory vs Builder - When to Use Each - Factory vs Abstract Factory vs Builder - When to Use Each - Quiz 10hard Liskov Substitution Principle - Subtype Behavioural Contract - Liskov Substitution Principle - Subtype Behavioural Contract - Quiz 14medium Open/Closed Principle - Open for Extension, Closed for Modification - Open/Closed Principle - Open for Extension, Closed for Modification - Quiz 2easy Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Quiz 15hard Prototype Pattern - Deep Copy vs Shallow Copy - Prototype Pattern - Deep Copy vs Shallow Copy - Quiz 12easy Prototype Pattern - Deep Copy vs Shallow Copy - Prototype Pattern - Deep Copy vs Shallow Copy - Quiz 9hard Single Responsibility Principle - One Class, One Reason to Change - Single Responsibility Principle - One Class, One Reason to Change - Quiz 1easy