DEA-C02 Data Movement Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Unload the data to an S3 bucket in US-WEST-2 and use Snowpipe to load it into EU-CENTRAL-1.

  Why it's wrong here

  While this works, it involves multiple manual steps and cross-region cloud storage costs. It is less automated and harder to maintain than native replication. Furthermore, managing the security and latency of moving data between S3 buckets in different regions adds unnecessary complexity to the data movement pipeline.

• ✓

  Use the Snowflake Database Replication feature to sync the database containing the table to the target region.

  Why this is correct

  Database Replication is the native Snowflake solution for moving data between regions and accounts. It is highly automated, supports incremental updates, and ensures data consistency. It also provides the foundation for disaster recovery, making it the most robust choice for cross-region data movement requirements.

• ✗

  Create an External Function that calls a Python script to copy data via the Snowflake Connector.

  Why it's wrong here

  Using External Functions for bulk data movement is highly inefficient and creates a significant bottleneck. External functions are designed for row-level processing or small-scale API calls. Moving entire tables across regions through a custom Python script would be slow, expensive, and prone to network failures.

• ✗

  Set up a Secure Data Share between the two regions and use a CREATE TABLE AS SELECT statement.

  Why it's wrong here

  As of current standard functionality, Secure Data Sharing is generally restricted to the same region unless using the Data Cloud's 'Private Sharing' or 'Global Listings'. Even then, sharing does not 'move' the data into a new table; it provides a view of the source data, which differs from synchronization.