Explanation:
After identity resolution runs, consultants and admins need tools to verify that unification worked correctly (e.g., correct records merged, attribute reconciliation accurate, no false positives). Salesforce Data Cloud provides three native features specifically designed for inspecting and validating unified profiles.

Correct Options:

A. Identity Resolution
The Identity Resolution ruleset detail page includes a “Preview” or “Run Preview” function that shows sample unified individuals, how many source records matched under each rule, and the resulting attribute values after reconciliation. It is the first validation step before publishing the full ruleset.

C. Data Explorer
Data Explorer allows drilling into the Unified Individual and Unified Link Individual DMOs directly. Consultants can query, filter, and view the full list of unified profiles, see which source Individuals were linked to each unified record, and inspect reconciled attribute values (e.g., which source won for First Name, Email, etc.).

D. Profile Explorer
Profile Explorer is the user-friendly UI for viewing a single unified customer profile. Search by email, phone, or ID, then see the timeline, all reconciled attributes, segment membership, and—most importantly—the “Source Records” tab that lists every original record that was unified into this profile and how reconciliation rules were applied.

Incorrect Options:
B. Query API – While technically possible to query unified DMOs via the REST/GraphQL Query API, it is not listed as a standard validation feature in the exam context and is less practical than the UI tools above.

E. Data Actions – Used for triggering journeys or exports, not for inspecting or validating unification results.

Reference:
Salesforce Help: “Validate Identity Resolution Results” – recommends Identity Resolution preview + Data Explorer + Profile Explorer.

Explanation:
NTO's requirement is for logical data separation and security between its two brands within a single Data Cloud org. This is a tenant-level isolation need, not just a matter of having separate ingestion paths or data models. The capability must enforce that data, segments, and insights for one brand are completely inaccessible from the context of the other, while allowing centralized platform management.

Correct Option:

C. Data spaces for each brand:
This is correct. Data Spaces are specifically designed for this multi-brand or multi-business unit use case. They provide logical partitioning within a single Data Cloud org, creating separate, secure environments. Each brand (Outdoor Clothing, Gourmet Food) would have its own Data Space, ensuring complete data isolation, security, and dedicated business processes.

Incorrect Option:

A. Data sources for each brand:
Using separate data sources only manages how data is ingested. Once ingested, the data would reside in a common data lake and would not be automatically isolated by brand, failing the security requirement.

B. Data model objects for each brand:
Creating separate model objects (e.g., Gourmet_Customer__dlm, Clothing_Customer__dlm) organizes the schema but does not enforce data security or prevent users with access to one object from seeing the other. It is a structural choice, not an isolation capability.

D. Data streams for each brand:
Data Streams are connectors for bringing data in from external storage. Like data sources, they are an ingestion concern and do not provide any data security or logical separation once the data lands in the platform.

Reference:
Salesforce Help - "What Are Data Spaces?"

Explanation:
To move rapidly changing data—such as inventory levels—into Data Cloud, the organization needs a streaming ingestion method capable of near-real-time, scalable data flow. The Ingestion API is designed precisely for high-velocity operational data sources. It supports fast, scalable, event-based data ingestion, making it ideal for scenarios where inventory changes frequently and must be reflected quickly for segmentation, personalization, analytics, or downstream activation.

Correct Option:

C — Ingestion API:
The Ingestion API provides low-latency, high-throughput data streaming into Data Cloud. It supports JSON payloads pushed directly from enterprise systems and can handle millions of events. This makes it perfect for inventory-level updates, where stock counts fluctuate rapidly and accuracy is critical for commerce, personalization, and operational decisions. It is the only option specifically built for real-time or near-real-time ingestion at scale.

Incorrect Options:

A. Cloud Storage Connector:
The Cloud Storage Connector ingests data from cloud file storage such as AWS S3, Azure Blob, or GCP. This is a batch-based ingestion method, not suitable for fast, real-time streaming. It works well for periodic data loads or historical datasets but not for rapidly changing inventory values requiring instant updates.

B. Commerce Cloud Connector:
This connector syncs commerce data such as orders, products, and customer information from Salesforce Commerce Cloud. It does not stream external inventory management data and is not built for near-real-time operational updates. It focuses on integrating Commerce Cloud datasets, not general-purpose streaming ingestion.

D. Marketing Cloud Personalization Connector:
This connector brings behavioral and personalization data from Marketing Cloud Personalization (formerly Interaction Studio) into Data Cloud. It is not intended for inventory data nor for real-time ingestion from external inventory systems. It focuses on customer interactions, not operational stock data.

Reference:
Salesforce Data Cloud: Ingestion API Overview

Explanation:
To update a field in Salesforce CRM immediately after a record changes in a Data Model Object (DMO), the consultant should use Data Actions. Data Actions enable real-time or near-real-time operational workflows by triggering updates or actions in external systems (like Salesforce CRM) directly from Data Cloud, ensuring that CRM records reflect the latest information without waiting for batch processes.

Correct Option:

B — Data Actions
Data Actions allow Data Cloud to push changes to external systems, such as updating a CRM field when a DMO record changes. They are triggered automatically based on changes in the data, enabling real-time synchronization and keeping operational systems up-to-date. This approach ensures consistency across platforms and supports business processes requiring immediate updates.

Incorrect Options:

A — Data share target
Data Share Targets are used to define where segments or datasets are exported (e.g., Marketing Cloud, S3). They do not perform record-level updates in real time to external systems like CRM.

C — Rapid segments
Rapid Segments allow for fast audience creation for segmentation and activation but do not trigger operational updates in external systems. They are used for marketing purposes, not CRM field updates.

D — Streaming data transform
Streaming Data Transforms standardize, cleanse, or enrich incoming data in real-time within Data Cloud but do not push updates to external systems like CRM. They operate inside Data Cloud only.

Reference:
Salesforce Data Cloud: Data Actions Overview

Explanation:
In Data Cloud, when activating a segment to a destination like Marketing Cloud or Salesforce Sales Cloud, you can include specific data attributes to personalize the outreach. These attributes must be discrete pieces of information attached to the unified customer profile. Metrics and filters from a calculated insight are computational results or conditions, not directly activatable data fields.

Correct Option:

D. "branch" (dimension):
This is correct. A dimension from a calculated insight, such as "branch," represents a categorical attribute that is part of the customer's profile data. This attribute (e.g., "New York Branch") can be included in an activation payload to route customers or personalize communications based on their assigned branch.

Incorrect Option:

A. "high net worth" (filter):
This is incorrect. A filter is a condition or rule used to define a segment population (e.g., Banking Value > $1,000,000). It is not a storable or activatable data attribute itself; it's the logic that qualifies the customer for the segment.

B. "branch" (dimension) and "banking value" (metric):
This is partially incorrect. While "branch" is activatable, "banking value" is not. A metric is a computed numerical value. You cannot directly activate the computed metric itself as a profile attribute in the same way you can activate a descriptive dimension.

C. "banking value" (metric):
This is incorrect. As a calculated metric, "banking value" is the result of an aggregation or formula. Activation payloads are typically composed of dimensional attributes, not the underlying measures used in insights, which are often transient for analytical purposes.

Reference:
Salesforce Help - "Activate Segments and Data"