MC-Con-201 Salesforce Certified Marketing Cloud Next Consultant Questions and Answers

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.

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

C is the currently supportable answer among these choices. The uploaded bank originally keys A. However, Salesforce's August 2026 consent guidance explicitly states that the legacy MessagingConsent and MessagingConsentV2 Flow actions should not be used for Marketing Cloud Next consent because they can fall out of synchronization with the Marketing Cloud Next consent layer. Salesforce directs implementations to use Create Consent/Consent Request instead.

Create Consent is supported in Data 360-triggered flows and updates the applicable contact point for a specified channel and communication subscription. Direct writes into the underlying consent DLO/DMO, as described in B, bypass the supported consent service and aren't reliable for sending-time consent evaluation.

For a CRM-originated Contact creation, Salesforce's preferred current architecture is actually an Automation Event-Triggered Flow based on the Contact change plus Create Consent . That exact combination isn't offered. Of A–C, C is therefore the only option that uses the supported consent-writing mechanism.

Study Guide Reference: Consent → Creating and Updating Consent → Create Consent/Consent Request.

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

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.

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

The Privacy Consent Status component is specifically intended to expose Marketing Cloud Next consent information on Lead and Contact record pages. Salesforce documents that the component retrieves the relevant email addresses and phone numbers from the CRM record and displays the consent state associated with those contact points. Authorized users can therefore review and manage communication preferences while working directly from the person's Salesforce record.

This is materially different from Data 360 Related Lists, which surface related Data 360 information but aren't the dedicated consent-management interface. Data 360 Profile Insights is used for profile and calculated insight information, such as marketing scores, rather than managing channel and subscription consent.

Salesforce also clarifies that the ordinary HasOptedOutOfEmail field isn't the Marketing Cloud Next consent mechanism. Marketing Cloud Next consent is stored through its dedicated consent model and surfaced through the consent component.

The uploaded master correctly keys A. Current Salesforce documentation explicitly names the Privacy Consent Status component for displaying consent associated with email and phone contact points.

Study Guide Reference: Consent → Managing and Reviewing Consent → Privacy Consent Status Component.

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

B is the best answer among the available choices , because an Audience Flow with a Data 360 Segment source is the appropriate architecture for a dynamically changing audience. Salesforce states that Data 360 segments update membership based on profile attributes and behavioral data, while Audience Flows can use those segment members as their audience source.

For a "no purchase in 90 days" use case, the marketer defines the lapsed-customer criteria in a Data 360 segment. As purchase data changes and the segment republishes, qualifying customers enter or leave the segment automatically. The Audience Flow then orchestrates the scheduled re-engagement communication against the current membership.

An Automation Event-Triggered Flow is more appropriate for responding to discrete events, such as a form submission or email click. A Marketing Object stores marketing-specific tabular data and isn't a dynamic audience-management mechanism.

The uploaded bank keys B.

Technical precision: the Data 360 feature actually maintaining dynamic membership is the Segment ; Audience Flow is the orchestration layer consuming that segment. Because "Segment" isn't offered as an option, B is the only architecturally valid choice. Salesforce confirms both behaviors.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Dynamic Segments and Audience Flows.

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

Marketing Cloud Next supports both Salesforce Record and Offer as native email personalization data sources. Salesforce Record is designed to surface current business information from Salesforce objects. Salesforce specifically notes that marketers can add a Salesforce Record data source and reference Salesforce object fields directly in email content.

That makes it appropriate for a recipient's assigned sales representative when the representative relationship is maintained in Salesforce/Agentforce Sales data.

The Offer data provider is specifically designed for promotions. Salesforce states that marketers can add an Offer as an email data source and use merge fields for values such as the offer name, description, or coupon code . It also supports multiple offer providers and conditional targeting based on customer attributes.

An Apex Class would be unnecessary custom logic for retrieving an ordinary Salesforce business attribute. A Data Graph also isn't the natural mechanism for a Marketing Cloud Next-managed, time-sensitive offer code when the purpose-built Offer data source exists.

The uploaded bank identifies A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization Data Sources → Salesforce Record and Offer.

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

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.

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

A Repeater component is specifically designed for displaying a variable-length collection of related items within a Marketing Cloud Next email. Salesforce provides examples such as products, recent order updates, upcoming events, and promotions. The repeater connects to a supported collection data source—such as event data or a Data Graph attribute—and repeats its nested components once for every item returned.

For the order confirmation, the consultant can use the collection of purchased line items as the Repeater Source. Inside the repeater, nested text and image components use merge fields for Product Name, Image URL, and Price. Whether an order contains one product or twenty, the same component dynamically renders the full list.

Content variations solve conditional content-selection problems, not one-to-many row iteration. AMPscript is also unnecessary because Marketing Cloud Next provides the native Repeater capability for this requirement.

