Salesforce MC-Con-201 Dumps

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.

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

Marketing Cloud Next currently supports three field data types for Marketing Objects: Text, Number, and Decimal .

Salesforce defines Text as a string value of up to 255 characters. Number stores positive or negative integers with up to 18 digits. Decimal stores positive or negative decimal numbers with up to 18 digits. These deliberately constrained field types make Marketing Objects suitable for lightweight campaign, lookup, promotional, localization, and personalization datasets.

Option B is incorrect because Formula isn't listed as a Marketing Object field type. Calculated logic can be handled through other platform capabilities, but formula isn't one of the three selectable types when defining a Marketing Object field.

Option C uses familiar programming terminology—String, Integer, Boolean—but those aren't the Marketing Cloud Next field labels and Boolean isn't currently one of the supported Marketing Object field types documented by Salesforce.

The uploaded master bank identifies option A. This item has direct current-documentation support: Salesforce's Marketing Object Data Types and Resource Allocations reference explicitly lists only Text, Number, and Decimal .

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Marketing Objects → Supported Data Types and Resource Allocations.

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

An On-Demand Flow invoked through the REST API is specifically designed for externally initiated, real-time automation in Marketing Cloud Next. Salesforce supports triggering this flow type by calling the Flow invocable-action REST endpoint. Input variables can be supplied with the request and then used by downstream flow actions.

That architecture is ideal for a one-time verification code. The external authentication service generates the code, calls the Marketing Cloud Next on-demand flow, passes the code and recipient information as input values, and the flow immediately uses those values in the Send Email Message action.

There is no reason to persist an ephemeral security value such as a one-time code into Data 360 merely so it can be read back by a Data Graph. Doing so adds ingestion and synchronization latency. Similarly, waiting for an Automation Event-Triggered Flow to detect streamed data introduces unnecessary infrastructure when the external system already knows exactly when the message must be sent.

The uploaded bank correctly keys C. Salesforce's On-Demand Flow release documentation explicitly states that REST API calls can trigger this flow type for externally initiated marketing interactions.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → On-Demand Flows → REST API Invocation and Runtime Personalization.

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

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

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

The Email Engagement dashboard is the purpose-built dashboard for analyzing standard email performance metrics across Marketing Cloud Next sends. Salesforce's Marketing Performance Intelligence package includes preconfigured Email Engagement reports and dashboard components for common KPIs including Total Emails Sent, Open Rate, Click-Through Rate, Bounce Rate, and Opt-Out Rate.

The dashboard provides visualizations such as status bar graphs, time-based activity graphs, campaign click-engagement rankings, email-send-status views, and detailed activity tables. This allows marketers to evaluate messaging performance without having to construct a custom analytics model.

Campaign Performance is broader and focuses on campaign-level outcomes across associated marketing activity rather than being the specialized email KPI view requested here. Unified Engagement History serves another purpose: it surfaces marketing engagement alongside CRM records such as Contacts, Leads, Accounts, and Opportunities for sales and service users.

Therefore, B precisely matches the requirement for an easy-to-use, cross-send email analytics dashboard.

The uploaded master bank also identifies B. Salesforce's 2026 Marketing Cloud Next reporting documentation explicitly lists Open Rate, Click-Through Rate, Bounce Rate, and related metrics in the Email Engagement dashboard.

Study Guide Reference: Analytics and Performance Insights → Marketing Performance Intelligence → Email Engagement Dashboard.

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

Option B is the currently verified Salesforce-supported approach. Marketing Cloud Next treats a prospect, Lead, or Contact without applicable consent as opted out by default. Therefore, before a new Contact can receive promotional marketing, a valid opt-in must exist for the relevant contact point, channel, and communication subscription .

Salesforce's current 2026 guidance states that consent changes originating from CRM record creation or updates should be handled with an Automation Event-Triggered Flow using the Prospect, Lead, Contact, or Related Record Change event, followed by the Consent Request/Create Consent action . That supported action writes the consent so that Marketing Cloud Next honors it at send time.

