Data marketplace and listings in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Data Marketplace Listing Visibility

You have published a dataset to the Snowflake Data Marketplace. Which factor determines if your listing is visible to other Snowflake accounts?

A The dataset must be shared with the PUBLIC role in your account.

B The dataset must be stored in an internal stage within your account.

C The listing must be approved and published by Snowflake after submission.

D The listing is automatically visible once the share is created.

💡 Hint

Think about the approval process for marketplace listings.

Listings on the Snowflake Data Marketplace require approval and publication by Snowflake before they become visible to other accounts. Simply creating a share or storing data internally does not make the listing public.

❓ Architecture

intermediate

Best Architecture for Secure Data Sharing via Marketplace

You want to share sensitive data via Snowflake Data Marketplace but ensure only authorized consumers can access it. Which architecture best supports this?

A Create a share and restrict access using reader accounts with specific grants.

B Publish the dataset as a listing and require consumers to request access via Snowflake's approval process.

C Create a share with the dataset and grant access to the PUBLIC role.

D Upload data to an external stage and share the stage URL publicly.

💡 Hint

Consider how to control access tightly while using marketplace shares.

Using reader accounts with specific grants allows you to control who can access the shared data securely. Granting access to PUBLIC or sharing external stage URLs publicly exposes data without control.

❓ Configuration

advanced

Configuring a Data Marketplace Listing with Custom Metadata

Which Snowflake SQL command correctly adds custom metadata tags to a data marketplace listing named my_listing in the MARKETPLACE_SCHEMA schema?

A ALTER LISTING MARKETPLACE_SCHEMA.my_listing SET TAGS = ('industry=finance', 'region=us');

B ALTER LISTING MARKETPLACE_SCHEMA.my_listing SET TAGS = ('industry:finance', 'region:us');

C ALTER LISTING MARKETPLACE_SCHEMA.my_listing SET TAG = ('industry=finance', 'region=us');

D ALTER LISTING MARKETPLACE_SCHEMA.my_listing SET TAGS = ('industry:finance', 'region=us');

💡 Hint

Check the syntax for setting tags in Snowflake listings.

The correct syntax uses SET TAGS with key:value pairs separated by colons inside single quotes. Using equal signs or SET TAG is invalid syntax.

❓ security

advanced

Identifying Security Risks in Marketplace Data Sharing

Which of the following scenarios poses the greatest security risk when sharing data via Snowflake Data Marketplace?

A Sharing data with reader accounts that have limited access and expiration policies.

B Requiring consumers to authenticate with their own Snowflake accounts.

C Using secure views to expose only specific columns in the shared dataset.

D Publishing a listing with sensitive data without masking or encryption.

💡 Hint

Consider what happens if sensitive data is exposed directly.

Publishing sensitive data without masking or encryption exposes it to all consumers, which is a major security risk. Using reader accounts, secure views, and authentication helps protect data.

✅ Best Practice

expert

Optimizing Data Marketplace Listings for Performance and Cost

You manage multiple large datasets listed on Snowflake Data Marketplace. To optimize performance and reduce costs for consumers, which approach is best?

A Create curated views with pre-filtered and aggregated data for listings.

B Use reader accounts with unlimited compute warehouses for consumers.

C Store datasets in external stages and share stage URLs directly.

D Publish full raw datasets and let consumers filter data after download.

💡 Hint

Think about reducing data volume and compute for consumers.

Curated views with pre-filtered and aggregated data reduce the amount of data scanned and transferred, improving performance and lowering costs. Sharing raw data or external stages can increase costs and complexity.

Practice

1. What is the primary purpose of a data marketplace in Snowflake?

easy

A. To group data listings for easy sharing and discovery

B. To store raw data files permanently

C. To run complex SQL queries faster

D. To manage user access permissions

Solution

1. Step 1: Understand the role of a data marketplace

   A data marketplace is designed to organize and share data listings so users can find and use data easily.

2. Step 2: Compare options with this purpose

   Options A, B, and D describe other Snowflake features but not the marketplace's main role.

3. Final Answer:

   To group data listings for easy sharing and discovery -> Option A

4. Quick Check:

   Marketplace = Group data listings [OK]

Hint: Marketplaces group data listings for sharing [OK]

Common Mistakes:

• Confusing marketplace with data storage
• Thinking marketplace speeds up queries
• Mixing marketplace with access control

2. Which SQL command correctly and safely creates a new data marketplace named my_marketplace in Snowflake?

easy

A. CREATE NEW MARKETPLACE my_marketplace;

B. CREATE DATA MARKETPLACE my_marketplace;

C. CREATE MARKETPLACE my_marketplace;

