MENU
A Data 360 Consultant is configuring a zero- copy architecture where an external Snowflake instance needs to access Data 360 data without the latency of traditional extract, transform, load (ETL) processes. Which capability should the consultant use to expose Data 360 objects to the external Snowflake environment?
The architecture principle is to avoid unnecessary data movement when the external platform can be queried or shared securely. Data 360 Data Shares 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. This is the nuance exam questions often test: the platform capability must match both the technical layer and the business timing requirement, not just sound related to data.