Salesforce MC-Con-201 - Salesforce Certified Marketing Cloud Next Consultant

Handlebars QueryFirst is the current Marketing Cloud Next-native solution for retrieving a single matching record dynamically from a marketing object. Salesforce introduced this helper in the Summer '26 Marketing Cloud Next release. The function can query CRM objects, marketing objects, or Data Graphs and return the first record matching defined criteria.

For this scenario, the marketing object contains multiple localized promo codes. The email needs only the promo code whose region matches the recipient's Region_Code. QueryFirst can specify the marketing object, desired promo-code field, and a where condition using the recipient's region as a parameter. The returned object can then be referenced directly in Handlebars personalization.

AMPscript is associated primarily with Marketing Cloud Engagement and isn't the preferred Marketing Cloud Next content-personalization language for this use case. Standard cross-object merge-field notation also doesn't dynamically query an unrelated marketing-object record based on arbitrary matching criteria.

The uploaded bank correctly keys B. Salesforce's developer documentation explicitly states that QueryFirst retrieves the first matching record from marketing objects, Sales Cloud, or Data Graphs.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Handlebars Personalization → QueryFirst and Marketing Objects.

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

An On-Demand Flow invoked through the REST API is specifically designed for externally initiated, real-time automation in Marketing Cloud Next. Salesforce supports triggering this flow type by calling the Flow invocable-action REST endpoint. Input variables can be supplied with the request and then used by downstream flow actions.

That architecture is ideal for a one-time verification code. The external authentication service generates the code, calls the Marketing Cloud Next on-demand flow, passes the code and recipient information as input values, and the flow immediately uses those values in the Send Email Message action.

There is no reason to persist an ephemeral security value such as a one-time code into Data 360 merely so it can be read back by a Data Graph. Doing so adds ingestion and synchronization latency. Similarly, waiting for an Automation Event-Triggered Flow to detect streamed data introduces unnecessary infrastructure when the external system already knows exactly when the message must be sent.

The uploaded bank correctly keys C. Salesforce's On-Demand Flow release documentation explicitly states that REST API calls can trigger this flow type for externally initiated marketing interactions.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → On-Demand Flows → REST API Invocation and Runtime Personalization.

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

A Calculated Insight is designed for aggregations across multiple Data 360 records. The requested values aren't simple attributes stored on one ecommerce order. "Total Items" requires aggregation across the customer's purchase history, while "Favorite Category" requires grouping purchase activity by category and identifying the dominant result.

Salesforce Calculated Insights support aggregate metrics such as sums and counts together with dimensions that enable more granular analysis. Salesforce also supports calculated insight metrics in activations and downstream personalization scenarios.

A streaming insight is unnecessary because the campaign runs monthly and doesn't require second-by-second recalculation. Using a standard formula field as proposed in C also doesn't solve multi-record ecommerce aggregation: formula expressions aren't a substitute for analytical rollups across transaction history.

The uploaded source keys B. One wording issue exists in option B: it says "aggregate the purchase volume for the account," while the scenario ultimately requires values associated with each Unified Individual. The underlying architectural principle remains correct—use a Calculated Insight grouped appropriately to the customer/profile dimension.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Calculated Insights → Metrics, Dimensions, and Aggregations.

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

C is the current verified answer. Salesforce's current Marketing Performance Intelligence setup documentation states that turning on the capability requires Marketing Cloud Admin AND Data Cloud Architect permission sets. In the terminology used by this question, Data Cloud Architect corresponds to Data 360 Architect .

The Tableau Next Included App Business User permission set is important, but Salesforce distinguishes its purpose: it is required for users who need to view Marketing Performance Intelligence dashboards and embedded assets , rather than being the complementary administrative permission required to enable the feature itself. Salesforce's Tableau Next documentation confirms that this permission permits viewing included-app assets.

Data 360 Activation Manager focuses on activation operations and doesn't provide the architectural setup permissions required for Marketing Performance Intelligence.

The uploaded master bank keys this item as B. That key conflates dashboard-viewing permission with setup permission. Under current Salesforce documentation, the question's wording— "required to enable Marketing Performance" —makes C the correct answer.

Study Guide Reference: Analytics and Performance Insights → Marketing Performance Intelligence → Setup Permissions.

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

The Marketing Cloud Engagement Business Unit containing the Journey must be mapped to the Data Space in which the Marketing Cloud Next flow operates . Salesforce explicitly lists this mapping as a prerequisite for a Journey to appear as a selectable destination in the Send to Journey action. This ensures that the source audience, activation/contact-point configuration, and destination Journey operate within the correct data and organizational context.

Salesforce also requires the selected Journey to be active and to use an API Event as its entry source. Consequently, option B is incorrect because a Salesforce Data Entry Source isn't the required Journey entry mechanism for Send to Journey. Option C is also incorrect because the integration isn't dependent on the flow being record-triggered. Salesforce supports Send to Journey from the applicable marketing-flow architecture.

Activation templates can provide reusable contact-point-selection logic. However, that contact-point configuration doesn't remove the prerequisite relationship between the flow's Data Space and the Marketing Cloud Engagement Business Unit that owns the Journey.

