Free Practice Questions for the Salesforce Marketing Cloud Consultant MC-Con-201 Exam (2026 Updated)

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.

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

Marketing Cloud Next has its own dedicated consent layer based on Communication Subscription Consent . Salesforce explicitly states that consent data stored in Salesforce CRM is separate from Marketing Cloud Next consent and isn't automatically recognized simply because Marketing Cloud Next has been activated.

Consequently, an implementation that already maintains CRM consent must establish a supported synchronization process. Salesforce currently recommends Salesforce Flows when CRM fields or consent states must drive Marketing Cloud Next consent. For example, an Automation Event-Triggered Flow can monitor changes to Contact or Lead information and use a Consent Request/Create Consent action to update the corresponding Marketing Cloud Next consent state.

Option A is therefore incorrect because existing CRM consent isn't automatically the authoritative sending-time consent source. Option B is also incorrect because activation doesn't automatically synchronize the two models.

The master bank identifies C. Salesforce documentation specifically says that CRM consent records aren't automatically recognized by Marketing Cloud Next and describes flow-based mechanisms for keeping systems aligned.

Study Guide Reference: Consent → Consent Architecture → CRM Consent versus Marketing Cloud Next Communication Subscription Consent.

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

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 agency users need the Marketer-Standard Business Unit role because their responsibilities include both creating marketing assets and deploying campaigns.

Salesforce states that users with the Marketing Cloud Admin or Marketing Cloud Manager permission set can be added to a Business Unit as Marketer-Standard members. These users receive the Content Manager role in the Business Unit's marketing workspace, allowing them to create, edit, view, and publish content. They can also activate campaign flows in that Business Unit.

Marketer-ReadOnly is insufficient because Salesforce explicitly states that ReadOnly members can't activate campaigns and don't receive access to the Business Unit's marketing workspaces. This would prevent the agency from performing the tasks described.

Adding users directly to the Data Space isn't the proper Marketing Cloud Next access-governance model. Business Unit membership automatically grants access to its mapped Data Space according to the Business Unit architecture.

The source bank correctly identifies C.

Study Guide Reference: Platform Setup and Governance → Business Units → Marketer-Standard and Marketer-ReadOnly Roles.

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

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.

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

The Communication Subscription DMO defines the category of marketing content that customers can subscribe to, such as Weekly Deals, Product Updates, or Event Notifications. The Communication Subscription Channel Type DMO then associates that subscription with each supported engagement channel. Therefore, when Weekly Deals is available through both email and SMS, the subscription is represented by Communication Subscription and its channel relationships are represented through Communication Subscription Channel Type.

Communication Subscription Consent performs a different function: it represents customer-level consent associated with the subscription. It doesn't define which channels are supported by the subscription itself. Engagement Channel Type defines available channels such as Email or SMS, but the question specifically asks for the objects used to define the subscription and map it to communication channels . The linking DMO is therefore Communication Subscription Channel Type.

Salesforce explicitly states that each communication subscription contains at least one channel type and can contain several channels. The uploaded master bank also identifies C.

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

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

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

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

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

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

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

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

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

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

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.

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

An Automation Event-Triggered Flow is the Marketing Cloud Next-native architecture for responding near real time to CRM record changes associated with a Prospect, Lead, or Contact. Salesforce provides the Prospect, Lead, Contact, or Related Record Change automation event specifically for this purpose. It can start a flow when a qualifying related record is created or updated and meets configured conditions.

A Case associated with a Contact can therefore serve as the related object. The consultant can configure the entry condition so the automation executes when Case Status changes to Closed, identify the related Contact, and then send the customer-satisfaction email.

A generic Salesforce record-triggered flow can react to Case changes, but option C uses the purpose-built Marketing Cloud Next automation-event model for marketing communications. An Audience Flow is better suited to scheduled or segment/list-based audiences rather than immediate reaction to an individual CRM record update.

The uploaded source also identifies C.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Automation Event-Triggered Flows → Prospect, Lead, Contact, or Related Record Change.

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

An Audience Flow with Segment as the audience source is specifically designed for scheduled marketing communications to populations defined in Data 360. Salesforce states that an Audience Flow runs on a schedule and can use a Segment, List, Record, or Campaign as its audience source. When Segment is selected, the resulting flow targets members of a published Data 360 segment.

Because NTO already has a defined population of high-value customers, the consultant should use that segment rather than manually retrieving DMO records. The weekly schedule can then control campaign execution, while the segment determines membership based on current customer profile and behavioral attributes.

A generic schedule-triggered flow with Get Records bypasses the purpose-built Marketing Cloud Next segment-flow architecture. A Data 360-triggered flow is intended primarily to react to Data 360 record changes, not to execute a recurring weekly campaign against an audience.

Salesforce also recommends ensuring that the underlying segment is published and considering its publication schedule before the flow runs. The uploaded source keys B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Audience Flows → Segment Audience Source and Scheduling.

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

