MVVM pattern in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the role of ViewModel in MVVM

In the MVVM pattern, what is the primary responsibility of the ViewModel?

A To hold and manage UI-related data and handle business logic without referencing the View directly

B To directly update the UI components and handle user input events

C To manage database operations and network calls exclusively

D To act as a data model representing the app's data structure

💡 Hint

Think about which component acts as a bridge between UI and data without knowing UI details.

The ViewModel holds UI data and business logic, exposing data to the View without referencing it directly, enabling separation of concerns.

❓ ui_behavior

intermediate

LiveData observation in MVVM

Given a ViewModel exposing LiveData called 'status', what happens in the View when the LiveData value changes?

Android Kotlin

viewModel.status.observe(viewLifecycleOwner) { newStatus ->
  textView.text = newStatus
}

A The textView's text updates only if manually refreshed by the user

B The textView's text updates only once when the View is created

C The textView's text never updates because LiveData does not notify observers

D The textView's text updates automatically to the new status value whenever it changes

💡 Hint

LiveData notifies observers when data changes.

LiveData automatically notifies observers when its data changes, triggering UI updates like setting textView.text.

❓ lifecycle

advanced

ViewModel lifecycle and data retention

What happens to the ViewModel instance when the associated Activity is recreated due to a configuration change (e.g., device rotation)?

A The ViewModel is destroyed immediately and recreated with the Activity

B A new ViewModel instance is created, losing previous data

C The same ViewModel instance is retained and reused, preserving its data

D The ViewModel instance is shared across all Activities in the app

💡 Hint

ViewModel is designed to survive configuration changes.

ViewModel instances survive configuration changes like rotations, so data is preserved and reused by the new Activity instance.

❓ navigation

advanced

Sharing data between fragments using ViewModel

How can two fragments in the same Activity share data using MVVM pattern?

A Each fragment creates its own ViewModel instance and communicates via interfaces

B Both fragments use the same Activity-scoped ViewModel instance to share LiveData

C Fragments directly access each other's views to share data

D Fragments use static variables to share data globally

💡 Hint

Think about ViewModel scope and shared lifecycle owners.

Using an Activity-scoped ViewModel allows multiple fragments to observe and update shared LiveData, enabling communication without tight coupling.

🔧 Debug

expert

Diagnosing a memory leak caused by ViewModel misuse

A developer stores a reference to an Activity's Context inside a ViewModel. What is the likely consequence?

A Memory leak occurs because ViewModel outlives Activity and holds a strong reference to its Context

B No problem occurs because ViewModel automatically clears references on Activity destruction

C App crashes immediately due to invalid Context usage

D The Context reference is weak and does not affect memory

💡 Hint

Consider how long ViewModel lives compared to Activity and what holding Context means.

ViewModel lives longer than Activity during configuration changes; holding Activity Context causes memory leaks by preventing garbage collection.