Free Practice Questions for Salesforce MC-Con-201 Exam

The Activation data provider is specifically designed to expose attributes from a Data 360 segment activation to Marketing Cloud Next email content. Salesforce states that the Activation data provider references a Data 360 segmentation activation and makes its recipient attributes available as merge fields.

That directly fits the scenario. If the activation includes a calculated attribute such as Loyalty Tier, the marketer can add the Activation data provider to the email and reference that attribute during personalization.

A Data Graph is appropriate when the email needs profile attributes or related Data 360 data that isn't already part of the activation. It isn't necessary merely to expose attributes already included in the activation payload. An Apex Class is used when custom runtime code or complex external data retrieval is required; neither condition exists here.

This question is importantly different from the earlier runtime-value scenario: Activation is appropriate when the value actually comes from Data 360 activation data. A manually supplied campaign value would instead call for a Content Variable.

The uploaded bank correctly identifies A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization Data Providers → Activation.

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

Option A applies the least computationally intensive feature appropriate to each requirement. Days Since Last Login is fundamentally a row-level derived value based on an existing login-date attribute, so a Data 360 data-stream formula can derive a supplemental field without requiring an analytical aggregation pipeline. Salesforce supports formula fields derived from other fields, functions, and operators during data-stream processing.

Loyalty Tier based on lifetime spend , however, requires aggregation across potentially many transaction records for each customer. A batch calculated insight is designed for that type of multi-record calculation. Because the email is monthly, a daily batch calculation is adequate; there is no business need to pay the higher processing cost associated with streaming computation.

Streaming calculated insights consume Data 360 Streaming Pipeline Flex Credits based on processed records. Batch calculated insights are billed under Data 360 Prep according to underlying records processed. Therefore, unnecessary streaming should be avoided when sub-second freshness isn't required.

A formula-field caveat is that Salesforce recalculates a data-stream formula when the corresponding record is refreshed or changed, so implementation scheduling must ensure the value is sufficiently current for the monthly send.

The master bank keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data 360 Calculations → Formula Fields, Calculated Insights, and Credit Optimization.

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

Data 360 supports source-record filters directly on identity resolution rulesets . These filters act as preprocessing gates that determine which records from the ruleset's primary DMO enter that particular unification pipeline.

This is exactly the appropriate architecture when two populations share the same primary DMO but must be unified independently. The consultant can configure criteria distinguishing B2B from B2C records and apply complementary filters to the respective rulesets.

Salesforce specifically identifies separation of B2B and B2C populations as a valid ruleset-filter use case. For example, records can be filtered using an account type, customer type, record type, or other partition-level attribute so that business records don't enter the consumer ruleset and vice versa.

Creating separate DMOs simply to achieve identity-processing isolation isn't necessary when the records properly belong to the same canonical Individual model. Filtering source DLOs also places the separation at the wrong architectural layer because identity-resolution filtering is supported directly at the ruleset level.

The uploaded bank keys B. Salesforce's current ruleset documentation explicitly recommends filters for broad partition-level segregation, including B2B versus B2C scenarios.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Ruleset Source Filters.

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

Salesforce provides the Device to Known Identity Resolution rule specifically to associate anonymous tracked visitors with known Unified Individual profiles.

Current Marketing Cloud Next setup documentation states that an Individual Identity Resolution ruleset should include an Identity Match DMO match criterion where Identity Match Type is matched exactly to device-to-known. Salesforce explains that this recommended rule attributes web-tracking activity to the correct Unified Individual.

This architecture exists because anonymous website engagement initially contains a device or visitor identity rather than ordinary CRM identity attributes. Once the visitor becomes identifiable—for example, through a recognized interaction—the Identity Match relationship enables Data 360 to stitch that visitor identity to the known Individual.

Option A incorrectly proposes manually altering identity relationships with Flow. Option B assumes Website Engagement should be directly matched to Individual using email, which bypasses the specialized identity-stitching mechanism Salesforce provides.

The uploaded master bank identifies C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Identity Match DMO and Device-to-Known Matching.

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

The agency users need the Marketer-Standard Business Unit role because their responsibilities include both creating marketing assets and deploying campaigns.

Salesforce states that users with the Marketing Cloud Admin or Marketing Cloud Manager permission set can be added to a Business Unit as Marketer-Standard members. These users receive the Content Manager role in the Business Unit's marketing workspace, allowing them to create, edit, view, and publish content. They can also activate campaign flows in that Business Unit.

Marketer-ReadOnly is insufficient because Salesforce explicitly states that ReadOnly members can't activate campaigns and don't receive access to the Business Unit's marketing workspaces. This would prevent the agency from performing the tasks described.

