DAA-C01 Question 36
Single answer1.3 Enrich data by identifying and accessing relevant data from the Snowflake Marketplace.A retail analytics team in Snowflake wants to improve its weekly sales forecast by adding demographic and weather context to store-level transaction data. The team does not want to build ingestion pipelines or manage refresh logic for third-party data. They also want the external datasets to stay current as the provider updates them. Which action should the data analyst take to meet these requirements with the least operational overhead?
- A
Browse Snowflake Marketplace for relevant demographic and weather listings, subscribe to the selected datasets, and join the shared data directly to internal sales data in Snowflake
- B
Export internal sales data to cloud object storage, ask the provider to deliver files there, and create external tables to query the combined data
- C
Use Snowpipe to continuously load the provider's data into internal tables because Marketplace data must be copied into the consumer account before it can be queried
- D
Request that the provider create a data exchange and then replicate the shared database into the retailer's account so the team can manage refresh timing independently
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use Snowflake Marketplace to identify relevant external datasets and subscribe to them directly. This aligns with the scenario's requirements: no custom ingestion pipelines, minimal operational overhead, and access to provider-maintained current data. In Snowflake, Marketplace listings are consumed through secure data sharing, so the consumer can query shared data and join it with internal tables without moving files or building refresh processes. This is a key best practice for enriching analytical datasets with third-party data inside Snowflake. Relevant Snowflake documentation covers Marketplace listings and consumer workflows, as well as secure data sharing concepts that explain how shared databases are accessed and updated by providers.
- A. Correct.
Correct. Snowflake Marketplace is designed for discovering and accessing third-party datasets without building custom ingestion pipelines. When a consumer subscribes to a listing, the provider shares data directly into the consumer account as a shared database. The consumer can query that data in place and join it with internal data, while updates made by the provider are reflected automatically according to the share. This is the lowest-overhead approach for enriching analytics with current external data.
- B. Incorrect.
Incorrect. Exporting data to object storage and asking providers to deliver files there creates unnecessary ingestion and maintenance work. It also shifts the solution away from Snowflake Marketplace's native data sharing model, which is specifically intended to avoid file movement and pipeline management for shared datasets.
- C. Incorrect.
Incorrect. This reflects a common misconception. Marketplace data does not need to be copied into the consumer's internal tables before it can be queried. Although a consumer could choose to copy shared data for specific use cases, that is not required to access or analyze Marketplace data, and doing so would add operational overhead that the scenario explicitly wants to avoid.
- D. Incorrect.
Incorrect. A data exchange is a different sharing construct used for curated collaboration among specific participants, not the standard action a consumer takes to access broadly available third-party datasets in Snowflake Marketplace. Also, the goal is to minimize operational work, and managing independent refresh timing through replication is not the typical or necessary approach for simply consuming provider-maintained Marketplace data.