Salesforce Certified Data Cloud Consultant Free Sample Questions

Batch Data Transforms are designed for complex, large-scale transformations on data at rest after it has landed in the DLO. Using a Library function allows for reusable, complex logic like PII masking to be defined once and applied across multiple transforms, which is efficient and maintainable. Calculated Insights operate on DMOs, not DLOs during ingestion. Streaming Data Transformations act on data in-flight but are more suited for real-time event data, not large batch loads from a data warehouse. Formula fields on the DMO are applied after ingestion and do not mask the raw data in the DLO.

Streaming Insights are designed to process and aggregate data from real-time event streams (like website clicks) over a rolling time window, which is perfect for the 'viewed more than three times in 24 hours' criteria. This allows the segment to be updated in near real-time.

After the Streaming Insight identifies the high-intent behavior, a standard segment is used to combine this insight with other criteria, such as filtering out customers who have made a purchase in the last 7 days. The segment builder brings together both real-time and historical data for precise targeting.

The correct data model is to have the Individual DMO (representing the unified customer profile) as the 'one' side and the UnifiedSubscription_c DMO as the 'many' side. This allows a single unified individual to have multiple subscription events over time (e.g., a past subscription and a current one), which accurately reflects the business reality. The relationship is established by mapping a field in UnifiedSubscription_c (like User_Id__c) to the Individual DMO.

When activating a related attribute from a one-to-many relationship (one individual can have many trips), Data Cloud must be told how to select a single record if multiple exist. If this isn't configured, it may arbitrarily select one. If that selected record has a null value for the destination, the activated attribute will be blank. The consultant should edit the activation to add criteria for selecting the related attribute, such as 'Choose the record with the earliest upcoming trip date' and 'where Destination is not null'.

Reconciliation rules determine which source system's value to use for a specific field when multiple source profiles are merged into a Unified Individual. In this case, the rule explicitly states to prioritize the SIS source for the 'Status' field. Even though the match occurred between the alumni portal and SIS, the reconciliation rule for the 'Status' field dictates that the value from the SIS will be the winner and populated on the unified profile.

False. Segment criteria can be edited after creation and activation. When you edit and republish a segment, Data Cloud re-evaluates its membership based on the new criteria during its next scheduled or manual refresh. This allows for dynamic and iterative refinement of audiences without needing to create new segments and reconfigure activations.

Streaming Data Transformations are specifically designed to perform transformations on data ingested in near real-time via the Ingestion API before it's written to a Data Lake Object. They are ideal for use cases like classifying or cleansing event data in-flight. A Batch Data Transform runs on a schedule against data already at rest. A Calculated Insight operates on DMOs, not during ingestion. A formula field on the DMO also processes data after it has already landed.

Data must be modeled in DMOs before it can be used in Calculated Insights or Segmentation. Both Case and Order data need their own DMOs, and they must be related back to the Individual DMO to link them to a unified customer profile.

Calculated Insights are used to perform aggregations like summing up order values to compute the CLV. This insight is created on the Individual DMO, allowing the CLV to be an attribute of the unified profile.

Once the data is modeled and the CLV is calculated, the segment can be built. It targets the Individual DMO and uses direct attributes (from the Calculated Insight) and related attributes (from the linked Case DMO) to define the audience.

For time-based segmentation operators like 'Is In Last' to function correctly, the date field being used (VisitDate) must be designated as the 'Event Time' field in the DMO's properties. If this is not set, Data Cloud does not know which field represents the timestamp of the event, and time-windowed filters will not work as expected, often resulting in a count of zero.

Data Actions are designed to trigger processes in target systems based on real-time events or streaming insight rules. By creating a Data Action that listens for the 'Loyalty Sign-up' event and targets a Marketing Cloud Journey Entry Event, the welcome message can be sent in near real-time. Standard segment activations are batch-based and would not meet the immediacy requirement.