ADA-C01 Question 445
Single answerUse Cross-cloud auto fulfillment for listingsA data provider publishes a Snowflake listing from an AWS us-east-1 account. Several consumers want to access the listing from accounts in Azure East US and Google Cloud us-central1, but the provider does not want to manually create and maintain separate database replicas for each target cloud/region. The provider also wants consumers to receive the data through the listing experience rather than through direct account-to-account shares. Which action should the administrator take to meet these requirements with the least operational overhead?
- A
Enable Cross-Cloud Auto-Fulfillment for the listing so Snowflake manages fulfillment of the listing to supported target regions/clouds.
- B
Convert the listing into a direct share and grant imported privileges to consumer accounts in each cloud.
- C
Create a database replication group for each target cloud/region and ask consumers to query the replicated databases directly.
- D
Use Secure Data Sharing with reader accounts in the provider's AWS region so consumers on Azure and Google Cloud can access the data cross-cloud without fulfillment.
- E
Package the data as an application package and publish it as a Snowflake Native App instead of a listing.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to enable Cross-Cloud Auto-Fulfillment for the listing. In Snowflake Marketplace/data sharing scenarios, listings are the distribution mechanism intended for discoverability and consumer self-service. Cross-Cloud Auto-Fulfillment is specifically used when a provider wants to offer a listing to consumers in other supported cloud platforms or regions without manually standing up and maintaining separate copies for each target location. Snowflake handles the fulfillment workflow behind the listing, reducing administrative burden. By contrast, direct shares are not listings, reader accounts are for consumers without their own Snowflake accounts, and Native Apps solve a different problem. This aligns with Snowflake guidance for using listings with auto-fulfillment to support cross-region and cross-cloud data access while minimizing provider management effort.
- A. Correct.
Correct. Cross-Cloud Auto-Fulfillment is designed for listings and reduces provider overhead by allowing Snowflake to automatically fulfill the listing to supported regions/clouds when consumers request it. This fits the requirement to keep the listing-based consumer experience and avoid manually creating and maintaining separate replicas.
- B. Incorrect.
Incorrect. Direct shares are not the same as listings and do not satisfy the requirement to distribute the data through the listing experience. Also, cross-cloud access is not solved simply by converting a listing to a direct share; providers typically need listing-based fulfillment for cross-cloud distribution scenarios.
- C. Incorrect.
Incorrect. Replication can be part of data distribution strategies, but this option does not meet the requirement for minimal operational overhead because the provider would manually manage replication targets. It also does not preserve the intended consumer workflow of obtaining the data through a listing that Snowflake fulfills automatically.
- D. Incorrect.
Incorrect. Reader accounts are created in the provider's Snowflake account and are not the right solution for consumers who already have their own Snowflake accounts in other clouds and regions. This also does not provide the listing-based cross-cloud fulfillment behavior described in the scenario.
- E. Incorrect.
Incorrect. A Snowflake Native App is for packaging and distributing application logic and related objects, not simply the best mechanism to expose a dataset via a listing with minimal cross-cloud operational effort. This introduces a different distribution model and does not directly address the stated requirement.