Free Salesforce MC-Con-201 Practice Exam with Questions & Answers

The most appropriate pattern is Get Records followed by Decision . The flow needs information from a related CRM object—the Case object—that isn't inherently part of the current audience-flow record. A Get Records element can retrieve a matching Case for the customer using criteria such as Contact ID and an open Case status. The subsequent Decision element evaluates whether an open Case was returned and routes the customer accordingly.

Customers with an open case can be diverted away from the Send Email Message path, while those without a matching open Case proceed through the promotional sequence. This structure keeps the suppression condition explicit and maintainable within the flow.

An "Exclusion Filter" isn't the standard Flow Builder element presented for this type of CRM-record lookup and routing. A Decision element alone also can't simply assume access to arbitrary related Case data; the related records first need to be retrieved or otherwise supplied to the flow.

Salesforce lists both Get Records and Decision as supported Flow Builder elements for marketing automation. The supplied master bank likewise keys option A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Flow Elements → Get Records and Decision.

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

An Identity Resolution ruleset is the Data 360 component responsible for linking source profiles from different systems into unified customer profiles. A ruleset contains match rules and reconciliation rules that govern the unification process.

Match rules determine whether records from CRM, ecommerce, loyalty, or other systems represent the same person by comparing attributes such as names, normalized email addresses, telephone numbers, party identifiers, device identifiers, or other matching criteria. When records satisfy a match rule, Data 360 associates them with the same Unified Individual.

Reconciliation rules perform a different but complementary function: after records are matched, they determine which source value should represent single-valued unified attributes such as First Name.

A Data Graph doesn't perform entity resolution. It exposes primary and related data efficiently for personalization or other consumption use cases after the underlying model exists. An Audience Flow orchestrates communications to an audience; it doesn't unify identities.

The uploaded bank correctly identifies B. Salesforce's official Identity Resolution documentation confirms that rulesets contain match and reconciliation rules that link multiple source profiles into unified profiles.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Rulesets, Match Rules, and Reconciliation Rules.

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

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.

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

The appropriate solution is a Lightning Report based on the Marketing Performance Semantic Data Model . Salesforce's marketing reporting architecture provides semantic-model-backed report types that combine message-definition and engagement information into a unified reporting layer. The Marketing Performance Semantic Model specifically contains information about message send definitions and engagement data, allowing marketers to create detailed custom analytics instead of being limited to predefined dashboards.

This is important because unsubscribe information and unsuccessful message delivery are engagement-level events rather than ordinary Campaign Member attributes. A Campaign Member-based custom report therefore lacks the complete messaging and engagement model required for this analysis. Marketing Insights for Agentforce Sales is also designed for sales-oriented marketing intelligence and isn't the custom reporting mechanism requested here.

The uploaded source identifies option B as the answer. Salesforce documentation confirms that the Marketing Performance Semantic Model contains send-definition and engagement data and is available for custom analytics reporting.

Study Guide Reference: Analytics and Performance Insights → Marketing Performance Intelligence → Semantic Data Models and Custom Reporting.

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

Marketing Cloud Next requires an authenticated sending domain for branded email delivery. The domain is configured under Unified Messaging and authenticated through DNS records supplied by Salesforce. DKIM is a core part of this authentication process.

Salesforce states that Marketing Cloud Next uses Unified Messaging for outbound email and that an activated authenticated domain is required for email sending. Current Marketing Cloud Next DKIM keys are 2048-bit by default, and Salesforce uses outbound CNAME records to establish the DKIM authentication chain. Once the domain is active, From addresses using that domain can be configured for legitimate branded delivery.

A tracking domain serves a different purpose: it supports branded links, redirect tracking, or related channel tracking functionality. It doesn't substitute for the authenticated email-sending domain. An "Authorized domain" verified solely by an ownership TXT record isn't the Marketing Cloud Next sending-domain configuration described by Salesforce.

The uploaded bank correctly identifies A. Salesforce's May and August 2026 documentation confirms that an authenticated domain is mandatory for Marketing Cloud Next sending and that DKIM authentication uses generated DNS records.

