A company operates a Snowflake environment in AWS us-west-2 (Oregon). It must privately share data with a customer whose Snowflake environment runs in Azure East US 2 (Virginia).
What recommended sequence of operations must be followed to satisfy this requirement?
A
Create a share and add the database privileges to the share2. Create a new listing on the Snowflake Marketplace3. Alter the listing and add the share4. Instruct the customer to subscribe to the listing on the Snowflake Marketplace
B
Ask the customer to create a new Snowflake account in Azure EAST US 2 (Virginia)2. Create a share and add the database privileges to the share3. Alter the share and add the customer's Snowflake account to the share
C
Create a new Snowflake account in Azure East US 2 (Virginia)2. Set up replication between AWS us-west-2 (Oregon) and Azure East US 2 (Virginia) for the database objects to be shared3. Create a share and add the database privileges to the share4. Alter the share and add the customer's Snowflake account to the share
D
Create a reader account in Azure East US 2 (Virginia)2. Create a share and add the database privileges to the share3. Add the reader account to the share4. Share the reader account's URL and credentials with the customer
Show Answer Answer Explanation Direct account-to-account Secure Data Sharing works only between accounts in the same region and cloud platform. The provider is in AWS us-west-2 and the consumer is in Azure East US 2, so a direct share (B) or a reader account created in the target region (D) will not work. The recommended pattern is to create a Snowflake account in the consumer's region/cloud (Azure East US 2), replicate the database objects to be shared into that account, then create the share and add the customer's account to it. Marketplace listings (A) are a collaboration/discovery mechanism, not the recommended private cross-cloud share sequence. Therefore C.
Learn more
Community Discussion