Repository pattern in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of the Repository pattern in Android development?

Choose the best explanation for why developers use the Repository pattern in Android apps.

A To store user preferences and settings only.

B To directly connect UI components to the database without any abstraction.

C To handle all UI animations and transitions in the app.

D To separate data access logic from UI logic, making code easier to manage and test.

💡 Hint

Think about how to keep your app organized and easy to change.

The Repository pattern acts as a middle layer between data sources and the UI, helping to keep code clean and testable.

❓ ui_behavior

intermediate

How does the Repository pattern affect UI updates when data changes?

In an Android app using LiveData and Repository, what happens when data in the repository changes?

A The UI automatically updates because LiveData observes the data changes from the Repository.

B The UI must be manually refreshed by the user to see new data.

C The Repository directly modifies UI elements to show new data.

D The app crashes because Repository cannot notify the UI.

💡 Hint

Think about how LiveData helps UI react to data changes.

LiveData observes data in the Repository and notifies UI components to update automatically.

❓ lifecycle

advanced

What lifecycle benefit does the Repository pattern provide in Android apps?

How does using a Repository help manage data during configuration changes like screen rotations?

A Repository only works with static data and ignores lifecycle events.

B Repository resets all data when the screen rotates, forcing a reload.

C Repository keeps data consistent and survives configuration changes, avoiding unnecessary reloads.

D Repository causes memory leaks during lifecycle changes.

💡 Hint

Think about how ViewModel and Repository work together during rotations.

Repository combined with ViewModel keeps data stable across lifecycle changes, improving performance.

❓ navigation

advanced

How should the Repository pattern be used with Navigation components?

When navigating between fragments, how does the Repository pattern help with data sharing?

A Repository provides a single source of truth that multiple fragments can access for consistent data.

B Each fragment should create its own Repository instance with separate data.

C Repository should be tightly coupled to navigation actions to control screen changes.

D Repository replaces the Navigation component to handle screen transitions.

💡 Hint

Consider how to share data easily between screens.

A shared Repository allows fragments to access the same data source, ensuring consistency during navigation.

🔧 Debug

expert

What error occurs if Repository returns null LiveData and UI tries to observe it?

Given this Kotlin code snippet, what error will happen? val data: LiveData? = repository.getData() data.observe(viewLifecycleOwner) { value -> println(value) } Options:

A No error; the UI will just not update.

B NullPointerException because data is null and cannot be observed.

C IllegalStateException because LiveData must be initialized before observing.

D ClassCastException because LiveData type is incorrect.

💡 Hint

What happens if you call a method on a null object in Kotlin?

Observing a null LiveData causes a NullPointerException because you cannot call observe on null.