Compose Room Database Quiz Pt 2

Welcome to the Room Database Quiz! This quiz will test your knowledge of implementing SQLite-based database storage using the Room persistence library in Android applications. The questions cover various aspects, including setting up a Room database, working with entities, DAOs, repositories, and integrating these with a ViewModel and Jetpack Compose UI. Whether you’re revisiting concepts or testing your understanding, this quiz is designed to help reinforce your learning and ensure you’re ready to build robust data-driven Android apps.

Which library is required for handling asynchronous Room database queries?

Coroutines

Retrofit

Dagger

Glide

None

How can changes to database records be automatically reflected in the UI?

By setting up manual refresh methods in the DAO.

By directly accessing the database in the UI.

By storing data in SharedPreferences.

By using ‘LiveData’ and observing it in the ViewModel.

None

Which component is typically responsible for managing the UI state in the Room-based project?

Repository

ViewModel

DAO

Database

None

How is a Room database instance created in the RoomDemo project?

By writing raw SQL queries.

By creating a custom SQL engine.

By directly instantiating the RoomDatabase class.

By extending the RoomDatabase class and using ‘Room.databaseBuilder’.

None

Which function is used to prevent blocking the main thread during database operations?

launch() with Dispatchers.IO

Thread.sleep()

runOnUiThread()

AsyncTask()

None

What is the purpose of the 'MainViewModelFactory' class?

To create instances of the Room database.

To provide a factory for creating ‘MainViewModel’ instances with an application context.

To define custom SQL queries.

To manage database migrations.

None

What does the 'fallbackToDestructiveMigration()' method do in Room?

Deletes and recreates the database if a migration is not found.

Automatically updates the database schema without data loss.

Prevents data loss during migrations.

Backs up the database before migration.

None

Which annotation is used to define a class as an entity in Room?

@Dao

@Entity

@Table

@Database

None

What is the role of a Repository class when working with Room databases?

To provide direct access to the database.

To manage API calls.

To create UI components.

To abstract data operations and interact with the DAO.

None

10.

Why might 'autoGenerate = true' be used with the '@PrimaryKey' annotation?

To manage schema migrations automatically.

To enable foreign key constraints.

To automatically create entity classes.

To auto-generate primary key values for new records.

None

11.

Why is it important to avoid performing database operations on the main thread?

To improve network performance.

To reduce battery consumption.

To enable debugging features.

To ensure the app’s UI remains responsive.

None

12.

What is the purpose of using 'MutableLiveData' in a repository?

To define database table schemas.

To store search results for observed updates.

To manage UI theme changes.

To create a backup of database data.

None

13.

What should be done to use the Database Inspector with a running Room database app?

Enable ProGuard settings.

Enable a debug mode in Room configuration.

Connect to a physical device.

Run the app on an emulator or connected device.

None

14.

Which component in Room is responsible for defining SQL queries?

Entity

Repository

DAO

ViewModel

None

15.

What does the '@Insert' annotation in a DAO do?

Inserts new records into the database.

Updates existing records in the database.

Executes a custom SQL query.

Deletes records from the database.

None

16.

Why is 'LiveData' used in Room database queries?

To handle database transactions.

To observe and automatically update the UI with database changes.

To ensure queries are executed on the main thread.

To improve database performance.

None