Practice Free MC-Con-201 Salesforce Certified Marketing Cloud Next Consultant Exam Questions Answers With Explanation

Conversational Email is explicitly designed for two-way email interactions in Marketing Cloud Next. Salesforce states that customers can reply directly to outbound emails and that the platform evaluates those replies to determine intent. The resulting conversation can then trigger automated actions, route to an Agentforce agent, or escalate to a human representative while maintaining the original email thread and conversation context.

This precisely matches the requirement for order-notification replies. Salesforce also integrates Conversational Email with Agentforce, Digital Engagement, Service Cloud, Omni-Channel, and Data 360 , allowing AI handling and seamless human escalation. Human representatives can access the complete conversation history when an Agentforce agent escalates the interaction.

Reply Mail Management isn't the complete solution for an AI-driven, contextual conversational experience. Engagement Scoring is predictive marketing functionality based on engagement behavior; it doesn't analyze free-form customer email replies for service intent.

The uploaded document correctly identifies B. Salesforce's current Conversational Email documentation explicitly describes intent analysis, AI/human routing, and contextual thread preservation.

Study Guide Reference: Agentforce and AI Innovation ? Conversational Email ? Agentforce and Human Escalation.

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

The source bank identifies B because Marketing Cloud Next Business Units establish organizational boundaries not only for data but also for marketing workspaces and content.

Current Salesforce documentation supports this architecture. Each Business Unit has one or more marketing workspaces, and a workspace is assigned within that Business Unit's configuration. When Business Units are created, a default marketing CMS workspace is assigned to each unit. Consequently, content created only inside the corporate Business Unit's workspace doesn't automatically become available as reusable content to marketers working within other Business Units.

Salesforce provides Common Assets specifically to solve the cross-Business-Unit distribution problem. Content from one workspace can be posted to Common Assets, after which members of other Business Units can copy the approved asset into their own workspace.

Adding regional users as contributors to the corporate workspace would weaken the intended Business Unit governance model. Publishing an asset within the corporate workspace also doesn't automatically distribute it across Business Units.

Study Guide Reference: Platform Setup and Governance ? Business Units ? Marketing Workspaces and Cross-Business-Unit Content Governance.

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

A Salesforce CRM connector in Data 360 is a foundational prerequisite for bringing CRM data into Marketing Cloud Next. Salesforce's setup documentation lists creating a Salesforce CRM connector as one of the required tasks during initial Marketing Cloud Next configuration. The Sales Data Kit then deploys CRM data streams for objects such as Accounts, Contacts, Leads, and Opportunities.

An Identity Resolution ruleset isn't required before deploying the Sales Data Kit. In fact, Salesforce explains that deploying the Sales Data Kit provides a faster path to subsequently building Identity Resolution rulesets because the required CRM objects and mappings are already available.

Option C is plausible in a generic deployment failure, because deployment does require System Administrator plus Data Cloud Architect and Marketing Cloud Admin permissions. However, the question's provisioning context and guided deployment dependency point specifically to the missing CRM connector. The master bank likewise identifies B.

Therefore, before deploying the Sales Data Kit, the consultant should ensure Data 360 is enabled and its Salesforce CRM connector has been established.

Study Guide Reference: Platform Setup and Governance ? Marketing Cloud Next Setup ? CRM Connector and Sales Data Kit Deployment.

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

A Data 360-triggered flow is the more precise event-driven architecture when the automation should respond to a change in a Calculated Insight Object (CIO). Salesforce explicitly supports Data 360-triggered flows based on changes in either DMOs or calculated insights. The flow can define entry conditions so that it fires when the calculated value changes into the target state—for example, when Churn Risk = High.

This design avoids waiting for an independently scheduled audience-segment publication cycle. Data 360 change processing generates the triggering event after the calculated insight is recalculated and the record satisfies the configured conditions. Salesforce states that Data 360 data actions and triggered flows can react to CIO changes in near real time after the underlying calculation completes.

