Clean Architecture layers in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the core layer in Clean Architecture

In Clean Architecture, which layer contains the business rules and enterprise logic that should not depend on any other layers?

A Entities layer

B Interface Adapters layer

C Frameworks and Drivers layer

D Use Cases layer

💡 Hint

Think about the layer that holds the core business logic independent of UI or database.

The Entities layer contains the core business rules and enterprise logic. It is independent and does not depend on any other layers.

❓ Architecture

intermediate

Layer responsible for data format conversion

Which Clean Architecture layer is responsible for converting data from the format used by the database or external services into a format usable by the business logic?

A Entities layer

B Interface Adapters layer

C Use Cases layer

D Frameworks and Drivers layer

💡 Hint

This layer acts like a translator between external data and internal business logic.

The Interface Adapters layer converts data from external sources into a form usable by the business logic and vice versa.

❓ scaling

advanced

Scaling Clean Architecture for multiple user interfaces

When scaling an application to support multiple user interfaces (e.g., web, mobile, desktop), which Clean Architecture principle helps maintain code independence and reusability?

A Keep business rules independent of UI frameworks by placing them in the Entities and Use Cases layers

B Duplicate business logic in each UI layer to optimize performance

C Merge UI and business logic layers to reduce complexity

D Use Frameworks and Drivers layer to implement business rules for each UI

💡 Hint

Think about separation of concerns and reusability of core logic.

Keeping business rules independent of UI frameworks allows multiple user interfaces to reuse the same core logic without duplication.

❓ tradeoff

advanced

Tradeoff of placing database code in Frameworks and Drivers layer

What is a key tradeoff when placing database access code in the Frameworks and Drivers layer of Clean Architecture?

A It removes the need for Interface Adapters layer

B It improves performance by embedding queries in business rules

C It isolates database dependencies but may increase complexity in data mapping

D It simplifies business logic but tightly couples it to the database

💡 Hint

Consider separation of concerns and complexity of data transformations.

Placing database code in Frameworks and Drivers isolates dependencies but requires mapping data to business entities, adding complexity.

❓ component

expert

Request flow through Clean Architecture layers

In a typical request flow of Clean Architecture, which sequence correctly represents the order of layers a request passes through from UI to database and back?

A 1, 3, 2, 4

B 2, 1, 3, 4

C 4, 3, 2, 1

D 1, 2, 3, 4

💡 Hint

Think about the outermost layer receiving the request and the innermost layer containing core logic.

The request starts at Frameworks and Drivers (UI), passes through Interface Adapters (data conversion), then Use Cases (application logic), and finally Entities (business rules).

Practice

1. Which layer in Clean Architecture contains the core business rules and logic?

easy

A. UI layer

B. Entities layer

C. Database layer

D. Frameworks layer

Solution

1. Step 1: Understand the role of each layer

   The Entities layer holds the core business rules and logic, independent of external concerns.

2. Step 2: Identify the correct layer for business logic

   UI, Database, and Frameworks layers handle external interactions, not core logic.

3. Final Answer:

   Entities layer -> Option B

4. Quick Check:

   Business logic = Entities layer [OK]

Hint: Core logic always lives in the Entities layer [OK]

Common Mistakes:

• Confusing UI layer with business logic
• Thinking database layer contains core rules
• Mixing frameworks with core logic

2. In Clean Architecture, which layer is responsible for adapting data from the database to the business logic?

easy

A. Entities layer

B. Use Cases (Interactor) layer

C. UI layer

D. Interface Adapters layer

Solution

1. Step 1: Identify the role of Interface Adapters

   Interface Adapters convert data from external sources like databases into a form usable by inner layers.

2. Step 2: Confirm other layers' roles

   Entities hold business rules, Use Cases orchestrate logic, UI handles presentation, so adapting data fits Interface Adapters.

3. Final Answer:

   Interface Adapters layer -> Option D

4. Quick Check:

   Data adaptation = Interface Adapters [OK]

Hint: Data conversion happens in Interface Adapters [OK]

Common Mistakes:

• Choosing Entities layer for data adaptation
• Confusing Use Cases with data conversion
• Selecting UI layer for database data handling

3. Given the following flow in Clean Architecture: UI calls Use Cases, which then call Entities. What is the correct order of dependency direction?

medium

A. UI -> Entities -> Use Cases

B. Entities -> Use Cases -> UI

C. UI -> Use Cases -> Entities

D. Use Cases -> UI -> Entities

Solution

1. Step 1: Understand dependency rule in Clean Architecture

   Dependencies always point inward, from outer layers to inner layers.

2. Step 2: Apply to given flow

   UI depends on Use Cases, which depend on Entities, so direction is UI -> Use Cases -> Entities.

3. Final Answer:

   UI -> Use Cases -> Entities -> Option C

4. Quick Check:

   Dependency direction = UI to Entities [OK]

Hint: Dependencies always point inward [OK]

Common Mistakes:

• Reversing dependency direction
• Confusing which layer calls which
• Assuming Entities depend on UI

4. A developer placed database access code directly inside the Entities layer. What is the main problem with this design?

medium

A. Entities layer should not depend on external frameworks or databases

B. Entities layer must handle UI rendering

C. Database code belongs only in the UI layer

D. Entities layer should only contain database schemas

Solution

1. Step 1: Recall Clean Architecture dependency rules

   Inner layers like Entities must be independent of external concerns like databases.

2. Step 2: Identify why database code in Entities is wrong

   It creates tight coupling and breaks separation of concerns.

3. Final Answer:

   Entities layer should not depend on external frameworks or databases -> Option A

4. Quick Check:

   Entities layer independence = true [OK]

Hint: Keep Entities free from external dependencies [OK]

Common Mistakes:

• Thinking Entities handle UI
• Placing database code in UI layer
• Confusing database schemas with business logic

5. You need to design a system where the UI can be changed without affecting business rules, and the database can be swapped easily. Which Clean Architecture principle helps achieve this?

hard

A. Dependency Rule: Inner layers do not depend on outer layers

B. UI layer directly accesses Entities for faster updates

C. Database layer contains business logic for flexibility

D. Use Cases layer handles UI rendering and database access

Solution

1. Step 1: Identify the principle for independence

   The Dependency Rule states inner layers (business rules) do not depend on outer layers (UI, database).

2. Step 2: Explain how this helps system flexibility

   This separation allows changing UI or database without impacting core business logic.

3. Final Answer:

   Dependency Rule: Inner layers do not depend on outer layers -> Option A

4. Quick Check:

   Dependency Rule ensures flexibility [OK]

Hint: Inner layers must be independent for easy changes [OK]

Common Mistakes:

• Allowing UI to access Entities directly
• Putting business logic in database layer
• Mixing UI rendering with Use Cases