MC-Con-201 Salesforce Certified Marketing Cloud Next Consultant Questions and Answers

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.

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

Omni-Channel routing is the Salesforce architecture used to assign inbound conversations to Agentforce Service Agents or human service representatives. Conversational Email integrates Marketing Cloud Next with Agentforce and Service Cloud so that customer replies can remain within the same conversation thread and be routed appropriately.

Salesforce documents Omni-Channel flows as the mechanism for routing conversation-associated records to Agentforce. In general Agentforce channel architecture, the inbound Omni-Channel flow receives the conversation record and routes work to the configured Service Agent. For Conversational Email specifically, Salesforce also documents routing types such as Omni-Flow for directing a reply to a Service Agent.

A generic record-triggered flow on Email Message doesn't provide the complete channel-routing behavior required for Agentforce ownership. A platform-event trigger likewise isn't the prescribed Conversational Email routing architecture.

The uploaded master bank identifies B.

Study Guide Reference: Agentforce and AI Innovation → Conversational Email → Omni-Channel and Agentforce Routing.

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

Basic Marketing Cloud Next implementation spans both Marketing Cloud administration and Data 360 architecture , so administrative access must cover both domains. Salesforce identifies the Marketing Cloud Admin permission set as the administrative role that can configure Marketing Cloud Next settings and manage core marketing functionality. The Data Cloud Architect permission set—the current Salesforce documentation terminology for the architectural Data 360 role—provides access to Data 360 Setup, data modeling, data streams, identity resolution, and related infrastructure.

Accordingly, option A represents the required combination among the available choices: the Data 360/Data Cloud architectural permission set together with Marketing Cloud Admin. Marketing Cloud Manager is oriented toward campaign and marketing operations rather than full administrative configuration, so B doesn't provide the required administrative scope. Data 360 Activation Manager is more narrowly focused on activation-related responsibilities and doesn't replace the broader architecture capabilities needed for foundational implementation.

The uploaded question bank identifies A as the correct response.

Study Guide Reference: Platform Setup and Governance → Getting Started with Marketing Cloud Next Setup → Administrator personas and permission sets.

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

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.

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

Marketing Cloud Next provides on-canvas Flow Analytics for supported marketing-flow elements. Salesforce identifies this capability as On-Canvas Insights and states that recent performance metrics for active and completed flows can appear directly on the flow canvas. To expose those insights, marketers select the relevant flow element and enable or review insights from its Analytics tab.

For messaging elements such as Send Email Message, these analytics allow marketers to evaluate element-level execution and engagement without relying on low-level automation logs. Depending on the edition and configuration, detailed Flow Performance analytics are powered by Tableau Next, and users may require the Tableau Next Included App Business User permission set.

Debugging the flow is useful for validating logic, variables, and execution paths during development, but it isn't the intended interface for production engagement metrics. Flow Interview logs similarly focus on flow execution and troubleshooting rather than marketer-facing email engagement analysis.

The uploaded master keys A. Salesforce's current Flow Builder documentation specifically states that On-Canvas Insights are enabled from the Analytics tab of a flow element's editing panel .

Study Guide Reference: Analytics and Performance Insights → Flow Analytics → On-Canvas Insights and Messaging Element Performance.

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

Marketing Cloud Next uses an explicit opt-in consent model for promotional marketing. Absence of an opt-out doesn't mean that an individual is eligible to receive marketing messages. Salesforce explicitly states that a Prospect, Lead, or Contact without a consent value is considered opted out by default for marketing channels and communication subscriptions.

Therefore, recipients must have valid affirmative consent associated with the appropriate contact point, channel, and communication subscription. If the "New Product Promotion" campaign uses its own communication subscription, customers who lack the necessary OPT_IN state are suppressed rather than treated as implicitly eligible.

Option A incorrectly assumes an opt-out-only consent model. Option C makes the same incorrect inference: the absence of an OPT_OUT record isn't equivalent to affirmative permission.

This distinction is critical during initial implementation because existing CRM records aren't automatically opted in. Salesforce recommends importing or otherwise establishing valid consent before promotional messaging begins.

The source bank correctly identifies B. Salesforce's July 2026 documentation explicitly states that consent isn't default opt-in and that promotional messages are rejected when the recipient lacks an affirmative opt-in.

Study Guide Reference: Consent → Consent Validation → Explicit Opt-In and Default Consent Status.

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

Marketing Cloud Next's native lead-generation architecture uses a landing page, form, and flow . Salesforce states that forms collect visitor information, landing pages host the forms, and flows process the submitted values. When a Signup Form campaign is used, Marketing Cloud Next can automatically create and connect these assets.