Option C is incorrect because a normal CRM record-triggered flow isn't the proper trigger type for a Data 360 calculated insight object. Option A can support scheduled re-engagement campaigns, but it introduces segment publication scheduling when the requirement explicitly centers on the moment the insight changes.

The uploaded bank keys A. Current Salesforce documentation directly supports CIO-triggered Data 360 flows, making B the stronger current answer .

Study Guide Reference: Campaign Design, Flow Orchestration and Content ? Data 360-Triggered Flows ? Calculated Insight Changes.

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

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 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.

An Apex Class data provider is the appropriate solution when personalization requires custom runtime logic and data that isn't already available in Data 360. Salesforce supports Apex Class as a personalization data source for both email and SMS content.

The Apex data provider enables custom Apex logic to supply simple or complex values to the marketing message at runtime. This is especially relevant when an external system must be queried, proprietary calculations must be executed, or structured data must be assembled immediately before rendering the message.

A Data Graph would require the relevant information to already exist within Data 360 or be represented through its associated DMOs. That contradicts the requirement that the external information isn't stored there. An Event data provider works well when the triggering event itself contains all required values, but the question specifically states that a complex calculation against external system data must occur at send time. That requirement calls for executable server-side logic rather than simple event-payload personalization.

The uploaded bank keys C. Salesforce explicitly documents Apex Class as a supported data provider for personalized Email and SMS and notes that it can supply complex structured data.

Study Guide Reference: Campaign Design, Flow Orchestration and Content ? Advanced Personalization ? Apex Data Providers.

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

Salesforce explicitly lists an important limitation for the Marketing Cloud Next Prospect object: a prospect can't directly be added to a Salesforce Campaign as a Campaign Member. Campaign Member relationships use supported CRM person records, principally Leads and Contacts. Therefore, if the business process requires an actual Campaign Member record, the prospect must first be converted or otherwise represented as a supported Lead or Contact.

This doesn't mean prospects are unusable for marketing. Marketing Cloud Next can ingest and manage prospects, create related Individual records in Data 360, include them in Unified Individual processing, score them, segment them, and nurture them. Salesforce also supports converting qualified prospects into Leads or Contacts when they reach the appropriate stage.

Option B is incorrect because using an Audience Flow doesn't remove the underlying Campaign Member object limitation. Option C is also incorrect; activating the campaign doesn't change the supported record types for Campaign Members.

The uploaded master bank keys A. Salesforce's current Prospect considerations explicitly state that a Prospect can't be added to a campaign as a campaign member.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation ? People Records ? Prospects, Leads, Contacts, and Campaign Members.

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

A Salesforce campaign represents the broader marketing initiative, while individual flows implement the distinct automated experiences that contribute to that campaign. Therefore, one overarching product launch should be represented by one campaign containing three related flows .

Salesforce explicitly states that each campaign can relate to multiple flows. The Campaign record provides a consolidated view of the associated flow automations, assets, status, and campaign-level engagement information. This allows marketers to evaluate the overall product-launch initiative while still maintaining separate automation logic for each customer trigger.

Combining three fundamentally different triggered sequences into a single flow would make the automation unnecessarily complex and wouldn't reflect the logical separation of customer behaviors described in the scenario. Conversely, creating three independent campaigns would fragment what the business explicitly considers one coordinated product-launch initiative.

Salesforce's campaign-stage functionality also evaluates the states of all flows associated with a campaign, further confirming the one-to-many relationship between campaigns and marketing flows.

The uploaded question bank identifies C. Salesforce documentation confirms that a campaign can contain multiple flows and provides campaign-level information across those flows.

Study Guide Reference: Campaign Design, Flow Orchestration and Content ? Campaign Architecture ? Campaign and Flow Relationships.

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

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 correct data source is Event because the required Order Number belongs to the purchase event that initiated the marketing interaction. Marketing Cloud Next supports Event as a personalization data source for Email, SMS, and WhatsApp messages . Event-based personalization makes attributes carried by the triggering event available as merge fields within the message.

