DAA-C01 Question 35
Single answer1.3 Enrich data by identifying and accessing relevant data from the Snowflake Marketplace.A retail analytics team wants to improve a daily sales dashboard by adding local weather context for each store location. The team needs a fast way to evaluate and use third-party weather data without building or maintaining ingestion pipelines. They also want the provider to continue updating the data automatically after access is granted. Which action should the Snowflake data analyst take?
- A
Search the Snowflake Marketplace for a weather data listing, review the listing details and usage terms, and request or get the data so it is made available in the team’s Snowflake account as a shared dataset.
- B
Create an external stage that points to the weather provider’s cloud storage, then use Snowpipe to continuously ingest files into internal Snowflake tables.
- C
Ask the provider to export weather data as CSV files and upload them manually into a table each day because Marketplace listings are only for one-time static snapshots.
- D
Use a data share created by the retail company and publish it to the provider so the provider can push weather records directly into the company’s existing sales tables.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use Snowflake Marketplace to identify and access a relevant weather data listing. This approach fits all scenario requirements: rapid evaluation, no custom ingestion pipeline, and provider-managed updates after access is granted. In Snowflake, Marketplace data products are typically delivered through secure sharing, allowing consumers to query shared data without copying or moving it into their own managed pipelines. When evaluating listings, analysts should review details such as provider credibility, available regions, refresh cadence, schema, sample data, and legal or usage restrictions before obtaining access. This aligns with Snowflake best practices for enriching internal analytics with third-party data from the Marketplace.
- A. Correct.
Correct. Snowflake Marketplace is designed for discovering and accessing third-party data products directly within Snowflake. A consumer can search Marketplace listings, inspect metadata such as provider information, refresh frequency, regions, sample data, and terms of use, then obtain the listing. The data is then available in the consumer account through secure sharing mechanisms, so the provider maintains the data and updates are reflected without the consumer building ingestion pipelines.
- B. Incorrect.
Incorrect. This is a valid ingestion pattern for raw files in cloud storage, but it does not match the stated requirement to avoid building and maintaining ingestion pipelines. It also assumes the provider is exposing data as files rather than offering a Snowflake Marketplace listing. Marketplace access is intended to simplify consumption of provider-managed datasets.
- C. Incorrect.
Incorrect. This option reflects a common misconception that external data must be copied into Snowflake as files. Marketplace listings are not limited to static snapshots; providers can publish continually updated data products. Manually loading CSV files adds operational overhead and does not meet the requirement for automatic provider-managed updates.
- D. Incorrect.
Incorrect. A consumer does not use its own outbound data share to receive third-party Marketplace data, and providers do not push records directly into the consumer’s existing tables through this mechanism. Marketplace consumption is based on obtaining a provider’s listing, which exposes shared database objects for read access in the consumer account rather than writing into the consumer’s tables.