For device delivery, Oracle Analytics distinguishes between Active Delivery Profile and Specific Devices . Active Delivery Profile lets each user determine delivery behavior through personal delivery preferences. When the Agent must instead target explicitly chosen device types, the author selects Specific Devices and identifies the permitted devices. This satisfies the requirement to avoid reliance on the user's active profile.

For cache seeding, Oracle documents a dedicated Agent workflow. After choosing the analysis or dashboard page and establishing recipients, the administrator clears ordinary user destinations and selects the Analytics Server/BI Server Cache destination. Scheduled execution then populates the query cache using the results generated by the Agent.

The terminology in the question uses Oracle BI Server Cache , while current Oracle Analytics Server documentation refers to Oracle Analytics Server Cache ; functionally, this is the same cache-seeding destination represented by option E.

Selecting Never wouldn't schedule cache seeding. Home Page and Dashboard creates analytics alerts rather than restricting delivery to email devices. Active Delivery Profile does the opposite of the requirement, and Printer isn't the standard cache-seeding destination.

Therefore, the correct selections are Specific Devices and Oracle BI Server Cache .

Reference Topic: Managing Administration, Security, and Performance — Agent Destinations and Cache Seeding

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