Salesforce MC-Con-201 Dumps Questions Answers

Match rules determine whether separate source profiles represent the same real-world individual. Data 360 Identity Resolution evaluates configured attributes and matching methods—such as normalized email, normalized phone, name, party identifiers, or device identifiers—to decide which Individual records should belong to the same Unified Individual.

Salesforce provides default and custom match rules. For example, default configurations can compare fuzzy first name, exact last name, and normalized email or telephone values. Multiple rules can coexist within an Identity Resolution ruleset.

Reconciliation rules serve a later and fundamentally different purpose. After records have been matched, reconciliation determines which values become representative unified-profile attributes—for example, whether CRM or loyalty should supply the preferred First Name. Therefore B confuses matching with attribute-value selection.

Identity Resolution also doesn't destructively merge the source records into one Individual record. Source profiles remain available and are linked through the resulting unified profile.

The uploaded master bank correctly identifies C.

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

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

Marketing Cloud Next manages promotional consent through communication subscriptions, channels, and contact points . A communication subscription represents a particular category of marketing content, such as product updates, newsletters, or promotions. Consent checks evaluate whether the relevant contact point has the required consent for the specific subscription and channel being used.

Consequently, opting out of the "Promotions" subscription creates an opt-out state for that subscription; it doesn't automatically revoke consent for a different subscription such as "Product Updates." Salesforce explicitly distinguishes a subscription-specific opt-out from a broader request such as unsubscribing from all email communications. Therefore, assuming the customer has valid opt-in consent for Product Updates, those communications can continue.

Option B incorrectly treats subscription consent as a single global email-address preference. Option C invents a 90-day consent-renewal requirement that isn't part of the Marketing Cloud Next consent model.

The uploaded question bank keys this question as A.

Study Guide Reference: Consent → Consent Management Fundamentals → Understanding Consent Concepts → Communication Subscriptions, Channel Types, Contact Points, and Consent Checks.

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

Option A aligns directly with Salesforce's recommended segmentation credit-optimization practices. Data 360 consumes segmentation credits when segments are processed and published. If source data changes only weekly, publishing the segment every day creates unnecessary processing with no meaningful freshness benefit. Salesforce specifically recommends reducing publication frequency and, where the use case permits, setting the segment so it isn't automatically scheduled.

Marketing Cloud Next Audience Flows also support republishing the target segment immediately before the flow executes . This provides the best of both approaches: the segment isn't repeatedly processed during the week, but the weekly promotional send still receives the most current membership immediately before execution.

Option B keeps the unnecessary daily processing schedule. Option C is even less suitable because real-time or streaming processing is unnecessary when underlying source data changes only once each week and can increase credit usage.

The uploaded master bank also identifies A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Segmentation → Scheduling, Republish Behavior, and Credit Optimization.

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