ADA-C01 Question 446
Single answerUse Cross-cloud auto fulfillment for listingsA data provider publishes a paid listing from a Snowflake account hosted on AWS us-east-1. Several prospective consumers use Snowflake accounts on Azure and Google Cloud in other regions, and the provider wants those consumers to be able to request the data without the provider manually creating separate shares or replication setups for each target platform. The provider also wants fulfillment to occur only when a consumer actually requests the listing. Which configuration best meets these requirements?
- A
Enable Cross-Cloud Auto-Fulfillment for the listing so Snowflake can automatically create and manage the required replication and fulfillment when eligible consumers request the listing.
- B
Convert the listing to a direct share and ask each consumer to create a reader account in the provider's AWS region, because Cross-Cloud Auto-Fulfillment only works within the same cloud.
- C
Create a database replication group manually for every supported consumer region and cloud before publishing the listing, because listings cannot trigger fulfillment automatically.
- D
Use Secure Data Sharing without a listing and rely on external stages to move the data to each cloud when consumers subscribe.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to enable Cross-Cloud Auto-Fulfillment for the listing. This capability is intended for providers who publish listings and want Snowflake to handle fulfillment to supported target regions and clouds when consumers request access. It reduces administrative effort compared with manually creating separate replication or distribution mechanisms for each cloud/region combination. In practice, administrators should also verify prerequisites, supported regions/clouds, and any cost implications associated with replication and fulfillment. This aligns with Snowflake's documentation and best practices for sharing data products through listings at scale, especially when the provider wants on-demand cross-cloud fulfillment rather than manually managed per-consumer setups.
- A. Correct.
Correct. Cross-Cloud Auto-Fulfillment is designed for listings so providers can make data products available across supported clouds and regions without manually building separate fulfillment paths for each potential consumer. The key benefit in this scenario is that fulfillment is driven by consumer requests for the listing, reducing administrative overhead and avoiding pre-provisioning every target location.
- B. Incorrect.
Incorrect. This reflects a common misconception that cross-cloud distribution requires reader accounts or same-cloud sharing only. Reader accounts are for consumers without their own Snowflake account and do not solve the provider's stated need to support many existing Snowflake consumers across multiple clouds through a listing. Cross-Cloud Auto-Fulfillment specifically addresses cross-cloud and cross-region listing fulfillment where supported.
- C. Incorrect.
Incorrect. Manual replication may be used in some architectures, but it does not best meet the requirement of avoiding manual setup for each target platform and region. The scenario explicitly asks for fulfillment only when a consumer requests the listing. Cross-Cloud Auto-Fulfillment is intended to automate the underlying fulfillment workflow for eligible listings rather than requiring the provider to pre-create replication for every destination.
- D. Incorrect.
Incorrect. Secure Data Sharing alone does not provide the marketplace/listing-based cross-cloud fulfillment workflow described here. Using external stages to move data between clouds is also not how listing fulfillment is implemented and would add unnecessary complexity, governance risk, and operational burden compared with the native listing capability.