Free and Premium Salesforce MC-Con-201 Dumps Questions Answers

The Communication Subscription Channel Type object represents the relationship between a particular Communication Subscription and an Engagement Channel Type. Salesforce defines it as the object that specifies the engagement channel that can be used for a given communication subscription.

Therefore, if "Product Announcements" supports both Email and SMS , two subscription-channel relationships exist: Product Announcements + Email, and Product Announcements + SMS. Each combination requires its own Communication Subscription Channel Type record.

Salesforce's Data 360 mapping requirements reinforce this relationship. The Communication Subscription Channel Type DMO includes both a Communication Subscription ID and an Engagement Channel Type ID , confirming that each record associates one subscription with one channel.

Contact points are associated with individual subscribers and consent records, not with the definition of the subscription/channel relationship itself, so A is incorrect. OPT_IN and OPT_OUT states are stored as consent information and don't cause the two Communication Subscription Channel Type records described here.

The uploaded bank correctly keys C.

Study Guide Reference: Consent → Communication Subscription Data Model → Communication Subscription Channel Type.

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

Match rules determine whether separate source profiles represent the same real-world individual. Data 360 Identity Resolution evaluates configured attributes and matching methods—such as normalized email, normalized phone, name, party identifiers, or device identifiers—to decide which Individual records should belong to the same Unified Individual.

Salesforce provides default and custom match rules. For example, default configurations can compare fuzzy first name, exact last name, and normalized email or telephone values. Multiple rules can coexist within an Identity Resolution ruleset.

Reconciliation rules serve a later and fundamentally different purpose. After records have been matched, reconciliation determines which values become representative unified-profile attributes—for example, whether CRM or loyalty should supply the preferred First Name. Therefore B confuses matching with attribute-value selection.

Identity Resolution also doesn't destructively merge the source records into one Individual record. Source profiles remain available and are linked through the resulting unified profile.

The uploaded master bank correctly identifies C.

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

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

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.

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

The Forms Engagement dashboard is specifically designed to provide an aggregate view of Marketing Cloud Next form performance. Salesforce's current Reporting in Marketing Cloud Next reference describes the Forms Engagement dashboard as a big-picture view of form KPIs that can be filtered by date, public title, and other attributes . That wording aligns directly with this scenario.

The Landing Page Engagement dashboard instead measures landing-page performance. Although the forms may be embedded on landing pages, the marketing manager is asking to compare the performance of the forms themselves. Campaign Performance provides higher-level campaign analysis across multiple assets and interactions but isn't the specialized dashboard for form-level KPIs.

Typical form analytics can help marketers understand submission activity and compare forms used across campaigns. Because the requirement explicitly calls for a high-level view across several gift-finder forms and filtering by public title, Forms Engagement is the exact reporting surface Salesforce documents for this purpose.

The uploaded master bank also identifies option B.

Study Guide Reference: Analytics and Performance Insights → Reporting in Marketing Cloud Next → Forms Engagement Dashboard.

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

An Automation Event-Triggered Flow with the supported consent action is the correct architecture for processing consent immediately after a Marketing Cloud Next form submission. Salesforce specifically states that Create Consent can be used in event-triggered flows to automate consent updates based on events such as a form submission .

Current Salesforce documentation commonly labels the Flow element Create Consent , while some recent support guidance still refers to the underlying operation as Consent Request . The functional purpose is the same in this question: update the contact point's OPT_IN or OPT_OUT state for the appropriate channel and communication subscription through the supported Marketing Cloud Next consent service.

Options B and C are incorrect because directly mapping ingestion or transformation results into the Communication Subscription Consent DMO isn't the supported consent-writing path. Salesforce's August 17, 2026 guidance specifically states that landing-page form consent should be paired with an Automation Event-Triggered Flow and Consent Request action.

The uploaded master correctly keys A.

Study Guide Reference: Consent → Automating Consent → Form Submission, Automation Event-Triggered Flow, and Create Consent/Consent Request.

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

Identity Resolution can be a significant consumer of Data Services Credits because profile-unification jobs process qualifying source records. Salesforce specifically recommends controlling unnecessary identity-resolution execution when configuring or modifying rulesets. One supported optimization is to disable Run jobs automatically while making configuration changes and use Run Now deliberately when processing is actually required. This prevents repeated automatic runs while administrators are iterating on match, reconciliation, or filtering logic.

Salesforce also recommends keeping only one active ruleset when possible to reduce usage costs. Therefore, option B would move in the wrong direction: maintaining multiple active rulesets can increase processing and credit consumption rather than reduce it.

Option C is also inappropriate. Recreating data streams can cause unnecessary data reprocessing and isn't the recommended credit-management technique. Data filtering and sensible scheduling are much more controlled approaches.