In this scenario, when the purchase occurs, the triggering event contains contextual transaction information such as the Order Number. The WhatsApp template can reference that event attribute directly without requiring the value to be separately persisted and retrieved through a Data Graph.

A Data Graph is more appropriate when personalization requires persistent customer-profile information or attributes from related Data 360 objects. A Salesforce Record source is appropriate when the content specifically needs fields from a CRM record supplied to the personalization context. Neither is necessary when the desired information originates directly from the event that triggered the message.

The uploaded master bank identifies option C. Salesforce's personalization reference confirms that Event is supported for WhatsApp and can supply event-based attributes to marketing content.

Study Guide Reference: Campaign Design, Flow Orchestration and Content ? Content Personalization ? Event Data Sources and WhatsApp Messaging.

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

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.

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

Aggregations and Container Paths are required when segment criteria depend on records from a related DMO with a one-to-many relationship to the segmentation entity. Salesforce explains that aggregations allow marketers to evaluate related-record quantities, such as identifying individuals with at least one order or customers with five or more purchases. In this scenario, the consultant needs an aggregation equivalent to a purchase count greater than or equal to one.

Containers group attributes from related DMOs so that their conditions are evaluated within the correct relationship context. When more than one relationship exists between the related DMO and the segmentation entity, the Container Path tells Data 360 which relationship path to traverse. Salesforce specifically advises verifying the container path when multiple paths are available.

Publish Type relates to how or when segment membership is published; it doesn't establish the relationship or aggregation logic needed to evaluate multiple purchase records. Therefore, options B and C omit one of the essential segmentation concepts.

The uploaded master bank also identifies option A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation ? Segmentation ? Containers, Container Paths, and Aggregations.

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

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 problem isn't merely the batch schedule; the implementation is using an unsupported consent-write path . Salesforce's August 2026 Marketing Cloud Next guidance explicitly warns against using Data 360 batch transforms, streaming transformations, direct data-stream mappings, or bulk APIs to write directly into the Communication Subscription Consent DMO. Those methods can produce consent values that appear stored but aren't consistently honored by the messaging consent layer at send time.

The supported solution is to route the change through Create Consent/Consent Request . A Data 360-triggered flow can listen for the relevant change and invoke Create Consent, which updates the contact point's consent for the required channel and communication subscription through the supported consent service.

Therefore, changing a daily batch to hourly doesn't fix the architectural defect. Switching from batch to streaming transformation also doesn't make a direct DMO write supported.

The master bank correctly identifies B. Salesforce explicitly recommends reissuing incorrectly written consent through a Data 360-triggered flow calling Create Consent.

Study Guide Reference: Consent ? Supported Consent Write Methods ? Create Consent Action and Data 360-Triggered Flows.

Among the available choices, A is the intended Advanced-edition capability. Standard content creation is a core Marketing Cloud Next capability available in both Growth and Advanced editions, so C doesn't require Advanced. Standard Salesforce reporting likewise isn't inherently restricted to Marketing Cloud Next Advanced, eliminating B.

The edition distinction becomes important for account-oriented marketing capabilities. Salesforce's current implementation documentation identifies Account scoring as an Advanced Edition capability and requires identity resolution for both Individual and Account objects before configuring people-and-account scoring. This is why account-level identity infrastructure appears in Advanced-focused implementation scenarios.

There is an important technical nuance: Salesforce's general Identity Resolution documentation describes creating custom rulesets for either Individual or Account and doesn't independently state, in the current public article, that merely creating an Account ruleset is universally Advanced-only. The Advanced restriction is explicitly documented around the account-oriented scoring capability that depends on that ruleset. Within the supplied options and certification context, however, A is the valid answer ; B and C are clearly Growth-supported functionality.

The master bank also keys A.

Study Guide Reference: Platform Setup and Governance ? Editions and Feature Availability ? Growth vs. Advanced.

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