D. CREATE MARKETPLACE IF NOT EXISTS my_marketplace;

Solution

1. Step 1: Recall correct syntax for creating marketplace

   Snowflake uses CREATE MARKETPLACE [IF NOT EXISTS] name; to create marketplaces safely.

2. Step 2: Check each option

   CREATE MARKETPLACE my_marketplace; lacks IF NOT EXISTS and will fail if the marketplace already exists; Options B and D use invalid syntax; CREATE MARKETPLACE IF NOT EXISTS my_marketplace; is correct and safe.

3. Final Answer:

   CREATE MARKETPLACE IF NOT EXISTS my_marketplace; -> Option D

4. Quick Check:

   CREATE MARKETPLACE IF NOT EXISTS = safe creation [OK]

Hint: Use IF NOT EXISTS to avoid errors creating marketplace [OK]

Common Mistakes:

• Adding extra keywords like DATA or NEW
• Omitting IF NOT EXISTS causing errors if exists
• Using incorrect command structure

3. Given the SQL query:

SHOW LISTINGS IN MARKETPLACE my_marketplace;

What will this command do?

medium

A. Create a new listing inside my_marketplace

B. Delete all listings from my_marketplace

C. Display all data listings available in the marketplace named my_marketplace

D. Show all marketplaces in the account

Solution

1. Step 1: Understand the SHOW LISTINGS command

   This command lists all data listings inside a specified marketplace.

2. Step 2: Match command with options

   Display all data listings available in the marketplace named my_marketplace matches the command's purpose; Options A and C describe create/delete actions which SHOW does not do; Show all marketplaces in the account shows all marketplaces in the account, not listings.

3. Final Answer:

   Display all data listings available in the marketplace named my_marketplace -> Option C

4. Quick Check:

   SHOW LISTINGS = list data sets [OK]

Hint: SHOW LISTINGS lists data sets in a marketplace [OK]

Common Mistakes:

• Confusing SHOW with CREATE or DELETE
• Thinking it lists marketplaces instead of listings
• Assuming it modifies data

4. You run the command:

CREATE LISTING my_listing IN MARKETPLACE my_marketplace;

But get an error saying the marketplace does not exist. What is the most likely cause?

medium

A. The marketplace my_marketplace was not created before creating the listing

B. The listing name my_listing is invalid

C. You need to use DROP MARKETPLACE before CREATE LISTING

D. Listings cannot be created inside marketplaces

Solution

1. Step 1: Analyze the error message

   The error says the marketplace does not exist, so the system cannot find my_marketplace.

2. Step 2: Check command dependencies

   You must create the marketplace before adding listings inside it. If missing, this error occurs.

3. Final Answer:

   The marketplace my_marketplace was not created before creating the listing -> Option A

4. Quick Check:

   Create marketplace first, then listing [OK]

Hint: Create marketplace before listings to avoid errors [OK]

Common Mistakes:

• Assuming listing name causes error
• Trying to drop marketplace before listing
• Believing listings can't be inside marketplaces

5. You want to share a dataset with external users by creating a listing in a marketplace. Which sequence of commands correctly achieves this?

hard

A. CREATE LISTING my_listing; CREATE MARKETPLACE my_marketplace; GRANT USAGE ON MARKETPLACE my_marketplace TO ROLE external_role;

B. CREATE MARKETPLACE my_marketplace; CREATE LISTING my_listing IN MARKETPLACE my_marketplace; GRANT USAGE ON LISTING my_listing TO ROLE external_role;

C. CREATE MARKETPLACE my_marketplace; GRANT USAGE ON MARKETPLACE my_marketplace TO ROLE external_role; CREATE LISTING my_listing IN MARKETPLACE my_marketplace;

D. GRANT USAGE ON LISTING my_listing TO ROLE external_role; CREATE MARKETPLACE my_marketplace; CREATE LISTING my_listing IN MARKETPLACE my_marketplace;

Solution

1. Step 1: Create the marketplace first

   You must create the marketplace before adding listings inside it.

2. Step 2: Create the listing inside the marketplace

   After marketplace creation, create the listing specifying the marketplace.

3. Step 3: Grant usage on the listing to external users

   Granting usage on the listing allows external roles to access the shared data.

4. Final Answer:

   CREATE MARKETPLACE my_marketplace; CREATE LISTING my_listing IN MARKETPLACE my_marketplace; GRANT USAGE ON LISTING my_listing TO ROLE external_role; -> Option B

5. Quick Check:

   Create marketplace -> listing -> grant usage [OK]

Hint: Create marketplace, then listing, then grant access [OK]

Common Mistakes:

• Creating listing before marketplace
• Granting usage before creating listing
• Granting usage on marketplace instead of listing