The form can use Salesforce Lead as a data source. After submission, the associated flow performs the appropriate CRM actions, such as creating the Lead and optionally creating consent or sending follow-up communications. Salesforce specifically describes a form as having two functional pieces: its fields/settings and the flow that processes submitted data.

A form handler is generally used when integrating external forms rather than when building the registration experience natively on a Marketing Cloud Next landing page. A separate Data 360 data stream isn't required simply to create the CRM Lead from the native form.

The uploaded master bank identifies option B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Forms and Landing Pages → Signup Form Campaigns and Lead Creation.

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

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.

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

The uploaded bank keys C , which places the automation at the layer where the actual email-click engagement exists: Data 360 engagement data.

Current Salesforce documentation supports the core architecture. Create Consent is supported in Data Cloud/Data 360-triggered flows and can be used to automate consent updates based on behavioral data such as a link click . Salesforce explicitly describes link clicks and form submissions as valid sources for automated Create Consent processing.

The original CRM Lead record doesn't itself become updated merely because an email engagement event occurred, so a conventional Lead record-triggered flow is an unreliable trigger for this behavior. A Data 360-triggered flow can instead react to the appropriate engagement DMO event and pass the relevant sending contact point into Create Consent.

The source specifically identifies the Email Engagement DMO, click criteria, link URL, and Send time Email Address fields. Those exact field-level details are source-derived; current public Salesforce documentation independently confirms the broader Data 360-triggered + Create Consent pattern.

Study Guide Reference: Consent → Behavioral Consent Automation → Data 360-Triggered Flow and Create Consent.

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

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.

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

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.

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

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.

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

Among the supplied choices, A represents the Marketing Cloud Next consent-layer update rather than manipulating the ordinary CRM Email Opt Out field . Current Salesforce terminology has evolved: service representatives can view and update Marketing Cloud Next consent from the Salesforce record using the Privacy Consent Status Lightning Web Component , while automated changes use Create Consent/Consent Request.

Salesforce explicitly states that the standard HasOptedOutOfEmail field on Lead or Contact isn't used by Marketing Cloud Next consent by default. Therefore, C doesn't reliably unsubscribe the person from Marketing Cloud Next communications.

A preference page is normally the customer's self-service experience. Customers can use an "unsubscribe from all emails" preference-page action, which sets them to OPT_OUT for all applicable subscriptions, but the scenario describes a service representative acting on the customer's request.

The uploaded source keys A. The phrase "Consent Status flow element" reflects older/imprecise terminology; the current manual interface is Privacy Consent Status.

Study Guide Reference: Consent → Manual Consent Management → Privacy Consent Status and Subscription-Level Opt-Out.

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

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.

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

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.

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

An Actionable List is the correct audience mechanism when marketers need to target a fixed, specifically selected collection of existing Leads or Contacts without building a Data 360 segment. Salesforce describes Actionable Lists as static collections suited to known individuals, such as imported event attendees or other deliberately selected contacts. An Audience Flow can use a List as its audience source.

For personalization, Content Variables provide dynamic placeholders whose values can be populated by Flow at runtime. Salesforce allows content variables to map to data sources available to Flow, including Salesforce records and other connected data. This makes it possible to supply attributes such as First Name and Account information during message execution.

A Data Graph is designed primarily as a personalization data source and isn't itself the appropriate fixed-list audience source described here. Option A unnecessarily introduces a marketing object and AMPscript when the records already exist as Contacts.

The uploaded master bank identifies C. Salesforce confirms that Audience Flows support List sources and that Actionable Lists represent fixed audiences.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Audience Flows → Actionable Lists and Content Variables.

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

An Audience Flow with Segment as the audience source is specifically designed for scheduled marketing communications to populations defined in Data 360. Salesforce states that an Audience Flow runs on a schedule and can use a Segment, List, Record, or Campaign as its audience source. When Segment is selected, the resulting flow targets members of a published Data 360 segment.

Because NTO already has a defined population of high-value customers, the consultant should use that segment rather than manually retrieving DMO records. The weekly schedule can then control campaign execution, while the segment determines membership based on current customer profile and behavioral attributes.

A generic schedule-triggered flow with Get Records bypasses the purpose-built Marketing Cloud Next segment-flow architecture. A Data 360-triggered flow is intended primarily to react to Data 360 record changes, not to execute a recurring weekly campaign against an audience.

Salesforce also recommends ensuring that the underlying segment is published and considering its publication schedule before the flow runs. The uploaded source keys B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Audience Flows → Segment Audience Source and Scheduling.

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

Identity Resolution can be a significant consumer of Data Services Credits because profile-unification jobs process qualifying source records. Salesforce specifically recommends controlling unnecessary identity-resolution execution when configuring or modifying rulesets. One supported optimization is to disable Run jobs automatically while making configuration changes and use Run Now deliberately when processing is actually required. This prevents repeated automatic runs while administrators are iterating on match, reconciliation, or filtering logic.

