Explanation:
Data 360 offers near real-time data actions that monitor changes in Data Model Objects (DMOs) and Calculated Insights, publishing events to the Salesforce Platform when predefined conditions are met . These events can directly trigger an automation event-triggered flow in the core CRM org, enabling immediate orchestration of business processes. This is the architecture designed specifically for "in the moment" responsiveness to streaming data events .

Correct Option:

B. Real-time data actions via an automation event-triggered flow.
A data action can be configured to fire when a specific condition is detected (e.g., negative sentiment score), and its destination can be the Salesforce Platform. This publishes an event that an automation event-triggered flow subscribes to, allowing the flow to run immediately upon event ingestion . This capability is purpose-built for streaming, event-driven use cases requiring sub-second or near-instantaneous response .

Incorrect Option:

A. Manual activation to a Salesforce CRM target.
Manual activations are batch-oriented and require human intervention to initiate. They are not designed for immediate, event-driven triggers and would introduce significant latency.

C. Calculated insights published via real-time segment refresh.
Calculated insights run on a schedule and are not inherently real-time triggers. While they can be used in flows, the refresh cycle introduces delay, making this unsuitable for instantaneous service recovery scenarios .

D. Standard data actions via scheduled batch transforms.
Scheduled batch transforms run at defined intervals (e.g., hourly, daily) and are not designed for the immediate processing of individual streaming events. This approach would miss the "in the moment" requirement entirely.

Reference:
Salesforce Help: Data Actions in Data 360; Salesforce Help: Real-Time Capabilities in Data 360; Trailhead: Power Automation with Flows and Agents.

Explanation:

This question assesses the impact of performing a Full Sandbox refresh on an existing Data 360 configuration. It evaluates understanding of how metadata and ingested data behave differently during a sandbox refresh from production.

✅ Correct Option:

D. All Data 360 metadata is replicated from the current version of production instance, and the ingested records are cleared and must be re-ingested.
When a Full Sandbox is refreshed, Salesforce copies all Data 360 metadata (such as data streams, mappings, identity resolution rules, segments, and calculated insights) from the production environment. However, all ingested records, unified profiles, and calculated data are cleared. The team must re-ingest data and re-run processes to restore data volume for performance testing.

❌ Incorrect options:

A. The sandbox maintains its connection to the existing Data 360 instance, but all data mapping is reverted to Draft status.
The connection breaks after refresh due to Org ID change, and data mappings are replicated from production without reverting to Draft.

B. Only the identity resolution rules are deleted, while data streams remain active and continue to pull data from the refreshed sandbox objects.
All metadata is replicated from production. Data streams do not remain active automatically after refresh.

C. The Data 360 instance is deleted and a new, blank Data 360 instance must be provisioned after the refresh.
The Data 360 instance is not deleted. Metadata is replicated; only ingested data is cleared.

🔧 Reference:
→ Refresh and Synchronize Your Data 360 Sandbox
Explains sandbox refresh behavior for Data 360 metadata and ingested data.

Explanation:

This question tests what causes a higher identity resolution consolidation rate in Data 360. Consolidation rate rises when more source profiles are matched and merged into unified profiles. So the change that typically increases it is one that makes the ruleset match more profiles, not one that removes rules or reduces sources.

A. Modifying a ruleset that increases the number of matched profiles
✅ This is correct because adding or broadening match rules causes more source profiles to be linked into the same unified profile. That reduces the total number of unified individuals relative to source records, which increases the consolidation rate. Salesforce documents that to increase consolidation rate, you should add more match rules.

B. Removing existing identity resolution rules
❌ This usually lowers matching accuracy and reduces the number of profiles that merge together. With fewer matches, more unified individuals remain separate, so the consolidation rate tends to decrease instead of increase.

C. Reducing the number of data sources mapped to the Individual object
❌ This affects data coverage, not consolidation behavior. Fewer mapped sources may reduce the amount of data available for matching, but it does not typically raise the consolidation rate the way stronger or additional match rules do.

D. Deleting duplicate records from source data streams
❌ This removes duplicates before identity resolution can use them to consolidate profiles. Since consolidation rate measures how much source data was combined into unified profiles, deleting duplicates upstream does not cause the ruleset itself to consolidate more records.

🔧 Reference:
→ Salesforce Help — Identity Resolution Ruleset Processing Results
— confirms that adding more match rules increases consolidation rate.

Explanation:
In Data 360, formula fields are best suited for simple, row-level operations that process each record independently. They are designed for lightweight transformations like string manipulation, type conversions, date calculations, and basic arithmetic within a single row. When logic becomes complex or requires combining data across multiple rows or objects, batch or streaming transforms are the recommended approach instead.

Correct Option:

B. When performing simple, row-level arithmetic or string manipulation.
Formula fields in Data 360 support operations such as text manipulation, type conversions, date calculations, and logical expressions on individual records. They are ideal for simple, row-level transformations like concatenating fields to create a unique key or flagging records based on a single field's value. Since formulas process each row independently without requiring joins or aggregations, they offer an efficient way to clean and standardize data during ingestion.

Incorrect Option:

A. When processing multi-terabyte datasets in parallel.
Formula fields are not designed for large-scale parallel processing. Multi-terabyte datasets that require parallel computation are better handled through batch data transforms, which support complex operations like joins, aggregations, and appending data from multiple sources at scale.

C. When performing complex multi-row joins.
Formula fields operate on individual rows and cannot perform joins across multiple objects or rows. Complex multi-row joins require batch or streaming data transforms, which can combine data from multiple DLOs and execute SQL queries to link records based on keys.

D. When the logic needs to be reused across 10 different ingestion sources.
While formulas can be created within data streams, reusing the same logic across multiple ingestion sources is better managed through transforms. Data transforms provide a centralized way to apply consistent business logic and can output to multiple targets, making them more maintainable for reusable logic.

Reference:
Trailhead: Connect and Transform Data; Salesforce Help: Authoring Considerations for Insights.

Explanation:
The process of mapping different source schemas (user, contact, subscriber) into a standard data model is called harmonization. In Data 360, harmonization involves mapping Data Lake Objects (DLOs) to Data Model Objects (DMOs) within the Customer 360 Data Model, creating a unified representation of data from disparate sources . This step is essential before unification and segmentation can occur.

Correct Option:

C. Harmonize.
Harmonization is the specific Data 360 term for mapping and transforming ingested data into the standard Customer 360 Data Model. When multiple schemas refer to a person by different names (user, contact, subscriber), harmonization aligns these fields to standard DMO attributes like Individual, Contact Point Email, and Contact Point Phone . This creates a consistent semantic layer that downstream processes like identity resolution and segmentation rely upon.

Incorrect Option:

A. Transform.
Transformation refers to modifying data values during ingestion or mapping, such as creating formula fields to cleanse or standardize formats . While transformations may support harmonization, the term specifically describes the mapping of source schemas to the standard data model, not the broader mapping process itself.

B. Segment.
Segmentation is the process of creating audience filters and groups from harmonized and unified data. It occurs after harmonization and unification are complete, and it does not describe the schema mapping activity in the question .

D. Unify.
Unification (identity resolution) is the process of matching and reconciling records from different sources into unified profiles. It occurs after harmonization and uses the mapped data to link profiles, but the question specifically asks about mapping source schemas to a standard model .

Reference:
Salesforce Help: Data Federation, Ingestion, and Modeling; Data Model Objects (DMOs) Overview.