The uploaded master source identifies B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Email Personalization → Repeater Components and Collection Data.

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

The correct Data Model Object is Email Engagement Score . Einstein Engagement Scoring evaluates historical email engagement behavior and creates predictive attributes that can be used to understand the likelihood of future customer actions. Salesforce identifies the Email Engagement Score DMO as the Data 360 object used for reporting on engagement personas and likelihood measures such as email opens, clicks, and subscription-related behavior.

The DMO can also be incorporated into Data Graph relationships. For example, when an Einstein Decision element relies on Engagement Scoring, Salesforce requires the Contact Point Email DMO to include the Einstein Engagement Score DMO as a related object and the appropriate attributes, such as Email Click Likelihood and Email Open Likelihood.

"Email Engagement Metrics" and "Email Engagement Profile" aren't the standard DMOs Salesforce specifies for these predictive outputs. They therefore don't represent the correct persisted scoring object.

The uploaded master bank also identifies option C as the keyed answer.

Study Guide Reference: Agentforce and AI Innovation → Einstein capabilities in Marketing Cloud Next; Analytics and Performance concepts → Data 360 reporting for Einstein features.

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

Marketing Cloud Next currently supports three field data types for Marketing Objects: Text, Number, and Decimal .

Salesforce defines Text as a string value of up to 255 characters. Number stores positive or negative integers with up to 18 digits. Decimal stores positive or negative decimal numbers with up to 18 digits. These deliberately constrained field types make Marketing Objects suitable for lightweight campaign, lookup, promotional, localization, and personalization datasets.

Option B is incorrect because Formula isn't listed as a Marketing Object field type. Calculated logic can be handled through other platform capabilities, but formula isn't one of the three selectable types when defining a Marketing Object field.

Option C uses familiar programming terminology—String, Integer, Boolean—but those aren't the Marketing Cloud Next field labels and Boolean isn't currently one of the supported Marketing Object field types documented by Salesforce.

The uploaded master bank identifies option A. This item has direct current-documentation support: Salesforce's Marketing Object Data Types and Resource Allocations reference explicitly lists only Text, Number, and Decimal .

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Marketing Objects → Supported Data Types and Resource Allocations.

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

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.

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

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.

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

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.

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

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.

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

Basic Marketing Cloud Next implementation spans both Marketing Cloud administration and Data 360 architecture , so administrative access must cover both domains. Salesforce identifies the Marketing Cloud Admin permission set as the administrative role that can configure Marketing Cloud Next settings and manage core marketing functionality. The Data Cloud Architect permission set—the current Salesforce documentation terminology for the architectural Data 360 role—provides access to Data 360 Setup, data modeling, data streams, identity resolution, and related infrastructure.

Accordingly, option A represents the required combination among the available choices: the Data 360/Data Cloud architectural permission set together with Marketing Cloud Admin. Marketing Cloud Manager is oriented toward campaign and marketing operations rather than full administrative configuration, so B doesn't provide the required administrative scope. Data 360 Activation Manager is more narrowly focused on activation-related responsibilities and doesn't replace the broader architecture capabilities needed for foundational implementation.

The uploaded question bank identifies A as the correct response.

Study Guide Reference: Platform Setup and Governance → Getting Started with Marketing Cloud Next Setup → Administrator personas and permission sets.

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

Conversational Email provides the most direct and autonomous solution. Rather than forcing customers to navigate to another web experience or create conventional support cases, NTO can make the existing Order Confirmation and Tracking emails conversational. Customers can simply reply to the email with a question such as "Where is my order?"

Salesforce states that Conversational Email integrates with Agentforce, Digital Engagement, and Data 360. The platform analyzes inbound replies, determines intent, and can route the conversation to an Agentforce agent or human representative while preserving the complete email-thread context.

Salesforce specifically lists Order Management and tracking-information requests as a Conversational Email use case. This makes C particularly strong: Agentforce can resolve repetitive tracking requests without generating unnecessary low-value support workload.

Option A adds friction by sending the customer to a separate chatbot page. Option B only automates routing after a support ticket already exists, whereas the requirement is to reduce or eliminate those cases through autonomous handling.

The uploaded source also keys C.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Autonomous Service and Order Management.

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

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.

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

Automation event-triggered flow is the current verified answer. Salesforce specifically provides a Form Submission Automation Event that launches an automation event-triggered flow whenever a configured marketing form is submitted. Salesforce describes this flow type as the mechanism for automatically responding to events such as form submissions, subscription activity, orders, and other customer behaviors.

This precisely matches the requirement: the action must occur because the customer submitted a web form. The event can launch the flow, after which the Send SMS Message functionality can deliver the white-paper link, subject to valid SMS consent and channel configuration.

