MC-Con-201 Exam Questions Tutorials

Automation event-triggered flow is the current verified answer. Salesforce specifically provides a Form Submission Automation Event that launches an automation event-triggered flow whenever a configured marketing form is submitted. Salesforce describes this flow type as the mechanism for automatically responding to events such as form submissions, subscription activity, orders, and other customer behaviors.

This precisely matches the requirement: the action must occur because the customer submitted a web form. The event can launch the flow, after which the Send SMS Message functionality can deliver the white-paper link, subject to valid SMS consent and channel configuration.

An activation-triggered flow is driven by publication of Data 360 activation data and isn't the direct event architecture for an individual form submission. A standard record-triggered flow reacts to creation or changes of Salesforce records but is no longer the preferred Marketing Cloud Next mechanism when the triggering business event is a supported form submission.

Source distinction: the uploaded bank keys this question as C . However, current Salesforce documentation explicitly states that form-submission automation uses an Automation Event-Triggered Flow , and that this mechanism replaced form-triggered flows. Therefore the current verified answer is B .

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Automation Event-Triggered Flows → Form Submission Events.

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

Salesforce specifically recommends optimizing Run Mode, scheduling frequency, end conditions, and Lookback Window to reduce Data 360 segmentation credit consumption.

Run Mode determines whether a segment publishes automatically or only when requested. During development or testing, Salesforce recommends avoiding unnecessary scheduled publishes. Frequency directly affects how often Data 360 recomputes segment membership; running more often than the source data changes wastes credits. The Ends setting prevents a segment from continuing to execute after the business need has expired.

The Lookback Window is equally important because it controls how much historical data must be evaluated. Narrowing the window to the minimum period required by the use case reduces records processed and therefore processing costs.

The criteria identified in option B affect segment definition and results but don't represent the specific billing-optimization controls Salesforce highlights before processing begins. Option A combines unrelated configuration concepts.

The uploaded source correctly keys C. Salesforce's current billing guidance explicitly names Run Mode, Frequency, Ends, and Lookback Window as settings to optimize for lower segmentation consumption.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Segmentation → Billing Considerations and Credit Optimization.

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

B is the best answer among the available choices , because an Audience Flow with a Data 360 Segment source is the appropriate architecture for a dynamically changing audience. Salesforce states that Data 360 segments update membership based on profile attributes and behavioral data, while Audience Flows can use those segment members as their audience source.

For a "no purchase in 90 days" use case, the marketer defines the lapsed-customer criteria in a Data 360 segment. As purchase data changes and the segment republishes, qualifying customers enter or leave the segment automatically. The Audience Flow then orchestrates the scheduled re-engagement communication against the current membership.

An Automation Event-Triggered Flow is more appropriate for responding to discrete events, such as a form submission or email click. A Marketing Object stores marketing-specific tabular data and isn't a dynamic audience-management mechanism.

The uploaded bank keys B.

Technical precision: the Data 360 feature actually maintaining dynamic membership is the Segment ; Audience Flow is the orchestration layer consuming that segment. Because "Segment" isn't offered as an option, B is the only architecturally valid choice. Salesforce confirms both behaviors.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Dynamic Segments and Audience Flows.

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

A Contact Point Selection Rule implemented through an activation template is specifically designed to determine which email address, phone number, or other messaging contact point should be used when an individual has multiple available values. Salesforce documents activation templates as reusable configurations containing contact point selection, source priority, filtering, enrichment, and membership rules.

For example, an activation template can prioritize a primary CRM email over another email address, filter invalid contact points, and apply consent criteria. Segment-triggered marketing flows can then reference that activation template and use its stored logic to choose one appropriate contact point. Salesforce specifically notes that this capability helps ensure recipients don't receive duplicate messages.

A Decision element isn't intended to reproduce Data 360 contact-point selection logic manually. Identity Resolution also doesn't simply merge multiple legitimate contact points into one. A Unified Individual may correctly retain multiple email addresses belonging to the same person; activation logic determines which address should actually be used.

The uploaded master keys A. Official Salesforce documentation directly supports contact-point selection through activation templates.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Activation Templates → Contact Point Selection.

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