Contact Point Phone expects one row per phone number with a type indicator (Mobile, Home, Work). Using streaming transforms, the Contact data stream can be exploded into a separate Phone DLO that produces three rows—one for each field—and adds the phone type attribute. This normalized DLO is then mapped to the Contact Point Phone data model object, making every phone number separately addressable for identity resolution and activation with a single ingestion.

A. Mapping three different fields in one row violates the one-row-per-number model and drops type metadata.

C. Calculated insights create metrics, not normalized records for identity and activation mapping.

D. Formula fields stay columnar inside the same row; they still fail the normalization requirement.

1. Salesforce Help, “Normalize Phone Data with Streaming Transforms,” Data Cloud Data Ingestion, section “Explode Columns,” para 2-4.

2. Salesforce Data Cloud Developer Guide, “Contact Point Phone Object Definition,” Table 1, Note on ‘one record per phone’.

3. Salesforce Architects, “Designing for Multi-valued Attributes in Data Cloud,” Tech Brief, p. 5-6.

A data delay in activations points to a scheduling or dependency issue in the data processing pipeline. The correct operational sequence is: Data Ingestion -> Calculated Insights -> Segment Refresh -> Activation. If the segment is refreshed before new data is ingested, it will be stale (C). Similarly, if a segment that relies on a calculated insight (CI) is refreshed before the CI has finished running with the latest data, the segment's membership will be outdated (B). Both scenarios would result in the activation publishing old data.

A. Data transformations must run before calculated insights, as CIs may depend on the transformed data. Running them after would cause data integrity issues.

D. Calculated insights must run before segments are refreshed because the segment criteria may depend on the output of the insight. This option describes the incorrect order.

1. Salesforce Help. (2024). Schedule and Automate Data Processes. "Ensure that your dependent processes are scheduled to run after the processes they depend on are complete. For example, schedule a segment to refresh after its underlying calculated insight is updated." Section: Data Process Dependencies.

2. Salesforce Help. (2024). Data Cloud Processing Order. "Data Cloud processes data in a specific order... 1. Ingestion and Unification... 2. Calculated Insights... 3. Segmentation... 4. Activation." Section: Understanding Data Refresh.

In Data Cloud segmentation, the 'Is Equal To' operator performs a case-insensitive exact match on the specified string value. It does not normalize or ignore diacritics (accent marks). Therefore, a filter for 'San José' will match any entry where the characters are exactly 'S', 'a', 'n', ' ', 'J', 'o', 's', 'é', regardless of their case. This means it will find 'San José' and 'san josé', but it will not match 'San Jose' because the 'é' is treated as a distinct character from 'e'.

A. This describes the behavior of a 'Contains' operator, not 'Is Equal To'. The match must be exact, not partial.

B. This is incorrect because the filter is case-insensitive, but it incorrectly ignores the required accent mark on the 'é'.

C. This is incorrect because it is case-sensitive (wrongly suggesting only 'San Jose' would match) and also ignores the required accent mark.

1. Salesforce Help. (2024). Segmentation Filter Operators. Section: "Text Operators". The documentation specifies that the "Is Equal To" operator is case-insensitive for text values.

2. Salesforce Developer Documentation. (2024). Segmentation API. The behavior of filter expressions in the underlying API confirms that string equality is case-insensitive but character-specific, meaning diacritics are not normalized against their base characters.

Streaming insights are designed for near real-time data processing in Data Cloud. They perform aggregations and calculations on data as it is ingested from sources like the Mobile SDK and Interaction SDK. This allows for low-latency segmentation and activation based on user behavior within defined time windows, such as the 15-minute window specified in the question. Batch transforms and calculated insights operate on schedules (hourly or daily) and are not suitable for this real-time requirement.

A. Batch transform: This processes data in scheduled batches, which does not meet the near real-time, 15-minute window aggregation requirement.

B. Calculated insight: This runs complex SQL queries on a schedule (typically hourly or daily) over the entire dataset, not on incoming data streams.

D. Formula fields: This is a feature within standard Salesforce objects for row-level calculations, not a Data Cloud feature for streaming data aggregation.

1. Salesforce Help, Data Cloud, "Streaming Insights and Data Actions". This document specifies, "Use streaming insights to create data model object records that are based on events that are occurring in a stream... For example, you can calculate a customer’s propensity to churn based on their last five minutes of website activity."

2. Salesforce Help, Data Cloud, "Calculated Insights". The documentation clarifies, "Calculated insights run on a schedule that you define (hourly or daily)..." This contrasts with the streaming nature of the question's requirement.

Data Cloud enforces data types upon ingestion. The target field is defined with a Date datatype, which stores calendar dates without a time component (format yyyy-mm-dd). The source data contains values in both Date (yyyy-mm-dd) and DateTime (yyyy-mm-dd hh:mm:ss) formats. When a DateTime value is mapped to a Date field, Data Cloud automatically truncates the time portion and stores only the date. The ingestion will succeed for all rows, standardizing the values to the target field's Date format. No errors will be thrown for this specific conversion.

A. The ingestion process does not throw an error for this type of conversion; it truncates the time part and successfully stores the date.

B. The target field is strictly a Date datatype and cannot store the time component; the value will be conformed to the target type.

C. The time part is ignored, and the date part is stored, not the other way around. This option describes the opposite behavior.

1. Salesforce Help. (2024). Data Cloud Data Types. "Date: A calendar date. If a DateTime value is mapped to a Date field, the time part of the value is truncated." Table: Data Type Mappings.