Option C is explicitly insufficient because HasOptedOutOfEmail isn't automatically synchronized with Marketing Cloud Next consent. Option A is misleading because directly manipulating a separate CRM consent record doesn't itself establish supported Marketing Cloud Next sending consent.

The uploaded document keys this question as A. However, Salesforce's updated July–August 2026 documentation supersedes that approach and explicitly directs implementations to Create Consent/Consent Request.

Study Guide Reference: Consent → Creating and Updating Consent → Create Consent / Consent Request Flow Action.

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

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.

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

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.

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

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

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

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.

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

Salesforce specifically recommends optimizing Run Mode, scheduling frequency, end conditions, and Lookback Window to reduce Data 360 segmentation credit consumption.

Run Mode determines whether a segment publishes automatically or only when requested. During development or testing, Salesforce recommends avoiding unnecessary scheduled publishes. Frequency directly affects how often Data 360 recomputes segment membership; running more often than the source data changes wastes credits. The Ends setting prevents a segment from continuing to execute after the business need has expired.

The Lookback Window is equally important because it controls how much historical data must be evaluated. Narrowing the window to the minimum period required by the use case reduces records processed and therefore processing costs.

The criteria identified in option B affect segment definition and results but don't represent the specific billing-optimization controls Salesforce highlights before processing begins. Option A combines unrelated configuration concepts.

The uploaded source correctly keys C. Salesforce's current billing guidance explicitly names Run Mode, Frequency, Ends, and Lookback Window as settings to optimize for lower segmentation consumption.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Segmentation → Billing Considerations and Credit Optimization.

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

A Marketing Object is the Marketing Cloud Next-native structure for storing tabular marketing data used in campaigns, personalization, briefs, and flows. Salesforce allows marketers to create a Marketing Object directly from a CSV upload; the resulting object contains the columns defined in the source file, and Marketing Cloud Next infers the appropriate field types during import.

This makes Marketing Objects suitable for datasets such as promotional codes, localized content, product reference information, campaign-specific lookup tables, or other relatively lightweight structured data that doesn't need to be harmonized into the full Data 360 customer model.

An Actionable List is intended to represent a fixed audience of known Leads or Contacts. It isn't a general-purpose tabular data store. A Data 360 file-upload data stream is appropriate when data must be ingested and mapped into Data 360 DMOs, but the scenario asks specifically for tabular data used for marketing purposes, where Marketing Objects provide the more direct Marketing Cloud Next capability.

The uploaded question bank identifies C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Marketing Objects → Importing and Managing Tabular Marketing Data.

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

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.

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

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.

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

This requirement combines conditional content selection with one-to-many repeated data , so two different Marketing Cloud Next personalization capabilities are appropriate.

For the subject line, a variation can be associated with targeting rules based on the customer's preferred language. Each language can therefore receive the appropriate localized subject-line version, with a fallback variation available when no targeting condition matches.

For the recommended-product list, a Repeater is the correct component. Salesforce states that repeaters display a series of items such as products, order updates, events, or promotions. The repeater can connect to a Data Graph attribute containing related records, and nested components can use merge fields from each repeated item.

Option C would only be correct if the Data Graph itself contained the fully localized subject text to merge directly. The scenario instead says the Contact stores the preferred language , which is decision criteria—not necessarily the translated subject line itself. Option B unnecessarily relies on AMPscript.

The uploaded source keys A. Salesforce documentation confirms both variation-based dynamic content and Data Graph-backed repeaters.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Dynamic Content → Variations, Targeting Rules, and Repeaters.

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

The source bank identifies B because Marketing Cloud Next Business Units establish organizational boundaries not only for data but also for marketing workspaces and content.

Current Salesforce documentation supports this architecture. Each Business Unit has one or more marketing workspaces, and a workspace is assigned within that Business Unit's configuration. When Business Units are created, a default marketing CMS workspace is assigned to each unit. Consequently, content created only inside the corporate Business Unit's workspace doesn't automatically become available as reusable content to marketers working within other Business Units.

Salesforce provides Common Assets specifically to solve the cross-Business-Unit distribution problem. Content from one workspace can be posted to Common Assets, after which members of other Business Units can copy the approved asset into their own workspace.

