Bird
Raised Fist0

What is a key trade-off when using the Singleton pattern for managing the ParkingLot instance in a multi-level parking system?

medium🪤 Complexity Trap Q13 of Q15
OOP & Design Patterns - Design a Parking Lot - LLD with OOP (Classes, Patterns, Extensibility)
What is a key trade-off when using the Singleton pattern for managing the ParkingLot instance in a multi-level parking system?
ASingleton pattern automatically handles persistence of ParkingLot state across system restarts
BSingleton ensures only one ParkingLot instance, which simplifies global access but limits scalability for multiple lots
CSingleton improves concurrency by allowing multiple threads to create instances simultaneously
DSingleton eliminates the need for synchronization in multi-threaded environments
Step-by-Step Solution

  1. Step 1: Understand Singleton purpose

    Singleton restricts instantiation to one object, providing a global point of access.

  2. Step 2: Identify trade-offs

    While simplifying access, it limits flexibility and scalability, especially if multiple parking lots or levels need independent management.

  3. Step 3: Address misconceptions

    Singleton does not inherently improve concurrency or persistence, nor does it remove synchronization needs.

  4. Final Answer:

    Option B -> Option B

  5. Quick Check:

    Singleton simplifies access but restricts scalability [OK]
Quick Trick: Singleton = one instance, good for global access but bad for scalability [OK]
Common Mistakes:
MISTAKES
  • Believing Singleton improves concurrency or persistence
  • Assuming Singleton removes synchronization requirements
Trap Explanation:
PITFALL
  • Options B, C, and D reflect common misunderstandings about Singleton's capabilities and limitations.
Interviewer Note:
CONTEXT
  • Tests candidate's grasp of design pattern trade-offs and when not to use Singleton
Master "Design a Parking Lot - LLD with OOP (Classes, Patterns, Extensibility)" 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
Command Pattern - Undo/Redo, Request Queuing & Logging - Command Pattern - Undo/Redo, Request Queuing & Logging - Quiz 12easy Encapsulation - Data Hiding, Getters/Setters & Access Modifiers - Encapsulation - Data Hiding, Getters/Setters & Access Modifiers - Quiz 12easy Inheritance - Types, Method Resolution Order & Diamond Problem - Inheritance - Types, Method Resolution Order & Diamond Problem - Quiz 8hard Inheritance - Types, Method Resolution Order & Diamond Problem - Inheritance - Types, Method Resolution Order & Diamond Problem - Quiz 5medium Iterator & Composite Pattern - Traversal Abstractions - Iterator & Composite Pattern - Traversal Abstractions - Quiz 1easy Observer Pattern - Event System, Publish-Subscribe - Observer Pattern - Event System, Publish-Subscribe - Quiz 9hard Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Quiz 5medium Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Polymorphism - Compile-Time (Overloading) vs Runtime (Overriding) - Quiz 7medium Singleton Pattern - Thread Safety, Double-Checked Locking & Lazy Init - Singleton Pattern - Thread Safety, Double-Checked Locking & Lazy Init - Quiz 1easy Strategy Pattern - Replace Conditionals with Polymorphism - Strategy Pattern - Replace Conditionals with Polymorphism - Quiz 5medium