0

You are reviewing an LLD for a payment processing system. The design uses tightly coupled classes for payment methods. What is the best design improvement?

hard📝 Trade-off Q8 of Q15

LLD - Advanced LLD Concepts

You are reviewing an LLD for a payment processing system. The design uses tightly coupled classes for payment methods. What is the best design improvement?

AIntroduce interfaces to decouple payment method implementations

BMerge all payment classes into one large class

CUse global variables to share payment data

DRemove abstraction layers to simplify design

Step-by-Step Solution

Solution:

Step 1: Identify problem with tight coupling
Tightly coupled classes reduce flexibility and increase maintenance effort.
Step 2: Apply design principle for decoupling
Using interfaces allows different payment methods to be implemented independently and extended easily.
Final Answer:
Introduce interfaces to decouple payment method implementations -> Option A
Quick Check:
Decouple with interfaces = D [OK]

Quick Trick: Use interfaces to reduce class dependencies [OK]

Common Mistakes:

MISTAKES

Combining classes increases complexity
Using globals harms modularity
Removing abstraction reduces flexibility

Master "Advanced LLD Concepts" in LLD

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More LLD Quizzes