Because the question states that row-count optimization has already been performed, controlling automatic identity-resolution jobs is the best additional measure among the available options. The master bank keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Data Services Billable Usage Types and cost optimization.

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

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.

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

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.

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

Einstein Engagement Scoring is designed to predict the likelihood that an individual subscriber will engage with future email communications. Salesforce states that the model predicts email opens and clicks, subscriber retention, web conversion, and overall engagement for individual consumer contacts.

Those predicted likelihood values can be used to identify customers with low engagement propensity. A marketer can therefore segment, filter, suppress, or branch customers according to their predicted open or click probability before an audience flow sends a message.

Send Time Optimization solves a different problem. STO assumes that a recipient is going to receive the communication and predicts when that person is most likely to engage. It doesn't primarily determine whether a low-propensity customer should be excluded. Messaging Insights isn't the predictive subscriber-level engagement scoring capability described in this requirement.

Salesforce also stores the output in the Email Engagement Score DMO , which supports reporting and audience analysis based on open, click, and subscription likelihood.

The uploaded master bank correctly keys A. Salesforce's current Einstein Engagement Scoring model card confirms that it predicts opens, clicks, retention, and overall engagement.

Study Guide Reference: Agentforce and AI Innovation → Einstein Engagement Scoring → Predictive Audience Optimization.

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

The Communication Subscription Consent DMO stores the individual's actual consent state for Marketing Cloud Next subscription-based communications. Salesforce's consent model separates the definition of a marketing subscription from the customer's consent associated with that subscription.

For example, "Product Updates" or "Events" is represented by a Communication Subscription . Email and SMS are associated channel types. The resulting consent state—such as OPT_IN or OPT_OUT—for the applicable contact point, subscription, and channel is represented through Communication Subscription Consent.

Salesforce explicitly identifies four core objects participating in the Marketing Cloud Next consent architecture: Communication Subscription, Engagement Channel Type, Communication Subscription Channel Type, and Communication Subscription Consent. It also confirms that Marketing Cloud Next consent is stored in the Communication Subscription Consent DMO.

Contact Point Consent isn't the appropriate Marketing Cloud Next subscription-level DMO in this scenario. Communication Subscription defines what customers are subscribing to but doesn't itself store each customer's consent state.

The uploaded master bank also identifies C.

Study Guide Reference: Consent → Communication Subscription Data Model → Communication Subscription Consent.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

Dynamic reply addresses require an authorized email domain , which is different from an authenticated sending domain. After the consultant adds the domain under Unified Messaging → Authorized Email Domains, Salesforce generates a verification code. The administrator must add that value to the organization's DNS as a TXT record , then return to Salesforce and verify the domain.

Salesforce uses this verification to establish domain ownership before Marketing Cloud Next allows dynamic reply-to addresses on that domain. If a dynamically resolved reply address uses an unauthorized domain, Marketing Cloud Next falls back to the configured fallback reply address. Salesforce reiterated this behavior in an August 28, 2026 support article.

An Authenticated From Address pertains to outbound email sending rather than authorizing dynamic replies. Sender Authentication Package is associated with other Marketing Cloud architectures and isn't the next step in Marketing Cloud Next's Authorized Email Domains workflow.

The master file correctly identifies C.

Study Guide Reference: Platform Setup and Governance → Unified Messaging → Authorized Email Domains and Dynamic Reply Addresses.

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

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.

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

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

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

Salesforce supports additive edits to an existing Data Graph , including adding related DMOs and adding fields to existing DMOs. When an active Data Graph is edited and the consultant chooses Save and Build , Salesforce processes the new version while keeping the currently active version available.

Salesforce explicitly states that during processing, the existing Data Graph remains active . Once processing completes successfully, the newly built version becomes active. If the build fails, the existing graph continues to operate. This design protects downstream consumers from unnecessary interruption during an additive update.

Cloning is useful when a genuinely separate Data Graph configuration is required, but it isn't necessary merely because an active graph needs additional data. Option B incorrectly claims that editing automatically invalidates dependencies. Option C adds unnecessary operational disruption by pausing segments and flows.

There are limits: once a Data Graph is active, changes are generally additive; existing objects and fields can't simply be removed as they can from a draft.

The master bank correctly keys A. Salesforce's current Data Graph editing documentation directly confirms this version-processing behavior.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graph Management → Editing, Building, and Version Processing.

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

Salesforce's current Conversational Email implementation guide lists essentially the same five activities shown in option C . First, configure the human representative escalation experience in Service Cloud and Omni-Channel. Second, configure an Agentforce Service Agent capable of handling email conversations. Third, enable and configure Conversational Email in Unified Messaging for the applicable sending address. Fourth, create the Conversational Email campaign and its flow. Finally, monitor engagement, routing, resolutions, and agent escalation outcomes.