Adding users directly to the Data Space isn't the proper Marketing Cloud Next access-governance model. Business Unit membership automatically grants access to its mapped Data Space according to the Business Unit architecture.

The source bank correctly identifies C.

Study Guide Reference: Platform Setup and Governance → Business Units → Marketer-Standard and Marketer-ReadOnly Roles.

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

Handlebars is the appropriate method because the scenario specifically requires conditional logic against values supplied by the Data Graph. Marketing Cloud Next's Handlebars implementation provides comparison and control helpers such as if, else if, equals, compare, and, or, and iif. These functions allow message content to change according to profile values such as Loyalty Tier or Points balance.

Marketing Cloud Next exposes the profile Data Graph through Handlebars, allowing deeply related profile attributes to be referenced and evaluated programmatically. Salesforce's developer documentation describes $dataGraph as the profile data graph loaded with marketing content and shows how nested attributes can be traversed.

Simple merge fields are appropriate when the requirement is only to print an attribute. They don't by themselves provide the richer branching logic requested here. Dynamic content variations can also implement marketer-configured targeting, but when the explicit requirement is conditional expression logic against Data Graph values, Handlebars is the more direct technical answer.

The uploaded source keys B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization → Handlebars Conditional Logic and Data Graph Data.

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

The administrator needs the Marketing Cloud Admin permission set to manage Business Unit membership. Salesforce's Business Unit setup documentation specifies Marketing Cloud Admin as the permission required for Business Unit administrative operations, while Business Unit members themselves can have either Marketing Cloud Admin or Marketing Cloud Manager depending on their job responsibilities.

When adding users, the administrator opens the Business Unit, selects Add Users , chooses the eligible users, and assigns either the Marketer-Standard or Marketer-ReadOnly role. Salesforce confirms that Marketer-Standard users must already have Marketing Cloud Admin or Marketing Cloud Manager.

There isn't a standard Marketing Cloud Next permission set named Business Unit Admin corresponding to option C. A System Administrator profile provides broad Salesforce administrative capability but, for the Marketing Cloud Next Business Unit feature, Salesforce specifically identifies the Marketing Cloud Admin permission set as required.

The uploaded source also keys A.

The distinction is important: Business Unit membership roles control what marketers can do inside a BU, while Marketing Cloud Admin provides the administrative authority to configure and manage Business Units.

Study Guide Reference: Platform Setup and Governance → Business Units → User Membership and Administrative Permissions.

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

The uploaded bank keys C , which places the automation at the layer where the actual email-click engagement exists: Data 360 engagement data.

Current Salesforce documentation supports the core architecture. Create Consent is supported in Data Cloud/Data 360-triggered flows and can be used to automate consent updates based on behavioral data such as a link click . Salesforce explicitly describes link clicks and form submissions as valid sources for automated Create Consent processing.

The original CRM Lead record doesn't itself become updated merely because an email engagement event occurred, so a conventional Lead record-triggered flow is an unreliable trigger for this behavior. A Data 360-triggered flow can instead react to the appropriate engagement DMO event and pass the relevant sending contact point into Create Consent.

The source specifically identifies the Email Engagement DMO, click criteria, link URL, and Send time Email Address fields. Those exact field-level details are source-derived; current public Salesforce documentation independently confirms the broader Data 360-triggered + Create Consent pattern.

Study Guide Reference: Consent → Behavioral Consent Automation → Data 360-Triggered Flow and Create Consent.

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

Marketing Cloud Next requires an authenticated sending domain for branded email delivery. The domain is configured under Unified Messaging and authenticated through DNS records supplied by Salesforce. DKIM is a core part of this authentication process.

Salesforce states that Marketing Cloud Next uses Unified Messaging for outbound email and that an activated authenticated domain is required for email sending. Current Marketing Cloud Next DKIM keys are 2048-bit by default, and Salesforce uses outbound CNAME records to establish the DKIM authentication chain. Once the domain is active, From addresses using that domain can be configured for legitimate branded delivery.

A tracking domain serves a different purpose: it supports branded links, redirect tracking, or related channel tracking functionality. It doesn't substitute for the authenticated email-sending domain. An "Authorized domain" verified solely by an ownership TXT record isn't the Marketing Cloud Next sending-domain configuration described by Salesforce.

The uploaded bank correctly identifies A. Salesforce's May and August 2026 documentation confirms that an authenticated domain is mandatory for Marketing Cloud Next sending and that DKIM authentication uses generated DNS records.

Study Guide Reference: Platform Setup and Governance → Unified Messaging Setup → Authenticated Sending Domains and DKIM.

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