A customer needs an automated process to send event notifications every 15 minutes to a group of users. No user should receive the same notification twice. What activities should the Adobe Campaign Classic developer use in the Campaign workflow to perform this?

To meet the requirements, the workflow must be initiated on a recurring schedule and must prevent sending duplicate notifications. The Scheduler activity is the correct tool to trigger a workflow at a defined, repeating interval, such as every 15 minutes. After an initial targeting activity (e.g., a Query) selects all users who meet the event criteria, a Test activity is necessary. This Test activity acts as a filter, checking if a user has already been targeted in a previous run of this same workflow (e.g., by checking delivery logs) and excluding them from the current execution, thus fulfilling the "no duplicates" requirement.

A. A Test activity before targeting is illogical because there is no audience defined yet to be tested or filtered.
B. A Wait activity only pauses a single workflow execution for a set duration; it does not re-trigger the entire workflow on a recurring schedule.
C. This option is incorrect for two reasons: a Wait activity cannot create a recurring schedule, and a Test activity cannot function properly before a target audience is defined.

1. Adobe Experience League - Campaign Classic v7 Documentation, "Scheduler". In the "Properties" section, the documentation states, "The Scheduler activity is used to trigger the execution of a workflow at a planned date and time." It details the "Execution frequency" parameter, which allows for repeated execution at set intervals (e.g., every N minutes), directly addressing the "every 15 minutes" requirement.

2. Adobe Experience League - Campaign Classic v7 Documentation, "Test". The documentation explains, "The Test activity allows you to use one or more activation conditions for a transition." This confirms its role in splitting a target population based on a condition, which is the necessary logic to filter out recipients who have already received the notification. The activity must be placed after the target population is defined.

3. Adobe Experience League - Campaign Classic v7 Documentation, "Workflow activities". The general structure of targeting workflows shows that scheduling activities initiate the process, followed by targeting activities to build an audience, and then segmentation or filtering activities (like Test or Exclusion) to refine the audience before a delivery. This confirms the logical sequence of Scheduler -> Targeting -> Test.