Northern Trail Outfitters wants to have a periodic, dynamic newsletter send to a set data...

A newsletter sent to a volatile, frequently-changing data extension is best served by a Scheduled Automation containing a Send Email/Send Activity, because that activity evaluates and sends to whatever population exists in the data extension at the moment the automation runs — additions and removals since the last run are automatically respected without requiring re-entry logic or contact-level state tracking. This is also the fastest delivery mechanism for large batch newsletter sends, since Send Activities in Automation Studio are optimized for bulk, list-based dispatch rather than the per-contact evaluation overhead of Journey Builder. A journey with re-entry allowed (B) introduces unnecessary complexity and processing overhead for a simple recurring batch send, and re-entry rules are designed for repeatable individual customer experiences, not periodic newsletter blasts to a churning list. Single Send Journeys (A) are designed for one-time, ad hoc sends to a static snapshot audience and are not suited to a recurring, periodically-changing send. Triggered Send Emails inside a Scheduled Automation (C) is a mismatched combination — Triggered Sends are typically driven by individual API/Salesforce events, not scheduled batch dispatch to a whole data extension. For recurring, high-volume, list-based newsletters, Scheduled Automation with a Send Activity is the standard, performant pattern. Reference: Automation Studio Send Activity, Journey Builder vs. Automation Studio Use Cases.