Study Guide Reference: Platform Setup and Governance → Unified Messaging Setup → Authenticated Sending Domains and DKIM.

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

Marketing Cloud Next evaluates consent at the intersection of a contact point, engagement channel, and communication subscription . Salesforce's consent model is deliberately granular so that customers can make different decisions for different channels and categories of marketing content.

For example, the same customer might opt in to the "Weekly Deals" subscription by SMS while declining the same subscription by email. They might simultaneously remain opted in to a separate "Product Updates" email subscription. Salesforce explicitly states that customers give consent for each channel type associated with a communication subscription.

The contact point is also significant. Consent is tied to contact-point values—such as a particular email address or telephone number—rather than simply being stored as one global preference on the Unified Individual. Salesforce notes that a Unified Individual can contain multiple contact points and that consent checks evaluate those contact points during sending.

Options B and C incorrectly describe consent as globally shared.

The source bank correctly identifies A.

Study Guide Reference: Consent → Consent Evaluation → Contact Point, Channel, and Communication Subscription.

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

The Communication Subscription Channel Type object represents the relationship between a particular Communication Subscription and an Engagement Channel Type. Salesforce defines it as the object that specifies the engagement channel that can be used for a given communication subscription.

Therefore, if "Product Announcements" supports both Email and SMS , two subscription-channel relationships exist: Product Announcements + Email, and Product Announcements + SMS. Each combination requires its own Communication Subscription Channel Type record.

Salesforce's Data 360 mapping requirements reinforce this relationship. The Communication Subscription Channel Type DMO includes both a Communication Subscription ID and an Engagement Channel Type ID , confirming that each record associates one subscription with one channel.

Contact points are associated with individual subscribers and consent records, not with the definition of the subscription/channel relationship itself, so A is incorrect. OPT_IN and OPT_OUT states are stored as consent information and don't cause the two Communication Subscription Channel Type records described here.

The uploaded bank correctly keys C.

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

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

The Privacy Consent Status component is specifically intended to expose Marketing Cloud Next consent information on Lead and Contact record pages. Salesforce documents that the component retrieves the relevant email addresses and phone numbers from the CRM record and displays the consent state associated with those contact points. Authorized users can therefore review and manage communication preferences while working directly from the person's Salesforce record.

This is materially different from Data 360 Related Lists, which surface related Data 360 information but aren't the dedicated consent-management interface. Data 360 Profile Insights is used for profile and calculated insight information, such as marketing scores, rather than managing channel and subscription consent.

Salesforce also clarifies that the ordinary HasOptedOutOfEmail field isn't the Marketing Cloud Next consent mechanism. Marketing Cloud Next consent is stored through its dedicated consent model and surfaced through the consent component.

The uploaded master correctly keys A. Current Salesforce documentation explicitly names the Privacy Consent Status component for displaying consent associated with email and phone contact points.

Study Guide Reference: Consent → Managing and Reviewing Consent → Privacy Consent Status Component.

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

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.

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

Option A applies the least computationally intensive feature appropriate to each requirement. Days Since Last Login is fundamentally a row-level derived value based on an existing login-date attribute, so a Data 360 data-stream formula can derive a supplemental field without requiring an analytical aggregation pipeline. Salesforce supports formula fields derived from other fields, functions, and operators during data-stream processing.

Loyalty Tier based on lifetime spend , however, requires aggregation across potentially many transaction records for each customer. A batch calculated insight is designed for that type of multi-record calculation. Because the email is monthly, a daily batch calculation is adequate; there is no business need to pay the higher processing cost associated with streaming computation.

Streaming calculated insights consume Data 360 Streaming Pipeline Flex Credits based on processed records. Batch calculated insights are billed under Data 360 Prep according to underlying records processed. Therefore, unnecessary streaming should be avoided when sub-second freshness isn't required.

A formula-field caveat is that Salesforce recalculates a data-stream formula when the corresponding record is refreshed or changed, so implementation scheduling must ensure the value is sufficiently current for the monthly send.

The master bank keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data 360 Calculations → Formula Fields, Calculated Insights, and Credit Optimization.

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