The architecture principle is to avoid unnecessary data movement when the external platform can be queried or shared securely. It defines metadata and paths to identify specific files for the data stream and track updates. aligns with the zero-copy model because Data 360 can expose or query governed data without building another extract pipeline. That is important when teams want freshness, reduced duplication, and lower operational burden while still respecting permissions and platform boundaries. 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.