DEA-C02 · Question #70
A company called IOT Corporation has subsidiary companies in Germany and Japan. - The German subsidiary has a Snowflake account called IOTGER in AWS region EU (Frankfurt) (Region ID: eu-central-1)…
The correct answer is D. Create an additional Snowflake account IOTGER2 into region Japan East. Replicate database. Option D is correct because the two Snowflake accounts belong to different organizations, which prevents direct sharing or cross-account replication between them. The solution is to create a bridge account (IOTGER2) within the German organization but in the same cloud region as…
Question
A company called IOT Corporation has subsidiary companies in Germany and Japan.
- The German subsidiary has a Snowflake account called IOTGER in AWS
region EU (Frankfurt) (Region ID: eu-central-1).
- The Japanese subsidiary has a Snowflake account called IOTJPN in
Azure region Japan East (Tokyo) (Region ID: japaneast). The subsidiaries are totally independent of one another, and their Snowflake accounts belong to different Snowflake organizations. A Data Engineer needs to share data in a database called IOT_PROD from the German account to the Japanese account. What steps need to be taken by the German subsidiary so that the Japanese subsidiary can use the shared data?
Options
- ACreate share S1 into IOTGER. Add the objects to be shared from IOT_PROD in IOTGER to the
- BReplicate database IOT_PROD from IOTGER to IOTJPN with the same database name. Create
- CCreate a clone of the database IOT_PROD into IOTJPN. Create secure views into the cloned
- DCreate an additional Snowflake account IOTGER2 into region Japan East. Replicate database
How the community answered
(26 responses)- A4% (1)
- B12% (3)
- C4% (1)
- D81% (21)
Explanation
Option D is correct because the two Snowflake accounts belong to different organizations, which prevents direct sharing or cross-account replication between them. The solution is to create a bridge account (IOTGER2) within the German organization but in the same cloud region as IOTJPN (Azure Japan East). German engineers then replicate IOT_PROD from IOTGER to IOTGER2, and create a share from IOTGER2 to IOTJPN - sharing works across organizations when the provider and consumer accounts are co-located in the same region.
Why the distractors fail:
- A - A direct share from IOTGER cannot reach IOTJPN because they are in different regions, different clouds, and different organizations; Snowflake sharing requires a same-region provider account.
- B - Snowflake database replication is an intra-organization feature; you cannot replicate directly from one organization's account into another organization's account.
- C - Cloning is strictly an intra-account operation in Snowflake; there is no mechanism to clone a database across accounts, let alone across organizations.
Memory tip: Think of it as a postal relay - you can't ship directly from Frankfurt (AWS) to Tokyo (Azure) across organizational borders, so you open a local warehouse (IOTGER2) in Tokyo first, ship the goods there, then hand them off to the neighbor (IOTJPN) down the street.
Topics
Community Discussion
No community discussion yet for this question.