MC-Con-201 Exam Dumps - Salesforce Marketing Cloud Consultant Questions and Answers

A Marketing Object is the most efficient solution when marketers have standalone structured data that is needed for personalization but doesn't need to become part of the enterprise Data 360 customer model. Salesforce allows users to create a Marketing Object directly by uploading a CSV file. The platform creates the object and loads the data in a single operation, automatically inferring supported field types from the uploaded columns.

Salesforce specifically describes Marketing Objects as appropriate for product information, reference data, content variations, and personalized campaign data . The information stored in them can then be retrieved from Marketing Cloud Next content by using Handlebars or AMPscript.

Creating a CRM custom object introduces unnecessary CRM configuration for data that exists only to support a one-time marketing campaign. Similarly, creating a Data 360 data stream and mapping it to a DMO adds ingestion, mapping, processing, and governance overhead that isn't justified by this isolated personalization requirement.

Therefore, A provides the simplest marketer-controlled architecture while maintaining the data in Marketing Cloud Next.

The uploaded master bank also keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Marketing Objects → CSV Import and Message Personalization.

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

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.

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

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 Email Engagement dashboard is the purpose-built dashboard for analyzing standard email performance metrics across Marketing Cloud Next sends. Salesforce's Marketing Performance Intelligence package includes preconfigured Email Engagement reports and dashboard components for common KPIs including Total Emails Sent, Open Rate, Click-Through Rate, Bounce Rate, and Opt-Out Rate.

The dashboard provides visualizations such as status bar graphs, time-based activity graphs, campaign click-engagement rankings, email-send-status views, and detailed activity tables. This allows marketers to evaluate messaging performance without having to construct a custom analytics model.

Campaign Performance is broader and focuses on campaign-level outcomes across associated marketing activity rather than being the specialized email KPI view requested here. Unified Engagement History serves another purpose: it surfaces marketing engagement alongside CRM records such as Contacts, Leads, Accounts, and Opportunities for sales and service users.

Therefore, B precisely matches the requirement for an easy-to-use, cross-send email analytics dashboard.

The uploaded master bank also identifies B. Salesforce's 2026 Marketing Cloud Next reporting documentation explicitly lists Open Rate, Click-Through Rate, Bounce Rate, and related metrics in the Email Engagement dashboard.

Study Guide Reference: Analytics and Performance Insights → Marketing Performance Intelligence → Email Engagement Dashboard.

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

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.

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

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.

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.

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

Handlebars is the appropriate method because the scenario specifically requires conditional logic against values supplied by the Data Graph. Marketing Cloud Next's Handlebars implementation provides comparison and control helpers such as if, else if, equals, compare, and, or, and iif. These functions allow message content to change according to profile values such as Loyalty Tier or Points balance.

Marketing Cloud Next exposes the profile Data Graph through Handlebars, allowing deeply related profile attributes to be referenced and evaluated programmatically. Salesforce's developer documentation describes $dataGraph as the profile data graph loaded with marketing content and shows how nested attributes can be traversed.

Simple merge fields are appropriate when the requirement is only to print an attribute. They don't by themselves provide the richer branching logic requested here. Dynamic content variations can also implement marketer-configured targeting, but when the explicit requirement is conditional expression logic against Data Graph values, Handlebars is the more direct technical answer.

The uploaded source keys B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization → Handlebars Conditional Logic and Data Graph Data.

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

Option C is the verified answer. Salesforce defines Business Units as organizational divisions that use distinct Data Spaces to enforce data separation. Each Business Unit maps to a unique Data Space, and data from one Business Unit isn't shared with another. This architecture directly addresses the requirement that Clinic A marketers must not query, segment, or accidentally activate Clinic B customer profiles.

Option B is fundamentally an object- and field-level access-control requirement. Restricting particular healthcare fields while allowing users to access other Contact fields should be handled through Salesforce permissions, field-level security, Data 360 governance permissions, and related access controls—not by creating an entire Business Unit.

Option A can benefit from Business Units for organizational or branding separation, but different subscriptions or messaging configurations alone don't establish the strongest requirement for segregating customer datasets.

Important correction: the uploaded master document keys this item as B . Current Salesforce documentation explicitly states that Business Units use Data Spaces to keep data separate and are appropriate for organizational divisions such as geographic regions, brands, or isolated audiences. Therefore, the verified answer is C , not B.

Study Guide Reference: Platform Setup and Governance → Business Units → Data Spaces, Data Isolation, and User Access.

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

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

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

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

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

The uploaded bank identifies A.

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

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