2. Salesforce Developer Documentation. (2024). Prepare and Map Your Data. "During data mapping, ensure that the source field's data type is compatible with the target DLO field's data type. Data Cloud attempts to convert data where possible, such as removing the time component from a datetime value when mapping to a date field." Section: Data Type Considerations.

The logical data flow in Data Cloud requires data to be present and structured before it can be used for advanced functions. First, data must be ingested from a source. Second, this raw data must be mapped to the Customer 360 Data Model to give it meaning. Only then can Calculated Insights be created to derive new KPIs, like Customer Lifetime Value, from the mapped data. Finally, this new KPI becomes an attribute available for building segmentation rules.

B. This is incorrect because a Calculated Insight cannot be created before the data it needs to calculate upon has been ingested and mapped to the data model.

C. This is incorrect for the same reason as B; a Calculated Insight requires ingested and mapped data as its input.

D. This is incorrect because Calculated Insights operate on Data Model Objects (DMOs), not directly on raw ingested data. Data must be mapped to the model first.

1. Salesforce Help, Calculated Insights. "Calculated Insights are built on data that is already in Data Cloud and mapped to the data model." (This confirms data must be ingested and mapped first).

2. Salesforce Help, Data Cloud Implementation Guide, Section: "Data Ingestion and Modeling". This guide outlines the sequence as connecting data sources, creating data streams (ingestion), and mapping to the data model as foundational steps before other actions.

3. Salesforce Help, Segmentation. "Use your Data Cloud data to create segments... You can use attributes from your data model objects and calculated insights." (This confirms CIs are used in segmentation).

Data Cloud provides a native SFTP Connector that securely pulls CSV or JSON files placed on an external SFTP server and loads them into a data stream, exactly matching the customer’s export method.

B. Cloud Storage Connector is for S3, Azure Blob, and Google Cloud Storage, not SFTP.

C. Data Import Wizard operates on core Salesforce objects, not Data Cloud datasets.

D. Data Loader uploads to CRM objects only and cannot write directly to Data Cloud.

• Salesforce Help, “Set Up the SFTP Connector,” Overview – “Use this connector to ingest files exported to an SFTP site.”

• Salesforce Help, “Cloud Storage Connectors,” Introduction – lists supported providers (S3, Azure, GCS) only.

• Salesforce Help, “Import Data with the Data Import Wizard,” Scope section.

• Salesforce Help, “Use Data Loader,” Overview – limited to standard and custom objects.

The Salesforce CRM Connector's integration user requires explicit Field-Level Security (FLS) permissions to access any new fields created on an object in the source CRM org. If the integration user does not have at least "Read" access to the new "Business Priority" custom field, Data Cloud cannot see or ingest it. The data stream's schema must then be manually refreshed after the permissions are granted.

B. The Salesforce Data Loader: This is a data import/export tool and is not used for managing the metadata schema of a data stream.

C. Custom fields on the Case object are not supported: This is incorrect. The Salesforce CRM Connector fully supports custom fields on standard objects like Case.

D. After 24 hours when the data stream refreshes: A data stream refresh ingests new or updated data, not metadata changes like new fields. Schema changes require permission updates and a manual refresh.

- Salesforce Help, Salesforce CRM Connector. In the "Set Up the Salesforce CRM Connector" section, it emphasizes the need for the integration user to have read access to all objects and fields intended for data ingestion.

- Salesforce Help, Edit a Salesforce CRM Data Stream. This page explains that after adding a new field in the source org and granting permissions, you must edit the data stream in Data Cloud to add the new field.

When a data stream is created, its associated Data Lake Objects (DLOs) and the resulting Data Model Objects (DMOs) are available only in the default data space. To use these objects in another data space, they must be explicitly added to that space's configuration. The correct procedure is to navigate to the specific data space's settings and select the required DLOs and DMOs to make them available for mapping and other operations within that segregated environment. This ensures proper data governance and isolation between brands.

A. Creating a new data stream for the same data source is inefficient and doesn't solve the object visibility issue in the new data space.

B. Copying data is a data manipulation task, not the correct method for making an object's schema available in a different data space.

C. A batch transform is used for data processing and enrichment, not for managing object availability across data spaces.

1. Salesforce Help, Data Cloud, "Manage Data in a Data Space". This document details the procedure: "From the Data Spaces tab, select a data space...Click Edit...To add an object, select it from the list of available objects and click the right arrow."

2. Salesforce Help, Data Cloud, "Considerations for Data Spaces". This guide notes, "When you create a data stream, its DLO is only available in the default data space. To make it available in another data space, add it to the data space."

Salesforce Flow is the ideal tool for this requirement. Data Cloud publishes platform events for key system processes, including the DataStreamStatusChangedEvent, which fires when a data stream's status changes (e.g., to 'Failed'). A consultant can create a platform event-triggered Flow that subscribes to this event. The Flow can then execute a series of automated actions: send custom notifications via Slack and email, create a Case record for the support team, and update records used by a monitoring dashboard. This provides a robust, immediate, and automated response.

A. Data actions are triggered by customer data or insights (e.g., a website click), not by system monitoring events like a data stream failure.

B. The Data Cloud Query Editor is a tool for manually running queries against DMOs. It is not an automation or monitoring tool.

D. Reports and dashboards are for visualizing data. While they can be scheduled, they cannot trigger immediate, multi-step automations like creating cases and sending Slack alerts.

1. Salesforce Help. (2024). Monitor Data Cloud with Flow. "You can use platform events with flows to send notifications or create processes when a data stream or activation fails."

2. Salesforce Developer Documentation. (2024). Platform Events in Data Cloud. Object Reference for DataStreamStatusChangedEvent. "Represents a change in the status of a data stream... You can create a platform event-triggered flow that subscribes to this event."