Clean Architecture layers in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the correct Clean Architecture layer for UI logic

In Clean Architecture for Android, which layer should handle user interface logic such as displaying data and capturing user input?

A Framework layer

B Data layer

C Domain layer

D Presentation layer

💡 Hint

Think about where the app interacts directly with the user.

The Presentation layer is responsible for UI logic, managing views and user interactions. The Domain layer handles business rules, Data layer manages data sources, and Framework layer includes external tools.

❓ ui_behavior

intermediate

Effect of violating Dependency Rule in Clean Architecture

What happens if the Data layer directly depends on the Presentation layer in a Clean Architecture Android app?

A The app will crash at runtime due to circular dependencies

B It improves performance by reducing abstraction layers

C It breaks the Dependency Rule, causing tight coupling and harder testing

D It is recommended for faster UI updates

💡 Hint

Consider the direction of dependencies in Clean Architecture.

Clean Architecture enforces that dependencies point inward, from outer layers to inner layers. If Data depends on Presentation, it creates tight coupling and makes testing and maintenance difficult.

❓ lifecycle

advanced

Correct lifecycle owner for ViewModel in Clean Architecture

In an Android app using Clean Architecture, which lifecycle owner should be used to scope a ViewModel in the Presentation layer?

A Activity or Fragment lifecycle

B Application lifecycle

C Domain layer lifecycle

D Data layer lifecycle

💡 Hint

ViewModels are tied to UI components' lifecycles.

ViewModels should be scoped to the Activity or Fragment lifecycle to survive configuration changes and manage UI data properly. Application lifecycle is too broad, and Domain/Data layers do not have lifecycles.

❓ navigation

advanced

Where to handle navigation logic in Clean Architecture

In Clean Architecture, where should navigation logic (e.g., moving between screens) be implemented in an Android app?

A Data layer, to fetch navigation data

B Presentation layer, to handle UI navigation events

C Domain layer, because navigation is a business rule

D Framework layer, to access Android navigation components

💡 Hint

Think about which layer controls user interactions and screen changes.

Navigation is part of UI behavior and should be handled in the Presentation layer. Domain layer handles business rules, Data layer manages data, and Framework layer provides tools but does not contain navigation logic.

🔧 Debug

expert

Diagnose the cause of a runtime crash due to layer violation

An Android app using Clean Architecture crashes at runtime with a ClassCastException when the Data layer tries to cast a Presentation layer class. What is the most likely cause?

A The Data layer depends on Presentation layer classes, violating the Dependency Rule

B The Presentation layer is incorrectly referencing Domain entities

C The Domain layer is missing interface implementations

D The Framework layer is not initialized before use

💡 Hint

ClassCastException often happens when layers depend on each other incorrectly.

If the Data layer depends on Presentation classes, it breaks the Dependency Rule and can cause ClassCastException at runtime due to improper class references.