ADA-C01 Question 442
Single answerConfigure cross-region and cross-cloud data sharingA global data provider maintains a Snowflake account in AWS us-east-1 and needs to share a curated dataset with two consumers: one in AWS eu-west-1 and another in Azure East US 2. The provider wants the consumers to query the data with the least operational overhead while ensuring the shared data stays synchronized as source tables change. Which approach should the Snowflake administrator recommend?
- A
Create a standard direct share from the provider account to both consumer accounts, because secure shares automatically work across all regions and clouds.
- B
Use database replication to copy the source database into each target region or cloud, then create local shares from the replicated databases to the consumers in those regions or clouds.
- C
Export the data to external stages in each target cloud, then have consumers create external tables over those files for near real-time access.
- D
Create a reader account in AWS us-east-1 for each consumer, because reader accounts are the recommended method for cross-region and cross-cloud sharing.
Show answer and explanation
Correct answer: B
Explanation
Snowflake-native direct sharing works most simply within the same region. When consumers are located in different regions or on different cloud platforms, the recommended administrative pattern is to use database replication (and associated refresh processes) to place a copy of the shareable database in the target region or cloud, then create a local share there for the consumer. This preserves the managed Snowflake sharing model and reduces the need for custom export pipelines. In practice, administrators should also validate edition/features, replication configuration, failover/replication group design where applicable, and any business requirements around refresh frequency and cost. This aligns with Snowflake documentation on secure data sharing and cross-region/cross-cloud data sharing using replication.
- A. Incorrect.
Incorrect. Standard secure data sharing is designed for accounts within the same region. It does not directly provide cross-region or cross-cloud sharing by simply adding consumer accounts in other regions or cloud platforms. A common misconception is that shares are globally routable across all Snowflake regions and clouds without replication.
- B. Correct.
Correct. For cross-region and cross-cloud scenarios, Snowflake supports database replication so that a database can be replicated to an account in the target region or cloud. The provider can then create a share from the local replicated database for consumers in that region or cloud. This approach keeps the shared data synchronized through refresh/replication operations and is the standard Snowflake pattern for minimizing custom operational work compared with file exports or ETL duplication.
- C. Incorrect.
Incorrect. Exporting to cloud storage and using external tables adds operational complexity, introduces file-management overhead, and does not provide the native governed sharing experience Snowflake is designed for. While it can be used for data distribution, it is not the recommended approach when the goal is Snowflake-native cross-region or cross-cloud sharing with synchronized data.
- D. Incorrect.
Incorrect. Reader accounts are used when the recipient does not already have a Snowflake account. They are not the preferred solution for existing consumer accounts in other regions or clouds, and they do not eliminate the regional/cloud constraints of where the data is hosted. This option reflects a common misunderstanding that reader accounts are a universal sharing mechanism.