Salesforce Updated MC-Con-201 Exam Questions and Answers by forest

The correct reconciliation strategy is Source Sequence , also described in newer Salesforce materials as Source Priority . This rule lets the consultant rank source systems from most trusted to least trusted when Data 360 must select a single representative value for a unified profile attribute.

In this scenario, Salesforce CRM has already been identified as the authoritative source for First Name. The consultant therefore places the CRM source first in the reconciliation priority. When a CRM value exists, Data 360 selects that value instead of choosing one from a lower-priority ecommerce, loyalty, or external source.

Most Frequent would select whichever value occurs most often among the linked records. That doesn't satisfy the requirement because multiple unreliable sources could outweigh the single trusted CRM value. A custom approach isn't required when source prioritization directly addresses the business rule.

The uploaded master bank identifies B. Salesforce Trailhead still describes this reconciliation method as Source Sequence , while current Help and architecture materials commonly use Source Priority for the same source-ranking concept.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Reconciliation Rules → Source Sequence/Source Priority.

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

An Event Data Provider is appropriate because the email is triggered by a discrete event—specifically, a landing-page form submission—and the email must use values contained in that event payload. Salesforce categorizes Event as a supported Marketing Cloud Next personalization data source and describes events as activities such as order confirmations and subscription signups that trigger flows.

A form submission can launch an Automation Event-Triggered Flow. Data associated with the triggering event can then be exposed to message content through the Event Data Provider, allowing submitted values such as first name, selected product, event choice, or form responses to appear as merge fields.

A Data Graph is better suited to persistent profile and related Data 360 information. It isn't necessary when the desired values are already available from the triggering event. Activation Data Provider is used when personalization attributes come from a Data 360 segment activation.

Salesforce documentation demonstrates the same pattern: event-triggered emails can use event values through Event Data Provider merge fields. The uploaded bank keys A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Event-Triggered Marketing → Event Data Provider Personalization.

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

The consultant should configure the Audience Flow to republish the segment immediately before the flow executes . Salesforce specifically provides this option to ensure that a segment-based flow works from the latest available membership rather than whatever population happened to exist after the previous scheduled publication.

Salesforce's Segment Flow guidance states that marketers should consider segment publication timing and, when the most current data is required, select republish the segment immediately before running the flow . Salesforce's segmentation documentation further explains that this setting adds a publication immediately before flow execution, independently of the segment's ordinary publication schedule.

A fixed Wait element is unreliable because segment processing duration can vary with data volume and other Data 360 workloads. Scheduling the flow and segment at exactly the same time makes the race condition worse rather than solving it.

Salesforce has also documented cases where segment-triggered flows can complete without correctly processing members when segment publication isn't synchronized; republishing at runtime resolves the issue.

The uploaded master correctly identifies C.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Audience Flows → Segment Publication and Immediately-Before-Run Refresh.

An activation-triggered flow requires an activation whose Activation Target type is Data 360 . Salesforce explicitly states that activation-triggered flows support only activations created with Data 360 as the activation target type. Although Flow Builder may display activations associated with other target types, selecting an unsupported type results in an error when the flow is saved.

The sequence is therefore: create or publish the target audience segment, create a Data 360 activation target , configure an activation that publishes the segment to that target, and then create an activation-triggered flow using that activation. When the activation completes, records are written into the Audience DMO and the associated flow starts automatically. Salesforce's Data 360 activation-target documentation confirms this architecture.

"Segment" isn't itself an Activation Target type; it is the audience being activated. Loyalty similarly isn't the required target for this Flow architecture.

The uploaded question bank correctly keys option A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Activation-Triggered Flows → Data 360 Activation Targets.

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