Which of the following are ways in which activities in Android are designed to be

They are destroyed (and must be recreated later) when the back button is pressed

They are destroyed and recreated to handle runtime configuration changes

They can interact with the user in powerful ways

They perform long-duration operations and/or access remote resources via background threads/processes

========================

Started services

Bound services

Background services

Scheduled services

========================

DownloaderService

Activity Manager Service

MusicPlaybackService

Alert service

========================

onUnbind()

onStartCommand()

onCreate()

onRebind()

onDestroy()

onBind()

========================

onBind()

onCreate()

onDestroy()

onUnbind()

========================

onCreate() receives the intent passed by the client that calls start service, whereas onStartCommand() does not

onStartCommand() is called once when startService() is first called, whereas onCreate() is called each time startService() is called

onStartCommand() receives the intent passed by the client that calls start service, whereas onCreate() does not

Which of the following are ways in which activities in Android are designed to be “ephemeral” (choose all that apply)