The uploaded master bank identifies A. Salesforce's current Send to Journey documentation confirms the Business Unit-to-Data Space mapping and API Event requirement.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Marketing Cloud Engagement Journeys → Send to Journey and Activation Templates.

A Marketing Object is the most efficient solution when marketers have standalone structured data that is needed for personalization but doesn't need to become part of the enterprise Data 360 customer model. Salesforce allows users to create a Marketing Object directly by uploading a CSV file. The platform creates the object and loads the data in a single operation, automatically inferring supported field types from the uploaded columns.

Salesforce specifically describes Marketing Objects as appropriate for product information, reference data, content variations, and personalized campaign data . The information stored in them can then be retrieved from Marketing Cloud Next content by using Handlebars or AMPscript.

Creating a CRM custom object introduces unnecessary CRM configuration for data that exists only to support a one-time marketing campaign. Similarly, creating a Data 360 data stream and mapping it to a DMO adds ingestion, mapping, processing, and governance overhead that isn't justified by this isolated personalization requirement.

Therefore, A provides the simplest marketer-controlled architecture while maintaining the data in Marketing Cloud Next.

The uploaded master bank also keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Marketing Objects → CSV Import and Message Personalization.

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

Salesforce explicitly documents the required Data Graph structure and fields for Marketing Cloud Next personalization. The Data Graph should use Unified Individual as its primary DMO and include the appropriate relationship chain through Unified Link Individual and Individual to the applicable contact-point objects.

Within that structure, Salesforce specifically requires these fields:

Individual ID from the Individual object,

Email Address from Contact Point Email, and

Telephone Number from Contact Point Phone.

These identifiers allow Marketing Cloud Next to resolve personalized profile information to the proper communication contact points when rendering email and SMS content.

Option B incorrectly locates email address and telephone number directly on the Individual DMO. Those values belong to their dedicated contact-point DMOs. Option C incorrectly substitutes the Unified Individual Link ID for the required Individual ID.

This answer has particularly strong current documentation support: Salesforce published a dedicated Marketing Cloud Next knowledge article on March 12, 2026 listing exactly these three required fields. The uploaded master bank also keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graphs → Required Personalization Relationships and Fields.

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

The critical word is initial . Marketing Cloud Next Business Units provide organizational separation for regions, brands, product lines, or other marketing divisions, but their data isolation is enforced through Data 360 Data Spaces. Salesforce establishes a one-to-one relationship between a Business Unit and a Data Space: a Business Unit can map to only one Data Space, and that Data Space can't be associated with another Business Unit.

More importantly, Salesforce's Business Unit setup instructions specify that before creating the initial Business Units, the organization must already have two or more Data Spaces . Therefore, for North American and European environments requiring segregation, the consultant first establishes the separate Data Spaces. The Business Units can then be created and mapped to those unique Data Spaces, with their associated marketing workspaces and content.

Option B represents an important subsequent configuration but isn't the prerequisite initial step. Option C addresses content organization but by itself doesn't establish the required data boundary.

The master bank likewise identifies A.

Study Guide Reference: Platform Setup and Governance → Business Units in Marketing Cloud Next → Data Spaces and Business Units.

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

An Identity Resolution ruleset is the Data 360 component responsible for linking source profiles from different systems into unified customer profiles. A ruleset contains match rules and reconciliation rules that govern the unification process.

Match rules determine whether records from CRM, ecommerce, loyalty, or other systems represent the same person by comparing attributes such as names, normalized email addresses, telephone numbers, party identifiers, device identifiers, or other matching criteria. When records satisfy a match rule, Data 360 associates them with the same Unified Individual.

Reconciliation rules perform a different but complementary function: after records are matched, they determine which source value should represent single-valued unified attributes such as First Name.

A Data Graph doesn't perform entity resolution. It exposes primary and related data efficiently for personalization or other consumption use cases after the underlying model exists. An Audience Flow orchestrates communications to an audience; it doesn't unify identities.

The uploaded bank correctly identifies B. Salesforce's official Identity Resolution documentation confirms that rulesets contain match and reconciliation rules that link multiple source profiles into unified profiles.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Rulesets, Match Rules, and Reconciliation Rules.

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

The Data 360 Profile Insights component is Salesforce's prescribed component for surfacing marketing scores directly on relevant CRM record pages. Salesforce explicitly states that administrators can add this component to Lead and Contact pages and configure it to display Overall Marketing Score, Marketing Engagement Score, and Marketing Fit Score .

This gives sales users an immediate, contextual indication of marketing readiness and engagement without requiring them to open a separate report or dashboard. These scores can help sales teams identify which leads or contacts have the greatest likelihood of engagement or conversion.

A custom report isn't the intended embedded scoring experience and adds unnecessary reporting overhead. Unified Engagement History serves a different purpose: it surfaces historical marketing interactions such as email or web engagement. It isn't the component used to display the calculated Overall Marketing Score.

The uploaded source identifies B.

The file wording includes prospects in addition to leads and contacts. Current Salesforce scoring documentation most explicitly describes the Profile Insights component on Lead and Contact record pages; the source supplies the broader exam framing.

Study Guide Reference: Analytics and Performance Insights → Marketing Scoring → Data 360 Profile Insights.

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