ARA-C01 Question 157
Single answerCross-Cloud Auto-FulfillmentA data provider shares a Snowflake listing from an AWS us-east-1 account. Several consumers want to obtain the data in their own regions and clouds without manually creating and refreshing separate copies. The provider also wants the sharing workflow to remain centralized in the listing so new consumers can receive data with minimal operational effort. Which approach best meets these requirements?
- A
Enable Cross-Cloud Auto-Fulfillment for the listing so Snowflake can automatically create and maintain database replicas in supported target regions/clouds as consumers request the listing.
- B
Create reader accounts for all consumers in the provider's AWS us-east-1 account, because reader accounts are the only supported way to share data across clouds.
- C
Replicate the shared database manually to each target region and cloud using custom ETL pipelines, then publish a separate listing for each replica.
- D
Use Secure Data Sharing directly from the provider account to all consumer accounts, because shares automatically traverse regions and cloud platforms without replication.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to enable Cross-Cloud Auto-Fulfillment on the listing. This capability is intended for providers distributing listings to consumers in other regions or cloud platforms while minimizing manual replication management. Instead of building custom copies or maintaining separate shares per environment, the provider publishes the listing once and Snowflake fulfills consumer access through supported replication mechanisms. This aligns with Snowflake best practices for Marketplace/private listing distribution across clouds: use listings with auto-fulfillment rather than reader accounts or custom ETL duplication. A key architectural distinction is that direct Secure Data Sharing is simplest within the same region, while cross-region/cross-cloud distribution for listings relies on replication/fulfillment support. Candidates should recognize that auto-fulfillment reduces operational burden, centralizes governance, and is the purpose-built feature for this scenario.
- A. Correct.
Correct. Cross-Cloud Auto-Fulfillment is designed for listings so providers can offer data to consumers across supported regions and cloud platforms without manually building separate replication workflows per target. Snowflake handles the required replication/fulfillment behind the scenes when eligible consumers access the listing, which reduces provider operational overhead and keeps distribution centralized through the listing.
- B. Incorrect.
Incorrect. Reader accounts allow providers to share data with organizations that do not have their own Snowflake account, but they are not the mechanism for cross-cloud sharing at scale for existing Snowflake consumers. They also place the consumer workload in the provider's account context and do not satisfy the requirement for consumers to access data in their own cloud/region environments.
- C. Incorrect.
Incorrect. Manual ETL-based copying and publishing separate listings would increase operational complexity and contradict the requirement for minimal ongoing effort and centralized listing management. It also introduces unnecessary pipelines when Snowflake's native cross-cloud auto-fulfillment capability is intended for this use case.
- D. Incorrect.
Incorrect. Native Secure Data Sharing does not automatically work across regions and cloud platforms from a single source without the necessary replication support. Cross-region and cross-cloud fulfillment requires Snowflake replication-based mechanisms rather than a basic direct share that transparently spans all locations.