Free Practice Questions for Salesforce MC-Con-201 Exam

The Marketing Cloud Engagement Business Unit containing the Journey must be mapped to the Data Space in which the Marketing Cloud Next flow operates . Salesforce explicitly lists this mapping as a prerequisite for a Journey to appear as a selectable destination in the Send to Journey action. This ensures that the source audience, activation/contact-point configuration, and destination Journey operate within the correct data and organizational context.

Salesforce also requires the selected Journey to be active and to use an API Event as its entry source. Consequently, option B is incorrect because a Salesforce Data Entry Source isn't the required Journey entry mechanism for Send to Journey. Option C is also incorrect because the integration isn't dependent on the flow being record-triggered. Salesforce supports Send to Journey from the applicable marketing-flow architecture.

Activation templates can provide reusable contact-point-selection logic. However, that contact-point configuration doesn't remove the prerequisite relationship between the flow's Data Space and the Marketing Cloud Engagement Business Unit that owns the Journey.

The uploaded master bank identifies A. Salesforce's current Send to Journey documentation confirms the Business Unit-to-Data Space mapping and API Event requirement.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Marketing Cloud Engagement Journeys → Send to Journey and Activation Templates.

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.

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

A Data 360-triggered flow is the more precise event-driven architecture when the automation should respond to a change in a Calculated Insight Object (CIO). Salesforce explicitly supports Data 360-triggered flows based on changes in either DMOs or calculated insights. The flow can define entry conditions so that it fires when the calculated value changes into the target state—for example, when Churn Risk = High.

This design avoids waiting for an independently scheduled audience-segment publication cycle. Data 360 change processing generates the triggering event after the calculated insight is recalculated and the record satisfies the configured conditions. Salesforce states that Data 360 data actions and triggered flows can react to CIO changes in near real time after the underlying calculation completes.

Option C is incorrect because a normal CRM record-triggered flow isn't the proper trigger type for a Data 360 calculated insight object. Option A can support scheduled re-engagement campaigns, but it introduces segment publication scheduling when the requirement explicitly centers on the moment the insight changes.

The uploaded bank keys A. Current Salesforce documentation directly supports CIO-triggered Data 360 flows, making B the stronger current answer .

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Data 360-Triggered Flows → Calculated Insight Changes.

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

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 custom Analytics report using the Marketing Performance Semantic Model is the appropriate solution when NTO needs detailed, exportable engagement information rather than only aggregated campaign KPIs.

Salesforce defines the Marketing Performance Semantic Model as a semantic layer containing information about message send definitions and engagement data . Email engagement includes events such as sends, deliveries, opens, bounces, clicks, and unsubscribes. Salesforce also provides combined reporting structures such as Bulk Email Message with Email Engagement for detailed analytical use cases.

By creating a custom report, NTO can filter the engagement data to the Back to School campaign and specifically to click events, then include the relevant profile/contact attributes available through the reporting model and export the resulting rows.

Campaign-record dashboards are primarily designed for summarized performance visualization and don't provide the same flexible row-level reporting/export capability. Likewise, viewing Marketing Performance dashboards doesn't automatically produce the requested individual-level extract.

The uploaded source identifies A.

Study Guide Reference: Analytics and Performance Insights → Custom Marketing Analytics → Marketing Performance Semantic Model and Email Engagement Reporting.

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.

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

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.

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.

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

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.

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

Among the available choices, A is the intended Advanced-edition capability. Standard content creation is a core Marketing Cloud Next capability available in both Growth and Advanced editions, so C doesn't require Advanced. Standard Salesforce reporting likewise isn't inherently restricted to Marketing Cloud Next Advanced, eliminating B.

The edition distinction becomes important for account-oriented marketing capabilities. Salesforce's current implementation documentation identifies Account scoring as an Advanced Edition capability and requires identity resolution for both Individual and Account objects before configuring people-and-account scoring. This is why account-level identity infrastructure appears in Advanced-focused implementation scenarios.

There is an important technical nuance: Salesforce's general Identity Resolution documentation describes creating custom rulesets for either Individual or Account and doesn't independently state, in the current public article, that merely creating an Account ruleset is universally Advanced-only. The Advanced restriction is explicitly documented around the account-oriented scoring capability that depends on that ruleset. Within the supplied options and certification context, however, A is the valid answer ; B and C are clearly Growth-supported functionality.

The master bank also keys A.

Study Guide Reference: Platform Setup and Governance → Editions and Feature Availability → Growth vs. Advanced.

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