How is recurring delivery similar to a continuous delivery?

The most fundamental similarity between a recurring delivery and a continuous delivery is their purpose: both are designed to be sent multiple times automatically. A recurring delivery executes in batches based on a schedule (e.g., weekly newsletter), while a continuous delivery sends individual messages triggered by an event or data entry (e.g., a welcome email). Despite their different execution mechanics, their core shared function is to facilitate repeated, automated communication, distinguishing them from a standard, one-off delivery.

A. Both deliveries append record to the delivery log This is incorrect. Only a continuous delivery appends records to a single, persistent delivery log. A recurring delivery creates a new, separate delivery instance and log for each execution.
C. Both deliveries can be modified in the delivery step This is not the best answer. While both are configured in a workflow's delivery activity ("step"), this is a general characteristic of workflow-based deliveries, including standard ones. It doesn't capture the unique functional similarity between recurring and continuous types.
D. Both deliveries create new delivery logs This is incorrect. Only a recurring delivery creates new delivery logs for each run. A continuous delivery uses a single delivery instance and appends to its existing logs. ---

1. Adobe Experience League Documentation - Campaign Classic - Recurring Delivery:

Section: "Operating principle"

Content: "The aim of a recurring delivery is to execute a delivery based on a template multiple times." This directly supports that the purpose is to send multiple times (Answer B). It also states, "This instance will be duplicated on each execution of the activity," which confirms it creates new instances/logs, invalidating option D and showing a difference from continuous delivery (invalidating A).

Source: Adobe. (n.d.). Recurring delivery. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/campaign-classic/using/automating-with-workflows/delivery-activities/recurring-delivery.html

2. Adobe Experience League Documentation - Campaign Classic - Continuous Delivery:

Section: "Operating principle"

Content: "The aim of a continuous delivery is to send a delivery each time an event is received." This supports the concept of sending multiple times based on triggers (Answer B). It also notes, "Each time a profile goes through this activity, a new line is added to the delivery logs," confirming it appends to a single log, which invalidates option A as a similarity and option D outright.

Source: Adobe. (n.d.). Continuous delivery. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/campaign-classic/using/automating-with-workflows/delivery-activities/continuous-delivery.html