1.

AndroidManifest.xml

2.

Components.xml

3.

AppManifest.xml

4.

ComponentManifest.xml

1.

android:talkBack

2.

android:labelFor

3.

android:hint

4.

android:contentDescription

1.

Set breakpoints and then step through the code line by line

2.

Use the profiler tools in Android Studio to detect anomalies CPU, and network usage.

3.

Add a Thread.sleep() call before you start the new activity.

4.

inspect the logs in Logcat.

1.

all of these answers

2.

The device token is not being sent to push provider correctly.

3.

Google Play Services is not installed on the deivce/emulator.

4.

Battery optimization is turned on on the device.

1.

2.

3.

4.

1.

Process:In the background;Activity:Is stopped

2.

Process:In the background;Activity:Is paused

3.

Process:In the foreground;Activity:Is started

4.

Process:In the foreground;Activity:Is paused

1.

2.

3.

4.

1.

in build.gradle:include ':app',':about' ':settings'

2.

in settings.gradle:include ':app',':about' ':settings'

3.

in settings.gradle:include ':about',':settings'

4.

in gradle.properties:include ':app',':about' ':settings'

1.

to denote that a class, methos, or field has its visibility relaxed to make code testable

2.

to denote that a class, method, or field is visible only in the test code

3.

to denote that a class, method, or field has its visibility increased to make code less testable

4.

to throw a run-time error if a class, methos, or field with this annotation is accessed improperly

1.

2.

3.

4.

1.

when calling finish()in the parent activity

2.

when placing an app into the background by sitching to another app

3.

When onStop() is called in the target activity

4.

when calling finish() in the target activity

1.