An activation-triggered flow is driven by publication of Data 360 activation data and isn't the direct event architecture for an individual form submission. A standard record-triggered flow reacts to creation or changes of Salesforce records but is no longer the preferred Marketing Cloud Next mechanism when the triggering business event is a supported form submission.

Source distinction: the uploaded bank keys this question as C . However, current Salesforce documentation explicitly states that form-submission automation uses an Automation Event-Triggered Flow , and that this mechanism replaced form-triggered flows. Therefore the current verified answer is B .

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Automation Event-Triggered Flows → Form Submission Events.

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

A Contact Point Selection Rule implemented through an activation template is specifically designed to determine which email address, phone number, or other messaging contact point should be used when an individual has multiple available values. Salesforce documents activation templates as reusable configurations containing contact point selection, source priority, filtering, enrichment, and membership rules.

For example, an activation template can prioritize a primary CRM email over another email address, filter invalid contact points, and apply consent criteria. Segment-triggered marketing flows can then reference that activation template and use its stored logic to choose one appropriate contact point. Salesforce specifically notes that this capability helps ensure recipients don't receive duplicate messages.

A Decision element isn't intended to reproduce Data 360 contact-point selection logic manually. Identity Resolution also doesn't simply merge multiple legitimate contact points into one. A Unified Individual may correctly retain multiple email addresses belonging to the same person; activation logic determines which address should actually be used.

The uploaded master keys A. Official Salesforce documentation directly supports contact-point selection through activation templates.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Activation Templates → Contact Point Selection.

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

Option B is the currently verified Salesforce-supported approach. Marketing Cloud Next treats a prospect, Lead, or Contact without applicable consent as opted out by default. Therefore, before a new Contact can receive promotional marketing, a valid opt-in must exist for the relevant contact point, channel, and communication subscription .

Salesforce's current 2026 guidance states that consent changes originating from CRM record creation or updates should be handled with an Automation Event-Triggered Flow using the Prospect, Lead, Contact, or Related Record Change event, followed by the Consent Request/Create Consent action . That supported action writes the consent so that Marketing Cloud Next honors it at send time.

Option C is explicitly insufficient because HasOptedOutOfEmail isn't automatically synchronized with Marketing Cloud Next consent. Option A is misleading because directly manipulating a separate CRM consent record doesn't itself establish supported Marketing Cloud Next sending consent.

The uploaded document keys this question as A. However, Salesforce's updated July–August 2026 documentation supersedes that approach and explicitly directs implementations to Create Consent/Consent Request.

Study Guide Reference: Consent → Creating and Updating Consent → Create Consent / Consent Request Flow Action.

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

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.

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

Conversational Email requires more than creating the underlying routing flow. Salesforce instructs administrators to open Authenticated From Addresses in Unified Messaging, select the From Address used for the outbound campaign, and configure Agent Conversational Messaging for that address. The consultant then chooses the Routing Type that determines how incoming replies are handled. Supported routing targets include an Agentforce Service Agent, an Omni-Flow, or an Omni-Queue, followed by a fallback queue where appropriate.

That configuration establishes the link between the outbound From Address and the conversational inbound-routing mechanism. Since the scenario states that the required flow is already built, configuring Agent Conversational Messaging on the sending From Address is the missing prerequisite.

Reply Mail Management can process ordinary inbound replies and fallback scenarios, but simply forwarding RMM mail to an AI queue doesn't establish Conversational Email routing. Similarly, adding another Route Work activity doesn't configure the email address to capture and associate customer replies with the conversational experience.

Therefore, B is correct, matching the uploaded bank.

Study Guide Reference: Agentforce and AI Innovation → Conversational Marketing Fundamentals → Set Up Conversational Email and inbound Agentforce routing.

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

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

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.

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

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

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

When an organization already uses a third-party Consent Management Platform , Marketing Cloud Next shouldn't display a second Salesforce consent banner for the same tracking purpose. Salesforce explicitly states that customers using third-party CMPs such as OneTrust should use the configuration without the Salesforce consent banner and remain responsible for ensuring that tracking complies with applicable privacy requirements.

The practical implementation is to allow the organization's CMP to control when Marketing Cloud Next tracking is initialized or granted consent. The Marketing Cloud Next web-tracking embed code/Interactions SDK can then collect visitor activity only after the appropriate consent state is established.

Option A unnecessarily introduces a second Salesforce banner, violating the requirement to avoid duplicate consent experiences. Option C similarly enables the Salesforce banner and attempts to solve the duplication using CSS suppression, which isn't a supported consent-governance architecture.

The uploaded master bank keys B. Salesforce's current documentation explicitly identifies the external-page configuration without a Salesforce banner as the appropriate configuration when a third-party CMP is being used.

Study Guide Reference: Consent → Web Tracking Consent → Third-Party Consent Management Platforms and Consent Banners.

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