The appropriate solution is a Lightning Report based on the Marketing Performance Semantic Data Model . Salesforce's marketing reporting architecture provides semantic-model-backed report types that combine message-definition and engagement information into a unified reporting layer. The Marketing Performance Semantic Model specifically contains information about message send definitions and engagement data, allowing marketers to create detailed custom analytics instead of being limited to predefined dashboards.

This is important because unsubscribe information and unsuccessful message delivery are engagement-level events rather than ordinary Campaign Member attributes. A Campaign Member-based custom report therefore lacks the complete messaging and engagement model required for this analysis. Marketing Insights for Agentforce Sales is also designed for sales-oriented marketing intelligence and isn't the custom reporting mechanism requested here.

The uploaded source identifies option B as the answer. Salesforce documentation confirms that the Marketing Performance Semantic Model contains send-definition and engagement data and is available for custom analytics reporting.

Study Guide Reference: Analytics and Performance Insights ? Marketing Performance Intelligence ? Semantic Data Models and Custom Reporting.

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

Marketing Cloud Next forms are designed to be presented through landing pages . Salesforce explicitly states that marketers create a form and add it as a component to a landing page. The landing page supplies the publicly accessible URL that can then be promoted through email, web, or other channels.

Therefore, NTO should create the event-registration form, associate it with the appropriate processing flow, place the form on a Marketing Cloud Next landing page, publish the landing page, and configure the email CTA to point to the page's public URL.

A form isn't intended to function as a standalone public web asset independently of a landing page. Salesforce notes that customers can't view a form until it's placed on a landing page that is published and has an active URL alias. Likewise, embedding a functional Marketing Cloud Next form directly inside an email isn't the supported registration architecture and would also face significant email-client limitations.

The uploaded master bank identifies C. Salesforce's current documentation directly states that forms should be added as components to landing pages and promoted by linking to those pages.

Study Guide Reference: Campaign Design, Flow Orchestration and Content ? Forms and Landing Pages ? Registration Experiences.

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

Digital Wallet Consumption Cards provide the appropriate operational view of messaging-credit consumption and remaining entitlement. Salesforce states that Digital Wallet displays consumption-based product information for Marketing Cloud Next, including Email and SMS Messaging Credits.

Each Consumption Card includes key entitlement metrics such as Credits Consumed, Credits Remaining, Consumption Percentage, and entitlement expiration information . This gives the consultant a direct view of how much messaging capacity has been used and what remains without requiring custom analytics.

Salesforce also documents that users can open a Consumption Card and choose View Consumption Details for additional usage information over time. This is significantly more appropriate than Data 360 harmonization logs, which relate to data processing and don't measure email/SMS messaging entitlements.

Usage-related information can exist elsewhere in Salesforce setup, but the question specifically asks for both message consumption and remaining credits. Digital Wallet Consumption Cards are the purpose-built interface for that requirement.

The uploaded source keys A. Salesforce's current July 2026 documentation confirms that Digital Wallet Consumption Cards display messaging usage, credits consumed, and credits remaining.

Study Guide Reference: Analytics and Performance Insights ? Digital Wallet ? Messaging Credit Consumption and Entitlements.

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

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.

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

Among the supplied choices, A represents the Marketing Cloud Next consent-layer update rather than manipulating the ordinary CRM Email Opt Out field . Current Salesforce terminology has evolved: service representatives can view and update Marketing Cloud Next consent from the Salesforce record using the Privacy Consent Status Lightning Web Component , while automated changes use Create Consent/Consent Request.

Salesforce explicitly states that the standard HasOptedOutOfEmail field on Lead or Contact isn't used by Marketing Cloud Next consent by default. Therefore, C doesn't reliably unsubscribe the person from Marketing Cloud Next communications.

A preference page is normally the customer's self-service experience. Customers can use an "unsubscribe from all emails" preference-page action, which sets them to OPT_OUT for all applicable subscriptions, but the scenario describes a service representative acting on the customer's request.

The uploaded source keys A. The phrase "Consent Status flow element" reflects older/imprecise terminology; the current manual interface is Privacy Consent Status.

