SnowPro Associate: Platform Question 355
Single answer● Snowflake MarketplaceA data engineering team wants to enrich internal sales analytics with a third-party demographic dataset from Snowflake Marketplace. The team needs to start using the provider's data quickly, avoid building ETL pipelines to copy and reload the dataset, and ensure the provider can publish updates that become available to consumers. Which approach should the Snowflake administrator recommend?
- A
Install the listing from Snowflake Marketplace so the team gets a database created from the provider's shared data, then query it directly alongside internal tables
- B
Export the Marketplace data to cloud storage, load it into an internal Snowflake table, and schedule recurring COPY INTO jobs to keep it current
- C
Request the provider send database files and recreate the dataset manually in the consumer account to preserve update control
- D
Use Snowpipe Streaming to subscribe to the provider's Marketplace listing so updates are pushed into the consumer's custom schema
Show answer and explanation
Correct answer: A
Explanation
The best answer is to install the Snowflake Marketplace listing and query the shared data directly. Snowflake Marketplace is built on Snowflake's secure data sharing capabilities, which let providers publish data products and let consumers access them without copying the underlying data into their own storage as part of the sharing mechanism. This is a key practical advantage: faster onboarding, reduced pipeline maintenance, and access to provider-published updates. For SnowPro Associate candidates, it is important to distinguish Marketplace and secure sharing from ingestion features such as Snowpipe or Snowpipe Streaming. Documentation and Snowflake best practices emphasize that Marketplace consumers typically install a listing, which creates a read-only database based on the provider's share, and then join that data with their own internal Snowflake data for analytics.
- A. Correct.
Correct. Snowflake Marketplace listings are consumed through Snowflake data sharing. When a consumer installs a listing, Snowflake creates a database in the consumer account from the provider's shared data. This allows the team to query the shared data directly without building ETL pipelines or copying the data into local tables. It also supports the requirement that provider updates become available to consumers through the share.
- B. Incorrect.
Incorrect. This approach adds unnecessary data movement and operational overhead. One of the main benefits of Snowflake Marketplace is direct access to shared data without exporting, copying, and reloading it. While a team could choose to copy data for a separate use case, it does not best satisfy the requirement to avoid ETL pipelines and use provider updates efficiently.
- C. Incorrect.
Incorrect. Snowflake Marketplace does not work by sending database files for manual recreation in the consumer account. Marketplace listings are accessed through secure sharing mechanisms managed by Snowflake. Recreating the dataset manually would defeat the benefits of centralized publishing and ongoing provider-managed updates.
- D. Incorrect.
Incorrect. Snowpipe Streaming is used for ingesting streaming data into Snowflake, not for consuming Snowflake Marketplace listings. Marketplace data is not subscribed to through Snowpipe Streaming or pushed into a custom schema in this way. This option reflects a common confusion between ingestion services and data sharing capabilities.