Bird
Raised Fist0

Which of the following statements about composition and inheritance is INCORRECT?

medium🐞 Bug Identification Q14 of Q15
OOP & Design Patterns - Composition vs Inheritance - Favour Composition, Why & When
Which of the following statements about composition and inheritance is INCORRECT?
AComposition leads to tighter coupling between classes than inheritance.
BInheritance models 'is-a' relationships, while composition models 'has-a' relationships.
CFavoring composition improves flexibility and maintainability of code.
DInheritance can cause fragile base class problems when base classes change.
Step-by-Step Solution

  1. Step 1: Analyze each statement

    Options A, C, and D are correct statements. Composition leads to tighter coupling between classes than inheritance. is incorrect because composition reduces coupling by separating concerns, whereas inheritance creates tighter coupling due to dependency on base classes.

  2. Final Answer:

    Option A -> Option A

  3. Quick Check:

    Composition reduces coupling; inheritance increases it.
Quick Trick: Composition reduces coupling; inheritance increases coupling.
Common Mistakes:
MISTAKES
  • Confusing which relationship leads to tighter coupling
  • Assuming composition increases coupling
Trap Explanation:
PITFALL
  • Candidates often mistakenly believe composition increases coupling because of object references, but inheritance creates stronger compile-time dependencies.
Interviewer Note:
CONTEXT
  • Tests ability to spot misconceptions about coupling in composition vs inheritance.
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