When Scheduling Unique Work, You Must Tell WorkManager What Action

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) REPLACE (existing work with the new work. This option cancels the existing work)
B) KEEP (existing work and ignore the new work)
C) 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)
D) 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)
E) 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)
F) 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)
G) DESTROY (if any work exists, the new work will be ignored)
H) APPEND_OR_DESTROY (if no any work exists, the new work will be ignored)