Adding regional users as contributors to the corporate workspace would weaken the intended Business Unit governance model. Publishing an asset within the corporate workspace also doesn't automatically distribute it across Business Units.

Study Guide Reference: Platform Setup and Governance → Business Units → Marketing Workspaces and Cross-Business-Unit Content Governance.

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

Einstein Engagement Scoring is designed to predict the likelihood that an individual subscriber will engage with future email communications. Salesforce states that the model predicts email opens and clicks, subscriber retention, web conversion, and overall engagement for individual consumer contacts.

Those predicted likelihood values can be used to identify customers with low engagement propensity. A marketer can therefore segment, filter, suppress, or branch customers according to their predicted open or click probability before an audience flow sends a message.

Send Time Optimization solves a different problem. STO assumes that a recipient is going to receive the communication and predicts when that person is most likely to engage. It doesn't primarily determine whether a low-propensity customer should be excluded. Messaging Insights isn't the predictive subscriber-level engagement scoring capability described in this requirement.

Salesforce also stores the output in the Email Engagement Score DMO , which supports reporting and audience analysis based on open, click, and subscription likelihood.

The uploaded master bank correctly keys A. Salesforce's current Einstein Engagement Scoring model card confirms that it predicts opens, clicks, retention, and overall engagement.

Study Guide Reference: Agentforce and AI Innovation → Einstein Engagement Scoring → Predictive Audience Optimization.

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

Salesforce provides the Device to Known Identity Resolution rule specifically to associate anonymous tracked visitors with known Unified Individual profiles.

Current Marketing Cloud Next setup documentation states that an Individual Identity Resolution ruleset should include an Identity Match DMO match criterion where Identity Match Type is matched exactly to device-to-known. Salesforce explains that this recommended rule attributes web-tracking activity to the correct Unified Individual.

This architecture exists because anonymous website engagement initially contains a device or visitor identity rather than ordinary CRM identity attributes. Once the visitor becomes identifiable—for example, through a recognized interaction—the Identity Match relationship enables Data 360 to stitch that visitor identity to the known Individual.

Option A incorrectly proposes manually altering identity relationships with Flow. Option B assumes Website Engagement should be directly matched to Individual using email, which bypasses the specialized identity-stitching mechanism Salesforce provides.

The uploaded master bank identifies C.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Identity Match DMO and Device-to-Known Matching.

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

Data 360 supports source-record filters directly on identity resolution rulesets . These filters act as preprocessing gates that determine which records from the ruleset's primary DMO enter that particular unification pipeline.

This is exactly the appropriate architecture when two populations share the same primary DMO but must be unified independently. The consultant can configure criteria distinguishing B2B from B2C records and apply complementary filters to the respective rulesets.

Salesforce specifically identifies separation of B2B and B2C populations as a valid ruleset-filter use case. For example, records can be filtered using an account type, customer type, record type, or other partition-level attribute so that business records don't enter the consumer ruleset and vice versa.

Creating separate DMOs simply to achieve identity-processing isolation isn't necessary when the records properly belong to the same canonical Individual model. Filtering source DLOs also places the separation at the wrong architectural layer because identity-resolution filtering is supported directly at the ruleset level.

The uploaded bank keys B. Salesforce's current ruleset documentation explicitly recommends filters for broad partition-level segregation, including B2B versus B2C scenarios.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Identity Resolution → Ruleset Source Filters.

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

An activation-triggered flow requires an activation whose Activation Target type is Data 360 . Salesforce explicitly states that activation-triggered flows support only activations created with Data 360 as the activation target type. Although Flow Builder may display activations associated with other target types, selecting an unsupported type results in an error when the flow is saved.

The sequence is therefore: create or publish the target audience segment, create a Data 360 activation target , configure an activation that publishes the segment to that target, and then create an activation-triggered flow using that activation. When the activation completes, records are written into the Audience DMO and the associated flow starts automatically. Salesforce's Data 360 activation-target documentation confirms this architecture.

"Segment" isn't itself an Activation Target type; it is the audience being activated. Loyalty similarly isn't the required target for this Flow architecture.

