Bird
Raised Fist0

When choosing composition over inheritance in object-oriented design, which of the following is a common downside that developers should be aware of?

medium💡 Conceptual Thinking Q5 of Q15
OOP & Design Patterns - Composition vs Inheritance - Favour Composition, Why & When
When choosing composition over inheritance in object-oriented design, which of the following is a common downside that developers should be aware of?
ARigid class hierarchies that are hard to extend
BInability to reuse code across classes
CIncreased complexity in managing multiple collaborating objects
DTight coupling between parent and child classes
Step-by-Step Solution
Solution:

  1. Step 1: Understand composition trade-offs

    Composition increases flexibility but requires managing multiple objects collaborating.

  2. Step 2: Analyze options

    Options B, C, and D describe inheritance issues, not composition drawbacks.

  3. Final Answer:

    Option C -> Option C

  4. Quick Check:

    Composition trades hierarchy simplicity for object collaboration complexity [OK]
Quick Trick: Composition trades hierarchy for collaboration complexity [OK]
Common Mistakes:
MISTAKES
  • Confusing inheritance problems with composition drawbacks
  • Assuming composition eliminates all design complexity
  • Believing composition prevents code reuse
Trap Explanation:
PITFALL
  • Options B, C, D describe inheritance issues, not composition
Interviewer Note:
CONTEXT
  • Evaluates awareness of composition's complexity trade-offs
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