ARA-R01 practice question 9 of 10
A large manufacturing company runs a dozen individual Snowflake accounts across its business divisions. The company wants to increase the level of…
Full set: 162 questionsDomain Architecting a Solution
A Private Data Exchange is the recommended Snowflake feature for creating a centralized data hub for multiple internal business units (consumers and providers). It simplifies data discovery and access management, minimizing administrative effort. However, a Data Exchange is specific to a single Snowflake region. To include data from the European divisions, which are in different regions, the best practice is to use database replication. The European accounts can replicate their shared databases to the region where the Private Data Exchange is hosted. This allows their data to be listed and accessed through the same central exchange, creating a unified and scalable sharing architecture for the entire company.
A. Migrating entire accounts is a complex and costly process that may also conflict with data residency regulations (e.g., GDPR) for European divisions.
B. This creates a hybrid model with two separate sharing mechanisms (an exchange and direct shares), which increases management complexity, contradicting the requirement to minimize effort.
C. The Snowflake Marketplace is designed for monetizing and distributing data to external Snowflake customers, not for private, internal data sharing between a company's own divisions.
1. Introduction to the Snowflake Data Exchange: "A data exchange enables you to share data securely and in near real-time with a select group of members that you invite... You can create a data exchange to share data privately between your business units..." This supports the use of a Private Data Exchange for the core requirement.
Source: Snowflake Documentation, docs.snowflake.com/en/user-guide/data-exchange-intro.
2. Working with a Data Exchange: "A data exchange is specific to a Snowflake region. All members of a data exchange must have a Snowflake account in the same region." This highlights the regional limitation that necessitates replication.
Source: Snowflake Documentation, docs.snowflake.com/en/user-guide/data-exchange-working-with.
3. Introduction to Database Replication and Failover: "Replicate databases and keep them synchronized across multiple Snowflake accounts in different regions... This enables sharing data from a single source with consumers in different regions." This directly supports using replication to make data available for cross-region sharing, which can then be integrated into a regional Data Exchange.
Source: Snowflake Documentation, docs.snowflake.com/en/user-guide/database-replication-intro.
Keep practicing
Take the free ARA-R01 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other ARA-R01 practice questions
- Question 1A Developer is having a performance issue with a Snowflake query. The query receives up t…
- Question 2Two queries are run on the customer_address table: create or replace TABLE CUSTOMER_ADDRE…
- Question 4An Architect needs to allow a user to create a database from an inbound share. To meet th…
- Question 5Which security, governance, and data protection features require, at a MINIMUM, the Busin…
- Question 6What does a Snowflake Architect need to consider when implementing a Snowflake Connector …
- Question 7A user named USER_01 needs access to create a materialized view on a schema EDW. STG_SCHEM