Salesforce also recommends keeping only one active ruleset when possible to reduce usage costs. Therefore, option B would move in the wrong direction: maintaining multiple active rulesets can increase processing and credit consumption rather than reduce it.

Option C is also inappropriate. Recreating data streams can cause unnecessary data reprocessing and isn't the recommended credit-management technique. Data filtering and sensible scheduling are much more controlled approaches.

Because the question states that row-count optimization has already been performed, controlling automatic identity-resolution jobs is the best additional measure among the available options. The master bank keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Data Services Billable Usage Types and cost optimization.

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

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.

The agency users need the Marketer-Standard Business Unit role because their responsibilities include both creating marketing assets and deploying campaigns.

Salesforce states that users with the Marketing Cloud Admin or Marketing Cloud Manager permission set can be added to a Business Unit as Marketer-Standard members. These users receive the Content Manager role in the Business Unit's marketing workspace, allowing them to create, edit, view, and publish content. They can also activate campaign flows in that Business Unit.

Marketer-ReadOnly is insufficient because Salesforce explicitly states that ReadOnly members can't activate campaigns and don't receive access to the Business Unit's marketing workspaces. This would prevent the agency from performing the tasks described.

Adding users directly to the Data Space isn't the proper Marketing Cloud Next access-governance model. Business Unit membership automatically grants access to its mapped Data Space according to the Business Unit architecture.

The source bank correctly identifies C.

Study Guide Reference: Platform Setup and Governance → Business Units → Marketer-Standard and Marketer-ReadOnly Roles.

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

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.

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

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.

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

Marketing Cloud Next supports both Salesforce Record and Offer as native email personalization data sources. Salesforce Record is designed to surface current business information from Salesforce objects. Salesforce specifically notes that marketers can add a Salesforce Record data source and reference Salesforce object fields directly in email content.

That makes it appropriate for a recipient's assigned sales representative when the representative relationship is maintained in Salesforce/Agentforce Sales data.

The Offer data provider is specifically designed for promotions. Salesforce states that marketers can add an Offer as an email data source and use merge fields for values such as the offer name, description, or coupon code . It also supports multiple offer providers and conditional targeting based on customer attributes.

An Apex Class would be unnecessary custom logic for retrieving an ordinary Salesforce business attribute. A Data Graph also isn't the natural mechanism for a Marketing Cloud Next-managed, time-sensitive offer code when the purpose-built Offer data source exists.

The uploaded bank identifies A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization Data Sources → Salesforce Record and Offer.

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

An On-Demand Flow is designed specifically for marketing interactions initiated externally through an API request. Salesforce allows external applications to invoke an On-Demand Flow through the REST API using the Flow invocable-action endpoint and provide required runtime inputs with that request.

This architecture fits an external airline operational system that already knows when an itinerary has changed and which passengers are affected. The external service can initiate the flow immediately instead of waiting for a segment refresh or a scheduled marketing process. The flow can then execute personalized SMS messaging using the passenger and itinerary information supplied through its runtime context.

A dynamic segment is inefficient for an event where the initiating system already knows the affected audience and requires immediate action. Segment publication introduces additional processing and isn't necessary merely to reconstruct the passenger set. Option C uses generic Flow terminology but doesn't identify the purpose-built API-triggerable Marketing Cloud Next flow type.

The uploaded master bank identifies A. Salesforce explicitly states that On-Demand Flows can be invoked via REST API for immediate SMS interactions initiated by external customer activity.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → On-Demand Flows → REST API-Triggered Messaging.

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

An Actionable List is specifically intended for a fixed collection of known individuals. Salesforce even uses people who signed up for marketing at a trade show as a canonical example of when an Actionable List is appropriate.

Unlike a dynamic segment, which continually recalculates membership using profile attributes or behavioral criteria, an Actionable List remains a defined static audience. That makes it ideal for an imported set of event attendees who need to receive a one-time communication.

Salesforce supports creating an Actionable List by importing a CSV containing the members. The list can contain Leads or Contacts, and marketers can subsequently select that list as an audience source in Marketing Cloud Next automation.

A Segment would introduce unnecessary dynamic filtering and publication processing when audience membership is already explicitly known. A Marketing Object is a tabular storage structure used for marketing-related reference or personalization data; it isn't the appropriate audience-management construct for this requirement.

The uploaded master bank correctly keys A. Salesforce's current documentation explicitly describes Actionable Lists as static collections ideal for reaching known individuals such as trade-show registrants.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Audiences → Actionable Lists versus Dynamic Segments.

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

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.

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

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.

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

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.

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