Free Salesforce MC-Con-201 Practice Exam with Questions & Answers | Set: 2

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.

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

Common Assets is specifically designed to distribute governed reusable content across Marketing Cloud Next Business Units. Salesforce states that Common Assets is a library that makes content available to all Business Units . Members can post approved content from their workspace to the library, and marketers in other Business Units can copy that content into their own workspaces.

This makes it well suited to centrally governed items such as logos, legal disclaimers, approved documents, forms, landing-page templates, and email assets. Salesforce's supported Common Assets content types include Email, images, documents, forms, preference pages, and several other CMS types.

Option A incorrectly assumes ordinary folder permissions provide a cross-Business-Unit governance mechanism. Option C would grant users access directly into another Business Unit's workspace, undermining the isolation that Business Units are intended to provide.

Using a central workspace as the authoritative creation location while publishing approved reusable assets through Common Assets preserves both centralized governance and regional campaign autonomy.

The uploaded source correctly identifies B.

Study Guide Reference: Platform Setup and Governance → Business Units → Common Assets and Centralized Content Governance.

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

Einstein Engagement Frequency is specifically designed to determine an appropriate email-contact frequency for each subscriber and reduce over-messaging. Salesforce states that the model analyzes each contact's engagement history to determine the optimal frequency for sending email and explicitly identifies reducing unsubscribes caused by email fatigue as a primary benefit.

This differs from Send Time Optimization. STO predicts when an individual is most likely to engage with a particular communication; it doesn't primarily determine whether that person is receiving too many emails overall. Engagement Frequency addresses the volume and cadence dimension.

Messaging Insights provides analytical insights but isn't the predictive frequency-management feature described in the scenario.

A marketer can therefore use Engagement Frequency to identify contacts who are oversaturated, appropriately saturated, or potentially undersaturated and apply that information when defining campaign audiences or communication strategies. This makes it the correct Einstein capability when the business objective is decreasing customer fatigue and consequent opt-outs.

The uploaded question bank correctly identifies A.

Study Guide Reference: Agentforce and AI Innovation → Einstein Engagement Frequency → Email Fatigue and Subscriber Optimization.

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

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.

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

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

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

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

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

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

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

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.

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

Einstein Send Time Optimization (STO) is designed to determine the best time to deliver an email to each individual based on predicted engagement behavior. Salesforce describes STO as a predictive AI capability that analyzes historical data and estimates the send time at which each subscriber is most likely to engage. This makes it the appropriate feature when a global campaign needs individualized delivery timing rather than one fixed send time for the whole audience.

Engagement Frequency addresses a different optimization problem. It determines how frequently a customer should receive email and is primarily intended to reduce fatigue and unsubscribes caused by over-messaging. Engagement Scoring predicts behaviors such as likelihood to open, click, or unsubscribe, allowing marketers to segment or branch audiences according to engagement propensity.

Neither of those features directly schedules each recipient's email for their predicted optimal engagement time.

The master question bank identifies A as the answer. Salesforce's STO model documentation likewise states that the feature maximizes email engagement by optimizing individual send times.

Study Guide Reference: Agentforce and AI Innovation → Einstein Predictive AI → Send Time 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 Data 360 Profile Insights component is Salesforce's prescribed component for surfacing marketing scores directly on relevant CRM record pages. Salesforce explicitly states that administrators can add this component to Lead and Contact pages and configure it to display Overall Marketing Score, Marketing Engagement Score, and Marketing Fit Score .

This gives sales users an immediate, contextual indication of marketing readiness and engagement without requiring them to open a separate report or dashboard. These scores can help sales teams identify which leads or contacts have the greatest likelihood of engagement or conversion.

A custom report isn't the intended embedded scoring experience and adds unnecessary reporting overhead. Unified Engagement History serves a different purpose: it surfaces historical marketing interactions such as email or web engagement. It isn't the component used to display the calculated Overall Marketing Score.

The uploaded source identifies B.

The file wording includes prospects in addition to leads and contacts. Current Salesforce scoring documentation most explicitly describes the Profile Insights component on Lead and Contact record pages; the source supplies the broader exam framing.

Study Guide Reference: Analytics and Performance Insights → Marketing Scoring → Data 360 Profile Insights.

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