Salesforce emphasizes that the human escalation experience should be configured before Conversational Email is enabled, because customers must have a supported path to a human representative when the AI agent can't resolve an inquiry. Service Agents are likewise a formal prerequisite because Agentforce provides the automated interpretation and response capability.

Option A introduces a transactional API endpoint that isn't a standard implementation requirement. Option B relies on Journey Builder and Marketing Cloud Connect concepts that aren't part of the Marketing Cloud Next Conversational Email setup sequence.

The uploaded source correctly identifies C.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Agentforce, Service Cloud, Escalation, and Monitoring.

After the consultant adds a sending domain, Unified Messaging generates the DNS configuration necessary to authenticate that domain. The required next step is to copy the generated DNS entries and configure them with the organization's DNS provider . Salesforce's current setup procedure states that the generated entries include CNAME and DKIM-related records , after which the consultant returns to Salesforce and verifies the domain.

Salesforce's 2026 DNS guidance states that Marketing Cloud Next authenticated domains require multiple CNAME records and that the outbound CNAME records provide DKIM authentication. The exact number of required CNAME entries can vary with the specific domain configuration and whether the domain is shared, but option B captures the required procedure.

A standalone TXT ownership record isn't sufficient for Marketing Cloud Next email authentication in this scenario. Sender Authentication Package is terminology associated primarily with the legacy Marketing Cloud Engagement configuration model and isn't how Marketing Cloud Next Unified Messaging authenticates a new sending domain.

The master bank keys B. Salesforce's current domain-authentication procedure confirms this DNS configuration sequence.

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

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

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.

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

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.

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

Option A most accurately reflects the different processing cadences involved. For Salesforce CRM data streams in Data 360, Salesforce documents an incremental refresh every 10 minutes after the initial full refresh. These refreshes bring newly created or changed CRM records into Data 360, although actual completion times can vary depending on processing conditions.

Identity Resolution operates on a different schedule. Once an identity resolution ruleset is published, Salesforce schedules it to run at least once per day by default. Identity Resolution is therefore not a synchronous operation that reruns every time an individual source record arrives. It periodically evaluates eligible source records according to configured match rules and then applies reconciliation logic to produce unified profiles.

Option B reverses these two schedules. Option C is incorrect because CRM incremental ingestion isn't universally instantaneous, and published identity-resolution rulesets aren't limited to weekly execution.

The 10-minute figure should specifically be understood in the context of the standard Salesforce CRM incremental connector behavior described in Salesforce documentation. The uploaded master bank keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data 360 → Identity Resolution Rulesets and Data Stream Processing.

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

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.

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

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 is the closest technically correct choice. Data 360 doesn't inherently activate every email address associated with a Unified Individual. Salesforce states that when Unified Individual is used as activation membership, Data 360 activates one row per Unified Individual and selects an appropriate contact point according to contact-point source selection and prioritization logic.

Where multiple contact points exist, selection can depend on configured source priority, filters, sorting, and—in applicable implementations—engagement scoring. Salesforce therefore preserves multiple valid contact points in the unified profile while selecting one contact point for an activation/send context.

Option B is incorrect because identity-resolution reconciliation rules don't select the email address used for message delivery . Reconciliation selects representative unified-profile attributes. Option C incorrectly assumes every retained contact point automatically generates a duplicate email.

The uploaded file contains this question but leaves its answer blank. The wording "designated as the primary Contact Point Email" isn't the most precise current Salesforce terminology; nevertheless, A correctly captures the essential behavior that one selected contact point is used , rather than sending to both.

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

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

A Marketing Object is the Marketing Cloud Next-native structure for storing tabular marketing data used in campaigns, personalization, briefs, and flows. Salesforce allows marketers to create a Marketing Object directly from a CSV upload; the resulting object contains the columns defined in the source file, and Marketing Cloud Next infers the appropriate field types during import.

This makes Marketing Objects suitable for datasets such as promotional codes, localized content, product reference information, campaign-specific lookup tables, or other relatively lightweight structured data that doesn't need to be harmonized into the full Data 360 customer model.

An Actionable List is intended to represent a fixed audience of known Leads or Contacts. It isn't a general-purpose tabular data store. A Data 360 file-upload data stream is appropriate when data must be ingested and mapped into Data 360 DMOs, but the scenario asks specifically for tabular data used for marketing purposes, where Marketing Objects provide the more direct Marketing Cloud Next capability.

The uploaded question bank identifies C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Marketing Objects → Importing and Managing Tabular Marketing Data.

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