A Data 360 Consultant is building a marketing- to- sales handoff process that requires sales...

The operational requirement is to move Data 360 context into the CRM process at the right latency and without unnecessary replication. Drag the native Data 360 Related List Enrichment onto the Lead Lightning page and configure the relevant Engagement data model objects (DMOs). meets the operational need because Data 360 can surface context or trigger action in Salesforce without forcing every engagement, score, or profile attribute to be copied into custom CRM objects. 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.