Bird
Raised Fist0

A developer believes that simply matching method signatures in a subclass guarantees LSP compliance. What is the fundamental misconception here?

medium🐞 Bug Identification Q7 of Q15
OOP & Design Patterns - Liskov Substitution Principle - Subtype Behavioural Contract
A developer believes that simply matching method signatures in a subclass guarantees LSP compliance. What is the fundamental misconception here?
ABelieving that private methods affect LSP substitutability.
BAssuming that method overloading is equivalent to overriding.
CIgnoring that behavioral contracts include preconditions, postconditions, and side effects beyond signatures.
DConfusing interface implementation with inheritance.
Step-by-Step Solution
Solution:

  1. Step 1: Clarify LSP requirements

    LSP requires behavioral substitutability, not just matching method signatures.

  2. Step 2: Analyze misconception

    A identifies the misconception that matching signatures alone suffice, ignoring behavioral contracts like pre/postconditions and side effects.

  3. Step 3: Evaluate other options

    B, C, and D are unrelated misconceptions about overloading, private methods, and interfaces.

  4. Final Answer:

    Option C -> Option C

  5. Quick Check:

    Behavioral contracts matter beyond method signatures [OK]
Quick Trick: LSP requires behavioral contracts, not just signatures [OK]
Common Mistakes:
MISTAKES
  • Equating signature matching with full substitutability
  • Ignoring side effects and conditions in LSP
Trap Explanation:
PITFALL
  • Candidates often focus on syntax rather than semantics of substitutability.
Interviewer Note:
CONTEXT
  • Reveals depth of understanding of behavioral contracts in LSP.
Master "Liskov Substitution Principle - Subtype Behavioural Contract" 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
Adapter vs Facade vs Proxy - Structural Pattern Comparison - Adapter vs Facade vs Proxy - Structural Pattern Comparison - Quiz 10hard Adapter vs Facade vs Proxy - Structural Pattern Comparison - Adapter vs Facade vs Proxy - Structural Pattern Comparison - Quiz 12easy Command Pattern - Undo/Redo, Request Queuing & Logging - Command Pattern - Undo/Redo, Request Queuing & Logging - Quiz 11easy Decorator Pattern - Wrapping Behaviour Without Subclassing - Decorator Pattern - Wrapping Behaviour Without Subclassing - Quiz 9hard Design a Library Management System - LLD with Relationships & Edge Cases - Design a Library Management System - LLD with Relationships & Edge Cases - Quiz 12easy Open/Closed Principle - Open for Extension, Closed for Modification - Open/Closed Principle - Open for Extension, Closed for Modification - Quiz 6medium Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Quiz 9hard Single Responsibility Principle - One Class, One Reason to Change - Single Responsibility Principle - One Class, One Reason to Change - Quiz 2easy Template Method Pattern - Define Skeleton, Override Steps - Template Method Pattern - Define Skeleton, Override Steps - Quiz 4medium Template Method Pattern - Define Skeleton, Override Steps - Template Method Pattern - Define Skeleton, Override Steps - Quiz 13medium