Free Salesforce Marketing Cloud Next Consultant Practice Test Questions

Explanation:
Marketing Cloud Next leverages Data 360 Identity Resolution to unify source profiles into Unified Individuals. To process B2B and B2C audiences independently within the same data space, the consultant should configure Identity Resolution Filters directly on each ruleset. This July 2026 feature allows filtering the data used for matching, enabling separate B2B and B2C unification while keeping the data available for other purposes .

Correct Option:

B. Configure filters on each identity resolution ruleset to separate B2B and B2C customer records:
Identity Resolution Filters are applied only when a specific ruleset runs, allowing you to pre-filter the data used for matching . This enables you to run one ruleset for B2B records and another for B2C records, each unifying only its relevant audience. Critically, filtered data remains available for Segmentation, Calculated Insights, and Data Graphs .

Incorrect Options:

A. Configure separate DMOs for B2B and B2C customers instead of mapping both to the Individual DMO:
Creating separate DMOs would require extensive custom data modeling and is not a supported approach for Identity Resolution. The Individual DMO is the standardized representation of a Person in Data 360, and both B2B and B2C records should map to it for unification . Filtering occurs at the ruleset level, not by creating separate DMOs.

C. Configure filters on the source Data Lake Objects (DLOs) to separate B2B and B2C customer records:
Data Space Filters (applied at ingestion to DLOs) would remove the filtered data entirely, making it unavailable for Segmentation, Calculated Insights, Data Graphs, and even other Identity Resolution rulesets . This approach would break the requirement to keep both audiences available for segmentation and activation.

Reference:

SFMC Tips #314: Marketing Cloud Next: Configuring Identity Resolution Filters

Salesforce Help: Configure Identity Resolution Rulesets for Marketing Cloud Next

Explanation:
Data 360 Identity Resolution is designed to be incremental, not a full reprocessing of all source data on every run. After the initial ruleset run, subsequent runs process only the records that are new or have been modified since the last execution. This significantly reduces credit consumption compared to reprocessing the entire data space, and aligns with Salesforce's guidance to align identity resolution job cadence with actual changes in the data.

Correct Option:

C. Only records that are new or have changed since the previous run:
The ruleset job runs only if source data, object mappings, or the ruleset's configuration has changed since the last run. This incremental approach is intentional: it minimizes credit consumption, since identity resolution is the most expensive Data 360 operation by multiplier. Reprocessing all source records daily would multiply costs unnecessarily.

Incorrect Options:

A. Only records that were created after the previous run:
This is too narrow. The job also processes records that have been updated, not just newly created ones. A change to an existing record's match fields (e.g., email, phone, name) can affect matching and consolidation, so modified records must be included.

B. All source records in the data space:
Processing the entire data space on every run would be prohibitively expensive and unnecessary. Identity resolution uses an incremental model precisely to avoid reprocessing unchanged records, which is why credits are charged based on rows actually processed.

Reference:

Salesforce Help: Run Identity Resolution Ruleset Jobs at Any Time (ruleset runs only if changes detected)

Salesforce Blog: Build a Credit Feedback Loop for Data 360 (align job cadence with actual data changes)

Explanation:
Data Graphs in Marketing Cloud Next require specific key identifier fields from the core DMOs to function correctly. These fields are essential for linking the Unified Individual to the underlying source data and enabling personalization. The Individual ID is the unique identifier, while the Email Address and Telephone Number serve as the primary contact points for message delivery.

Correct Option:

A. Individual ID, Email Address, Telephone Number:
These are the mandatory fields for a standard Data Graph. The Individual ID from the 'Individual' DMO is the primary key that links to the Unified Individual. The Email Address from 'Contact Point Email' and Telephone Number from 'Contact Point Phone' are required to route messages to the correct recipient channels.

Incorrect Options:

B. Unified Individual ID, Email Address from 'Individual', Telephone Number from 'Individual Object':
The field source mappings are incorrect. Email addresses are not stored directly on the 'Individual' object but rather on the 'Contact Point Email' DMO. Similarly, phone numbers reside on the 'Contact Point Phone' DMO. The Unified Individual ID is not the standard field used for personalization setup.

