Salesforce MC-Con-201 - Salesforce Certified Marketing Cloud Next Consultant

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.

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

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.

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

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.

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

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.

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

This requirement combines conditional content selection with one-to-many repeated data , so two different Marketing Cloud Next personalization capabilities are appropriate.

For the subject line, a variation can be associated with targeting rules based on the customer's preferred language. Each language can therefore receive the appropriate localized subject-line version, with a fallback variation available when no targeting condition matches.

For the recommended-product list, a Repeater is the correct component. Salesforce states that repeaters display a series of items such as products, order updates, events, or promotions. The repeater can connect to a Data Graph attribute containing related records, and nested components can use merge fields from each repeated item.

Option C would only be correct if the Data Graph itself contained the fully localized subject text to merge directly. The scenario instead says the Contact stores the preferred language , which is decision criteria—not necessarily the translated subject line itself. Option B unnecessarily relies on AMPscript.

The uploaded source keys A. Salesforce documentation confirms both variation-based dynamic content and Data Graph-backed repeaters.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Dynamic Content → Variations, Targeting Rules, and Repeaters.

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

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

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

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

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

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

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.

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

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.

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

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.

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

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.

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