Why ViewModel survives configuration changes in Android Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a ViewModel instance in an Activity.

Android Kotlin

val viewModel = ViewModelProvider(this).get([1]::class.java)

Drag options to blanks, or click blank then click option'

AApplication

BMainActivity

CViewModelProvider

DMyViewModel

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the Activity class instead of the ViewModel class.

You need to pass your ViewModel class to get() to create or retrieve it.

2fill in blank

medium

Complete the code to extend the ViewModel class correctly.

Android Kotlin

class MyViewModel : [1]() {
  // ViewModel logic here
}

Drag options to blanks, or click blank then click option'

AActivity

BFragment

CViewModel

DApplication

Attempts:

3 left

💡 Hint

Common Mistakes

Extending Activity or Fragment instead of ViewModel.

Your ViewModel class must extend ViewModel to survive configuration changes.

3fill in blank

hard

Fix the error in the code to get the ViewModel in a Fragment.

Android Kotlin

val viewModel = ViewModelProvider([1]).get(MyViewModel::class.java)

Drag options to blanks, or click blank then click option'

ArequireActivity()

Bthis

Capplication

DviewLifecycleOwner

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'this' which refers to Fragment, creating a Fragment-scoped ViewModel.

Using requireActivity() shares the ViewModel between Fragment and its Activity, surviving configuration changes.

4fill in blank

hard

Fill both blanks to explain why ViewModel survives configuration changes.

Android Kotlin

ViewModel is stored in the [1] and tied to the [2] lifecycle.

Drag options to blanks, or click blank then click option'

AViewModelStore

BActivity

CApplication

DFragment

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Application with ViewModelStore or Fragment.

The ViewModelStore keeps ViewModels alive, and they are tied to the Activity lifecycle, which survives configuration changes.

5fill in blank

hard

Fill all three blanks to complete the explanation of ViewModel behavior.

Android Kotlin

When configuration changes, the [1] is destroyed but the [2] and [3] remain, keeping ViewModel alive.

Drag options to blanks, or click blank then click option'

AActivity

BViewModelStore

CFragment

DApplication

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking Activity survives configuration changes.

The Activity is destroyed and recreated on configuration change, but the Application and ViewModelStore survive, so ViewModel data is preserved.