By default, the notification's text content is truncated to fit one line. If you want your notification to be longer, for example, to create a larger text area, you can do it in this way:

• A. NotificationCompat.Builder builder = new NotificationCompat.Builder(this, CHANNEL_ID)
  .setContentText("Much longer text that cannot fit one line...")
  .setLongText("Much longer text that cannot fit one line..."))
  ...
• B. NotificationCompat.Builder builder = new NotificationCompat.Builder(this, CHANNEL_ID)
  .setContentText("Much longer text that cannot fit one line...")
  .setStyle(new NotificationCompat.BigTextStyle()
  .bigText("Much longer text that cannot fit one line..."))
  ...
• C. NotificationCompat.Builder builder = new NotificationCompat.Builder(this, CHANNEL_ID)
  .setContentText("Much longer text that cannot fit one line...")
  .setTheme(android.R.style.Theme_LongText);
  ...

If you added to your build.gradle file a room.schemaLocation:
android {
defaultConfig {
javaCompileOptions {
annotationProcessorOptions {
arguments = ["room.schemaLocation": "$projectDir/schemas".toString
()]
}
}
}
}
Then, you build your app or module.
As a result you got a json file, with such path to it: app/schemas/your_app_package/db_package/DbClass/DB_VERSION.json What are the correct statements about this file? (Choose all that apply.)

• A. Main JSONObject in this file usually should contain a number "formatVersion" and a JSONObject "database"
• B. The JSONObject "database" in this file usually should contain such objects, like "entities", "views", "setupQueries", ets.
• C. It's a file with Room-exported schema

The Testing Pyramid, shown in the Figure, illustrates how your app should include the three categories of tests: small, medium, and large. Medium tests are integration tests that:

• A. validate user journeys spanning multiple modules of your app.
• B. validate your app's behavior one class at a time.
• C. validate either interactions between levels of the stack within a module, or interactions between related modules.

About running a debuggable build variant. Usually, you can just select the default "debug" variant that's included in every Android Studio project (even though it's not visible in the build.gradle file). But if you define new build types that should be debuggable, you must add 'debuggable true' to the build type. Is that mostly true?

• A. Yes.
• B. No, if you define new build types that should be debuggable, you must add 'debuggable false'
• C. No, the debug variant should be visible in the build.gradle file anyway.

The diagram below shows a basic form of the recommended architecture for apps that use Architecture Components. The architecture consists of a UI controller, a ViewModel that serves LiveData, a Repository, and a Room database. Drag modules to correct places.