LLD - Advanced LLD Concepts
A system uses Clean Architecture. You want to log all user actions without changing business logic or UI code. Where should you add this logging?
A system uses Clean Architecture. You want to log all user actions without changing business logic or UI code. Where should you add this logging?
hard📝 Trade-off Q9 of 15
Step-by-Step Solution
Solution:
Step 1: Identify where cross-cutting concerns like logging fit
Logging is a technical concern best handled in Interface Adapters to avoid polluting business logic.Step 2: Confirm other layers' roles
Entities and Use Cases focus on business rules; Frameworks handle external tools but not direct logging of user actions.Final Answer:
Inside Interface Adapters layer -> Option BQuick Check:
Logging user actions = Interface Adapters [OK]
Quick Trick: Add logging in Interface Adapters, not Entities [OK]
Common Mistakes:
- Adding logging inside Entities or Use Cases
- Placing logging in Frameworks layer
- Mixing business logic with logging
Master "Advanced LLD Concepts" in LLD
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore LLD Quizzes