certified-data-cloud-consultant Sample Questions & Answers

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.

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.

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.

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.

Reconciliation Rules are used to determine which field values 'win' when multiple source profiles are unified. By setting a Source Priority reconciliation rule on the MobilePhone field and placing the CRM data source at a higher priority than the trade show data source, the system will always select the CRM's phone number for the unified profile.

Data Spaces are the primary feature for managing data segregation within a single Data Cloud instance. They allow an organization to create logical partitions of data, where data streams, identity resolution rulesets, segments, and activations are all contained within a specific Data Space. Users are then granted access to one or more Data Spaces, ensuring they can only work with the data relevant to their business unit.

Calculated Insights are not computed in real-time. They are processed on a schedule (e.g., hourly, daily). If the insight is not scheduled to run, or if the schedule is not set to daily, the DATE_DIFF calculation will only be performed when the insight is manually run or when its schedule executes. To ensure the 'Days Since Last Purchase' value is current, the Calculated Insight must be scheduled to run daily.

Profile category is for DMOs that store information about individuals or entities, such as customers or contacts. This is a core category for data that will be used in identity resolution.

Engagement category is for DMOs that store data about interactions or events, such as email opens, website clicks, or purchases.

Other category is a general-purpose category for DMOs that do not fit into the Profile or Engagement categories, often used for product catalogs, store locations, or other reference data.

True. For DMOs in the Engagement category, which represent time-based events like clicks, purchases, or opens, designating an 'Event Time' field is mandatory. This field is crucial for time-series analysis, time-windowed segmentation, and creating calculated insights based on event chronology.