The design point is to preserve source fidelity while shaping data only where Data 360 processing needs it.
Here, Refresh Data Stream > Identity Resolution > Calculated Insight fits because it changes the shape, keying, or refresh behavior at the Data 360 layer instead of forcing the source system to carry an analytics- specific design. In production, this keeps the upstream application simpler and gives the data team a repeatable way to prepare records for mapping, identity resolution, insights, or segmentation. The distractors fall short because they either move the problem into the wrong system, add needless duplication, ignore Data
360 object relationships, or rely on a feature built for a different lifecycle stage. In a real implementation, those choices usually create brittle pipelines, stale data, security exposure, or segments that look correct on paper but fail when activated. Thinking like an architect, the selected option places the logic where Data 360 can govern it and reuse it reliably.