Pearson Data-Cloud-Consultant New Attempt

The B2C Commerce Order Bundle is a data bundle that creates a data stream to flow order data from a B2C Commerce instance to Data Cloud. However, this data bundle does not ingest any historical data and only ingests new orders from the time the data stream is created. Therefore, if a consultant wants to ingest historical order data, they need to use a different method, such as exporting the data from B2C Commerce and importing it to Data Cloud using a CSV file12. References:

• Create a B2C Commerce Data Bundle
• Data Access and Export for B2C Commerce and Commerce Marketplace

 The Ingestion API is a RESTful API that allows you to stream data from any source into Data Cloud in a fast and scalable way. You can use the Ingestion API to send data from your inventory management system into Data Cloud as JSON objects, and then use Data Cloud to create data models, segments, and insights based on your inventory data. The Ingestion API supports both batch and streaming modes, and can handle up to 100,000 records per second. The Ingestion API also provides features such as data validation, encryption, compression, and retry mechanisms to ensure data quality and security. References: Ingestion API Developer Guide, Ingest Data into Data Cloud

 The error “Segment references too many data lake objects (DLOs)” occurs when a segment query exceeds the limit of 50 DLOs that can be referenced in a single query. This can happen when the segment has too many filters, nested segments, or exclusion criteria that involve different DLOs. To remedy this issue, the consultant can try the following troubleshooting tips:

• Split the segment into smaller segments. The consultant can divide the segment into multiple segments that have fewer filters, nested segments, or exclusion criteria. This can reduce the number of DLOs that are referenced in each segment query and avoid the error. The consultant can then use the smaller segments as nested segments in a larger segment, or activate them separately.
• Use calculated insights in order to reduce the complexity of the segmentation query. The consultant can create calculated insights that are derived from existing data using formulas. Calculated insights can simplify the segmentation query by replacing multiple filters or nested segments with a single attribute. For example, instead of using multiple filters to segment individuals based on their purchase history, the consultant can create a calculated insight that calculates the lifetime value of each individual and use that as a filter.

The other options are not troubleshooting tips that can help remedy this issue. Refining segmentation criteria to limit up to five custom data model objects (DMOs) is not a valid option, as the limit of 50 DLOs applies to both standard and custom DMOs. Spacing out the segment schedules to reduce DLO load is not a valid option, as the error is not related to the DLO load, but to the segment query complexity.

References:

• Troubleshoot Segment Errors
• Create a Calculated Insight
• Create a Segment in Data Cloud

 Streaming insights are computed from real-time engagement events and can be used to trigger data actions based on pre-set rules. Data actions are workflows that send data from Data Cloud to other systems, such as Journey Builder. To ensure that the data action is triggered every hour, the consultant should set the insights aggregation time window to 1 hour. This means that the streaming insight will evaluate the events that occurred within the last hour and execute the data action if the conditions are met. The other options are not relevant for streaming insights and data actions. References: Streaming Insights and Data Actions Limits and Behaviors, Streaming Insights, Streaming Insights and Data Actions Use Cases, Use Insights in Data Cloud, 6 Ways the Latest Marketing Cloud Release Can Boost Your Campaigns