C. Unified Individual Link ID, Email Address, Telephone Number:
The Unified Individual Link ID is an incorrect identifier for the primary Data Graph configuration. The required field is the Individual ID from the 'Individual' object, which the Unified Link Individual bridges to the Unified Individual. Using the Link ID would not properly establish the necessary connection for personalization.

Reference:

Salesforce Help: Standard Data Graph Requirements

Salesforce Trailhead: Explore Data Sources for Email Personalization

Explanation:
Identity resolution is the single most expensive operation in Data 360, consuming credits at a dramatically higher multiplier than most other functions. Even after optimizing the number of rows processed, the frequency at which rulesets run can still drive significant consumption. Disabling automatic job execution allows the consultant to control when rulesets run, preventing unnecessary credit burn from scheduled or triggered executions.

Correct Option:

A. Disable "Run jobs automatically" on the identity resolution rule(s):
Identity resolution consumes credits each time a job runs, processing all source profiles that have changed since the last execution. By disabling automatic runs, the consultant can manually trigger jobs only when sufficient data changes have accumulated or when unified profiles are actually needed for a business process. This directly reduces the number of billable processing events without affecting data quality or completeness.

Incorrect Options:

B. Maintain multiple active rulesets per primary Data Model Object (DMO) per data space:
This approach would increase credit consumption, not reduce it. Each active ruleset processes data independently, and having multiple rulesets running against the same DMO would multiply the volume of records processed. Best practice is to consolidate into a single, well-designed ruleset per primary DMO to avoid redundant processing.

C. Delete and recreate data streams to remove unused records:
Data streams are ingestion pipelines, not storage containers. Deleting and recreating them would not reduce identity resolution costs and would actually trigger reprocessing of all data upon recreation. Credit consumption is driven by records processed during ruleset runs, not by the presence of unused records in streams. Filtering data before ingestion is the correct approach, not stream recreation.

Reference:
Salesforce Trailhead: Unify Your Data with Effective Identity Resolution Strategies (Run jobs automatically disabled to reduce costs)

Salesforce Blog: Build a Credit Feedback Loop for Data 360 (ruleset runs only if changes detected; align cadence with actual data changes)

Explanation:
The required fields ('Total Items' and 'Category Name') do not exist in the raw ecommerce order data, so they must be derived through aggregation and transformation. In Data 360, Calculated Insights are the native feature designed to compute aggregate metrics (like total purchases) across related records and write those results back to a DMO, typically the Unified Individual profile. This makes the computed values available as attributes for personalization in emails.

Correct Option:

B. Calculated Insight:
Calculated Insights use SQL-like definitions to aggregate measures across related DMOs and persist the results on the Unified Individual DMO . The insight can compute the total number of items purchased (aggregate) and determine the favorite category by grouping and ranking purchase volume per category . Once processed, these metrics become available as Data Graph attributes and can be inserted into emails as merge fields.

Incorrect Options:

A. Streaming insight:
Streaming Insights process real-time event data as it arrives, but they are optimized for immediate, time-windowed metrics (e.g., "purchases in the last 7 days") rather than full historical aggregates like "total items purchased to date." A streaming insight would not efficiently compute the cumulative lifetime total or the all-time favorite category, and it is not the standard tool for these derived attributes.

C. Custom formula field on the Unified Individual DMO:
Data 360 does not support creating ad-hoc formula fields directly on DMOs using standard SQL aggregate functions. Deriving aggregate metrics from related records requires the Calculated Insight framework, which handles the processing, scheduling, and writing of computed values to the target DMO. A simple formula field cannot perform cross-object aggregation.

Reference:

Salesforce Help: Calculated Insights in Data 360

Trailhead: Create Calculated Insights (Aggregate measures across related DMOs, write to Unified Individual)

The Agentic Marketer: Data 360 Calculated Insights for Marketing Personalization