New Release MC-Con-201 Marketing Cloud Consultant Questions

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 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.

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

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.

After the consultant adds a sending domain, Unified Messaging generates the DNS configuration necessary to authenticate that domain. The required next step is to copy the generated DNS entries and configure them with the organization's DNS provider . Salesforce's current setup procedure states that the generated entries include CNAME and DKIM-related records , after which the consultant returns to Salesforce and verifies the domain.

Salesforce's 2026 DNS guidance states that Marketing Cloud Next authenticated domains require multiple CNAME records and that the outbound CNAME records provide DKIM authentication. The exact number of required CNAME entries can vary with the specific domain configuration and whether the domain is shared, but option B captures the required procedure.

A standalone TXT ownership record isn't sufficient for Marketing Cloud Next email authentication in this scenario. Sender Authentication Package is terminology associated primarily with the legacy Marketing Cloud Engagement configuration model and isn't how Marketing Cloud Next Unified Messaging authenticates a new sending domain.

The master bank keys B. Salesforce's current domain-authentication procedure confirms this DNS configuration sequence.

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

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