Study Guide Reference: Consent ? Manual Consent Management ? Privacy Consent Status and Subscription-Level Opt-Out.

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

Common Assets is specifically designed to distribute governed reusable content across Marketing Cloud Next Business Units. Salesforce states that Common Assets is a library that makes content available to all Business Units . Members can post approved content from their workspace to the library, and marketers in other Business Units can copy that content into their own workspaces.

This makes it well suited to centrally governed items such as logos, legal disclaimers, approved documents, forms, landing-page templates, and email assets. Salesforce's supported Common Assets content types include Email, images, documents, forms, preference pages, and several other CMS types.

Option A incorrectly assumes ordinary folder permissions provide a cross-Business-Unit governance mechanism. Option C would grant users access directly into another Business Unit's workspace, undermining the isolation that Business Units are intended to provide.

Using a central workspace as the authoritative creation location while publishing approved reusable assets through Common Assets preserves both centralized governance and regional campaign autonomy.

The uploaded source correctly identifies B.

Study Guide Reference: Platform Setup and Governance ? Business Units ? Common Assets and Centralized Content Governance.

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

An Actionable List is the correct audience mechanism when marketers need to target a fixed, specifically selected collection of existing Leads or Contacts without building a Data 360 segment. Salesforce describes Actionable Lists as static collections suited to known individuals, such as imported event attendees or other deliberately selected contacts. An Audience Flow can use a List as its audience source.

For personalization, Content Variables provide dynamic placeholders whose values can be populated by Flow at runtime. Salesforce allows content variables to map to data sources available to Flow, including Salesforce records and other connected data. This makes it possible to supply attributes such as First Name and Account information during message execution.

A Data Graph is designed primarily as a personalization data source and isn't itself the appropriate fixed-list audience source described here. Option A unnecessarily introduces a marketing object and AMPscript when the records already exist as Contacts.

The uploaded master bank identifies C. Salesforce confirms that Audience Flows support List sources and that Actionable Lists represent fixed audiences.

Study Guide Reference: Campaign Design, Flow Orchestration and Content ? Audience Flows ? Actionable Lists and Content Variables.

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

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.

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

After the initial Identity Resolution processing, Data 360 uses incremental processing so that unchanged source records don't need to be repeatedly rematched. Salesforce's current Identity Resolution documentation explicitly states that preprocessing identifies records that are new or changed and sends only those records into Identity Resolution.

Salesforce determines whether a record changed by converting source records to hash values and comparing those hashes with the values from previous Identity Resolution runs. Records whose current hash indicates no change can be excluded from unnecessary reprocessing.

This behavior has direct credit-consumption implications. Salesforce explains that preprocessing prevents credits from being consumed by repeatedly running Identity Resolution over records that have already been unified in their current form. Even when a source performs a full refresh, preprocessing can protect unchanged records from unnecessary identity-processing work.

Option A is incomplete because an existing record that has been modified must also be reprocessed. Option B incorrectly assumes that every subsequent run rematches the entire source population.

The uploaded master correctly keys C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation ? Identity Resolution ? Incremental Processing and Credit Consumption.

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

Marketing Cloud Next evaluates consent at the intersection of a contact point, engagement channel, and communication subscription . Salesforce's consent model is deliberately granular so that customers can make different decisions for different channels and categories of marketing content.

For example, the same customer might opt in to the "Weekly Deals" subscription by SMS while declining the same subscription by email. They might simultaneously remain opted in to a separate "Product Updates" email subscription. Salesforce explicitly states that customers give consent for each channel type associated with a communication subscription.

The contact point is also significant. Consent is tied to contact-point values—such as a particular email address or telephone number—rather than simply being stored as one global preference on the Unified Individual. Salesforce notes that a Unified Individual can contain multiple contact points and that consent checks evaluate those contact points during sending.

Options B and C incorrectly describe consent as globally shared.

The source bank correctly identifies A.

Study Guide Reference: Consent ? Consent Evaluation ? Contact Point, Channel, and Communication Subscription.

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