Marketing Cloud Next provides purpose-built AI capabilities rather than requiring marketers to construct a custom Agentforce agent for standard campaign creation. The Campaign Creation Agent can use a natural-language objective to draft a campaign brief, refine the campaign concept, generate campaign assets, and establish audience requirements. Audience generation is then completed through the dedicated Segment Creation capability, which translates natural-language audience requirements into Data 360 segment criteria that the marketer can review and publish.

This separation is important. Campaign Creation and Segment Creation are specialized capabilities with related but distinct responsibilities. Therefore, option C overstates what the Campaign Creation Agent natively performs by implying that it directly completes every segment-building operation within one campaign-generation action.

Option B is technically overengineered for the stated requirement. Custom Agentforce actions and Prompt Builder are valuable when an organization needs bespoke business logic, but standard campaign and audience creation already have supported Marketing Cloud Next capabilities.

The uploaded question bank keys A.

Study Guide Reference: Agentforce and AI Innovation → Agentforce in Marketing Cloud Next → Campaign Creation and AI-assisted Segment Creation.

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

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.

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

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.

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

The source bank recommends starting with a single lean Data Graph and expanding it as additional campaign requirements emerge . This approach avoids building unnecessary relationships and processing large datasets before an actual personalization use case requires them.

Current Salesforce guidance supports the underlying principle. Marketing Cloud Next personalization begins with a Unified Individual-based Data Graph containing required identity/contact fields plus the additional objects and fields required for personalization . Salesforce also notes that Data Graph cost and processing depend on data-model structure, participating records, refresh frequency, and fields updated. It recommends filters so that only records required for the use case are included.

Option A risks creating an oversized graph based on speculative future requirements. Option B introduces two graphs immediately even though the first campaign doesn't establish a requirement for separate demographic and transactional graphs. In the standard Marketing Cloud Next configuration without additional Personalization capabilities, Salesforce also notes that only one default Data Graph is used at a time.

Therefore, begin with the smallest useful graph, validate the campaign, and expand the graph as real personalization requirements develop.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graph Design → Use-Case-Driven Personalization Architecture.

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.

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

An Omni-Channel flow is the appropriate mechanism because inbound customer conversations on Salesforce messaging channels are represented by Messaging Sessions and must be routed through supported messaging-routing infrastructure. Salesforce documents that an inbound Omni-Channel flow can use the Route Work action with the Service Channel set to Messaging and the routing destination set to an Agentforce Service Agent. This provides the supported handoff from the messaging channel to the autonomous agent while preserving the conversation context.

A record-triggered flow is not the standard routing mechanism for assigning an active messaging conversation to an Agentforce Service Agent. Although record-triggered flows can automate changes to Salesforce records, they don't provide the specialized work-routing semantics required for messaging sessions. Assignment rules similarly aren't designed for conversational Omni-Channel routing.

Therefore, option A correctly implements the inbound routing architecture. The uploaded master bank also identifies A as the keyed response.

Study Guide Reference: Agentforce and AI Innovation → Conversational Marketing Fundamentals for Marketing Cloud Next → Agentforce messaging and channel orchestration.

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

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.

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

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

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

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

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

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

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

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

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

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.

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

Salesforce supports generating a draft segment as part of an AI-assisted campaign when Einstein Segment Creation is enabled. The Campaign Creation Agent generates the campaign brief and campaign preview, and the resulting campaign can include a draft audience segment derived from the same campaign context.

Therefore, the marketer doesn't need to recreate the audience definition manually. From the Campaign, the consultant can open the related segment experience, use Segment Creation, and review or refine the generated draft before publishing it. This preserves the target-audience logic already established by the campaign brief.

Option A would require independently describing the segment again, which contradicts the requirement to avoid rewriting the audience description. Option B oversimplifies how the generated segment is managed: Campaign Creation can generate the campaign context and associated draft, but marketers still review the segment through the segment-building experience before using it operationally.

The uploaded bank identifies C.

Study Guide Reference: Agentforce and AI Innovation → Campaign Creation Agent → Einstein Segment Creation and Campaign Brief Grounding.

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

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.

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

The Communication Subscription DMO represents the category or purpose of marketing communication itself. Examples include Product Updates, Weekly Deals, Newsletters, Promotions, or Events. Salesforce's Marketing Cloud Next documentation directs marketers to create a communication subscription for each category of marketing content they send.

After creating a Communication Subscription, one or more channel types—such as Email, SMS, RCS, or WhatsApp where supported—can be associated with that subscription. This channel relationship is represented separately through the Communication Subscription Channel Type model.

Communication Subscription Consent , by contrast, stores the individual's actual consent state in relation to the relevant subscription/contact-point/channel context. It doesn't define the communication category itself.

Therefore, C correctly identifies the object representing the subscription concept that recipients can choose to receive or decline.

The source bank keys C. Salesforce's official documentation states that a communication subscription should be created for each category of marketing content, such as product updates, and that communication channels are then added to that subscription.

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

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

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.

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

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.

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