@DELETE("events)

2.

@DELETE("events/{id}")

3.

@REMOVE("events/{id}")

4.

@DELETE("events/{id}")

1.

when you need to have the app's strings present in multiple lanuages

2.

when you have to provide different versions of your app based on the physical device size

3.

when you want to provide different versions of your app based on the device screen density

4.

when you want to provide different version of your app with custom configuration and resources

1.

root.getById(R.id.text_home)

2.

findViewByID(R.id.text_home)

3.

root.findViewById(R.id.text_home)

4.

root.find(R.id.text_home)

1.

The test runner facilitates loading your test package and the app under test onto a device or emulator, runs the test, and reports the results.

2.

The test runner creating screenshots of each screen that displayed while tests are executed.

3.

The test runner facilitates parallelization of test classes by providing for each test class.

4.

The test runner facilitates interacting with visible elements on a device, regardless of the activity or fragment that has focus.

1.

the onSaveInstance()method

2.

all of these answers

3.

persistent storage

4.

ViewModel objects

1.

root.find(R.id.text_home)

2.

findViewById(R.id.text_home)

3.

root.getById(R.id.text_home)

4.

root.findViewById(R.id.text_home)

1.

Thread Not Responding

2.

Application Paused

3.

Application Not Responding

4.

Application Blocked

1.

getPreferances(this).getString(Email,"")

2.

getDefaultSharedPrefarances(this).getString(EMAIL,null)

3.

getDefaultSharedPreferances(this).getString(EMAIL,"")

4.

getPreferances(this).getString(EMAIL,null)

1.

Although screen pixel density varies, this does not impact the use of pixels to define sizes.

2.

Large devices always have more pixels, so your UI elements will be e=affected if you define them with pixels.

3.

The same number of pixels may correspond to different physical sizes, affecting the appearance of your UI elements.

4.

Different devices have different understanding of what a pixel is , affecting the appearance of your UI elements

1.

list devices

2.

adb devices

3.

list avd

4.

dir devices

1.

2.

3.

4.

1.

external file storage

2.

SharedPereferences

3.

SQLite

4.

internal file storage

1.

@GET("photo/{id}"}

2.

@LIST("photo")

3.

@GET("photo")

4.

@GET("photo")

1.

assertThat(resultAdd).is(2.0)

2.

assertNotNull(resultAdd)

3.

assertThat(resultAdd).isWqualTo(2.0)

4.

assertThat(resultAdd)

1.

`<merge/>`

2.

`<include/>`

3.

`<layout/>`

4.

`<add/>`

1.

fr-land-drawable

2.

drawable-fr-land

3.

drawable-french-land

4.

french-land-drawable

1.

to monitor the location of the devices so that you don't attempt to make network calls when the user is stationary

2.

to request the ability to make network calls from your app

3.

to monitor the network state of the device so that you can display an in-app banner to the user

4.

to monitor the network state of the devices so that you don't attempt to make network calls when the network is unavailable

1.

A

2.

B

3.

C

4.

D

1.

`startActivityWithResult()` should be used instead of `startActivity()` when using `Intent.ACTION_DIAL`.

2.

For `Intent.ACTION_DIAL`, the `Intent` option `Intent.FLAG_ACTIVITY_NEW_TASK` must be added when using this `dialerIntent`.

3.

The `dialerIntent` will cause an ActivityNotFoundException to be thrown on devices that do not support `Intent.ACTION_DIAL`.

4.

The permission `android.permission.CALL_PHONE` must be requested first before `Intent.ACTION_DIAL` can be used.

1.

when you need access to the original file names and file hierarchy [(Reference)](https://medium.com/mobile-app-development-publication/assets-or-resource-raw-folder-of-android-5bdc042570e0)

2.

when you need access to the file with its `resource ID`, like `R.assets.filename`

3.

when you have XML files that define tween animations

4.

when you need to access the file in its raw form using `Resources.openRawResource()`

1.

Users can select their favorite photo apps to take pictures.

2.

You do not have to make a permission request in your app to take a picture.

3.

You have full control over the user experience. The app that handles the camera `intent` will respect your design choices.

4.

You do not have to design the UI. The app that handles the camera `intent` will provide the UI.

1.

when a user first opens your app and you want to provide an explanation for the use of a given permission

2.

when a user has previously denied the request for a given permission and selects "Tell me more"

3.

when a user has previously denied the request for a given permission and you want to provide an explanation for its use

4.

when a user has previously denied the request for a given permission and selected "Don't ask again," but you need the permission for your app to function

1.

2.

3.

4.

1.

JPG

2.

PNG

3.

MPEG

4.

WebP [(Reference)](https://developer.android.com/topic/performance/reduce-apk-size#:~:text=packJPG%20and%20guetzli.-,Use%20WebP%20file%20format,than%20either%20JPEG%20or%20PNG.)

1.

checking whether `ProGuard` -keepclassmembers have been added to the network data transfer objects (DTOs) in question

2.

using the profiler tools in Android Studio to detect anomalies in CPU, memory, and network usage

3.

checking for exceptions in the server logs or server console

4.

checking that the network data transfer object has `@SerizlizedName` applied to its member properties

1.

2.

3.

4.

1.

test

2.

androidTest

3.

app

4.

main

1.

2.

3.

4.

1.

Use the `ActivityManager.isLowRamDevice()` method to find out whether a device defines itself as "low RAM."

2.

Use the `Activity.islowRam()` method to find out whether a device defines itself as "low RAM."

3.

Use the `ConnectivityManager.hasLowMemory()` method to find out whether a device defines itself as "low RAM."

4.

Make an image download request and check the remaining device storage usage.

1.

Use a common Gradle module shared by different Android projects.

2.

Prefer to build custom views or fragments over activities.

3.

Prefer to build activities instead of fragments.

4.

Break down UI layouts into common elements and use `<include/>` to include them in other layout XML files.

1.

LinearLayout

2.

ConstraintLayout

3.

FrameLayout

4.

RelativeLayout

1.

root_project_dir/app/build.gradle.

2.

root_project_dir/settings.gradle.

3.

root_project_dir/build.gradle.

4.

root_project_dir/app/gradle.properties.

1.

The Application class is instantiated before any other class when the process for the application is created.

2.

The Application class is instantiated after any permissions requests when the process for the application is created.

3.

The Application class is created each time a new Activity is launched, making it ideal for initialization code.

4.

The Application class is created each time a background service is called, making it ideal for initialization code.

1.

/drawable

2.

/icon

3.

/mipmap

4.

/launcher

1.

2.

3.

4.

1.

View B is not horizontally constrained.

2.

View C has too many constraints.

3.

View B is not vertically constrained.

4.

View C is constrained to the parent.

1.

productionDebug.

2.

developmentDebug.

3.

stagingDebug.

4.

stagingRelease.

1.

when the tests consist only of unit tests.

2.

when the number of tests to run is large(500+).

3.

when the tests need to run on your local machine.

4.

when the tests need to run on real or virtual devices.

1.

This APK is created on a developer machine from the debug product flavor.

2.

This APK is created from the internalDebug product flavor.

3.

This APK created from the debug product flavor and internal build type.

4.

This APK is created from the debug build type and internal product flavor.

1.

You have included incorect format information in your build.gradle file.

2.

You have added more than 20 dependencies to your build.gradle.

3.

You have exceeded the total number of methods that can be referenced within a single DEX file.

4.

You have a NullPointerException in your code.

1.

apply plugin: 'com.module.library'

2.

apply plugin: 'com.android.library'

3.

apply plugin: 'com.module.library'

4.

include plugin: 'com.module.library'

1.

2.

3.

4.

1.

It allows Android to choose the appropriate resource based on the current configuration during runtime.

2.

It allows you to have more performant applications because the code and resources are separated.

3.

It allows you to provide a different Ul experience based on the user's language settings.

4.

It allows you to provide a different Ul experience based on the user's device size.

1.

to make sure that the activity finishes when the savedInstanceState is not null

2.

to make sure that the activity creates a new fragment each time it is restored from a previous state

3.

to prevent the display of two fragments side by side in cases where the activity is restored from a previous state

4.

to prevent the creation of overlapping fragments in cases where the activity is restored from a previous state

1.

activity

2.

content provider

3.

fragment

4.

service

1.

ListView

2.

Recycler View

3.

LinearLayout

4.

Scrollview

1.

Intent(this, AboutActivity::class).also { intent ->

2.

Intent(this, AboutActivity::class.java).also { intent ->

3.

Intent(this, AboutActivity::class).also { intent ->

4.

Intent(this, AboutActivity::class).also { intent ->

1.

It describes the component of the application

2.

It declares the minimum level of the android API that the application requires

3.

It facilitates to provide a uinque name for the application by specifying package name

4.

All of the above

1.

android:targetSdkVersion

2.

android:minSdkVersion

3.

android:maxSdkVersion

4.

None of the above

1.

R8

2.

ProGuard

3.

Shrinker

4.

D8

1.

A

2.

B

3.

C

4.

D

1.

WorkManager

2.

AsyncTask

3.

IntentService

4.

Thread

1.

library module

2.

dynamic feature module

3.

Android app module

4.

Google Cloud module

1.

caching data

2.

storing data locally

3.

queuing outbound requests to action when connectivity has been lost

4.

always notifying users that connectivity has been lost