Online Access Free Associate-Android-Developer Practice Test

In a common Paging Library architecture scheme, move instances to the correct positions.

Correct Answer:

Reference:
https://developer.android.com/topic/libraries/architecture/paging/ui

Select a correct statement about PagedList.

• A.PagedList is content-immutable. This means that, although new content can be loaded into an instance of PagedList, the loaded items themselves cannot change once loaded.
• B.PagedList is content-mutable. This means that new content can be loaded into an instance of PagedList and the loaded items themselves can change once loaded.
• C.PagedList is content-accidental. This means that new content can be loaded into an instance of PagedList and the loaded items themselves can be changed to accidental values randomly.

What is the placeholder tag <xliff:g> used for?

• A.To mark text that should not be translated.
• B.To raise a translation priority to a higher level
• C.To raise a quantity of translations for the string
• D.To pick up and move sting translation from a different resource file

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.

Correct Answer:

When scheduling unique work, you must tell WorkManager what action to take when there is a conflict. You do this by passing an enum when enquing the work. For one-time work, you provide an ExistingWorkPolicy, which supports some options for handling the conflict. (Choose four.)

• A.APPEND_OR_KEEP (functions similarly to APPEND, except that it is not dependent on prerequisite work status. If the existing work is CANCELLED or FAILED, the new work still not runs)
• B.APPEND (the new work to the end of the existing work. This policy will cause your new work to be chained to the existing work, running after the existing work finishes)
• C.APPEND_OR_REPLACE (functions similarly to APPEND, except that it is not dependent on prerequisite work status. If the existing work is CANCELLED or FAILED, the new work still runs)
• D.APPEND_OR_DESTROY (if no any work exists, the new work will be ignored)
• E.DESTROY (if any work exists, the new work will be ignored)
• F.KEEP (existing work and ignore the new work)
• G.APPEND_AND_RUN (functions similarly to APPEND, except that it is not dependent on prerequisite work status. If the existing work is PAUSED, the new work still runs)
• H.REPLACE (existing work with the new work. This option cancels the existing work)