Northern Trail Outfitters (NTO) is ingesting transaction data into Data 360.

The modeling decision should make the data understandable, reusable, and correctly related before segmentation or activation depends on it. Map standard fields to the Sales Order DMO and add a custom attribute for the fee. fits because Data 360 depends on mappings and relationships between data lake objects and data model objects. Correct modeling lets the same attribute mean the same thing across source systems and prevents downstream users from building logic on ambiguous fields. 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.