The uploaded question bank correctly keys option A.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Activation-Triggered Flows → Data 360 Activation Targets.

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

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.

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

The Communication Subscription DMO represents the category or purpose of marketing communication itself. Examples include Product Updates, Weekly Deals, Newsletters, Promotions, or Events. Salesforce's Marketing Cloud Next documentation directs marketers to create a communication subscription for each category of marketing content they send.

After creating a Communication Subscription, one or more channel types—such as Email, SMS, RCS, or WhatsApp where supported—can be associated with that subscription. This channel relationship is represented separately through the Communication Subscription Channel Type model.

Communication Subscription Consent , by contrast, stores the individual's actual consent state in relation to the relevant subscription/contact-point/channel context. It doesn't define the communication category itself.

Therefore, C correctly identifies the object representing the subscription concept that recipients can choose to receive or decline.

The source bank keys C. Salesforce's official documentation states that a communication subscription should be created for each category of marketing content, such as product updates, and that communication channels are then added to that subscription.

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

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

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.

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

The source bank recommends starting with a single lean Data Graph and expanding it as additional campaign requirements emerge . This approach avoids building unnecessary relationships and processing large datasets before an actual personalization use case requires them.

Current Salesforce guidance supports the underlying principle. Marketing Cloud Next personalization begins with a Unified Individual-based Data Graph containing required identity/contact fields plus the additional objects and fields required for personalization . Salesforce also notes that Data Graph cost and processing depend on data-model structure, participating records, refresh frequency, and fields updated. It recommends filters so that only records required for the use case are included.

Option A risks creating an oversized graph based on speculative future requirements. Option B introduces two graphs immediately even though the first campaign doesn't establish a requirement for separate demographic and transactional graphs. In the standard Marketing Cloud Next configuration without additional Personalization capabilities, Salesforce also notes that only one default Data Graph is used at a time.

Therefore, begin with the smallest useful graph, validate the campaign, and expand the graph as real personalization requirements develop.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graph Design → Use-Case-Driven Personalization Architecture.

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.

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

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.

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

Account Discovery is the purpose-built Marketing Cloud Next agent for examining existing business accounts and helping marketers identify additional people who may belong to relevant buyer groups. Salesforce lists several standard actions associated specifically with the Account Discovery agent, including Get Marketing Scores, Get Recent Activities, Summarize Conversations, and Find New Buyer Group Members . Those capabilities directly match this scenario: employees need account-level intelligence and want to discover additional stakeholders who can be nurtured.

Agentforce Employee is a broader employee-facing Agentforce capability rather than the specialized marketing agent designed for account discovery. Segment Creation addresses a different requirement: it translates audience descriptions into Data 360 segmentation criteria. It doesn't primarily analyze business accounts or identify prospective buyer-group participants.

Therefore, Account Discovery is the correct specialized agent. The uploaded master bank also identifies option B. Current Salesforce documentation explicitly includes Find New Buyer Group Members among the Account Discovery agent's standard actions.

Study Guide Reference: Agentforce and AI Innovation → Marketing Agents → Account Discovery and Buyer Group Identification.

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

Salesforce explicitly documents the required Data Graph structure and fields for Marketing Cloud Next personalization. The Data Graph should use Unified Individual as its primary DMO and include the appropriate relationship chain through Unified Link Individual and Individual to the applicable contact-point objects.

Within that structure, Salesforce specifically requires these fields:

Individual ID from the Individual object,

Email Address from Contact Point Email, and

Telephone Number from Contact Point Phone.

These identifiers allow Marketing Cloud Next to resolve personalized profile information to the proper communication contact points when rendering email and SMS content.

Option B incorrectly locates email address and telephone number directly on the Individual DMO. Those values belong to their dedicated contact-point DMOs. Option C incorrectly substitutes the Unified Individual Link ID for the required Individual ID.

This answer has particularly strong current documentation support: Salesforce published a dedicated Marketing Cloud Next knowledge article on March 12, 2026 listing exactly these three required fields. The uploaded master bank also keys A.

Study Guide Reference: Data Modeling, Identity Resolution and Segmentation → Data Graphs → Required Personalization Relationships and Fields.

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

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.

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