To ensure that freshly imported data is ready and available for use in any segment, the processes should be run in the following sequence: Refresh Data Stream > Identity Resolution > Calculated Insight . Here’s why:
Understanding the Requirement
Northern Trail Outfitters uploads new customer data daily to an Amazon S3 bucket, which is ingested into Data Cloud.
A calculated insight is created to show the total spend per customer in the last 30 days.
The goal is to ensure that the data is properly refreshed, resolved, and processed before being used in segments.
Why This Sequence?
Step 1: Refresh Data Stream
Before any processing can occur, the data stream must be refreshed to ingest the latest data from the Amazon S3 bucket.
This ensures that the most up-to-date customer data is available in Data Cloud.
Step 2: Identity Resolution
After refreshing the data stream, identity resolution must be performed to merge related records into unified profiles.
This step ensures that customer data is consolidated and ready for analysis.
Step 3: Calculated Insight
Once identity resolution is complete, the calculated insight can be generated to calculate the total spend per customer in the last 30 days.
This ensures that the insight is based on the latest and most accurate data.
Other Options Are Incorrect :
B. Refresh Data Stream > Calculated Insight > Identity Resolution : Calculated insights cannot be generated before identity resolution because they rely on unified profiles.
C. Calculated Insight > Refresh Data Stream > Identity Resolution : Calculated insights require both fresh data and resolved identities, so this sequence is invalid.
D. Identity Resolution > Refresh Data Stream > Calculated Insight : Identity resolution cannot occur without first refreshing the data stream to bring in the latest data.
Conclusion
The correct sequence is Refresh Data Stream > Identity Resolution > Calculated Insight , ensuring that the data is properly refreshed, resolved, and processed before being used in segments.
