What happens when a cloned table is replicated to a secondary database? (Select TWO)

Question

Options

• AA read-only copy of the cloned tables is stored.
• BThe replication will not be successful.
• CThe physical data is replicated: The actual data of the cloned table is physically replicated to
• DAdditional costs for storage are charged to a secondary account
• EMetadata pointers to cloned tables are replicated: Along with the physical data, the metadata

• A
  4% (2)
• B
  6% (3)
• C
  74% (40)
• D
  17% (9)

Explanation

When a cloned table is replicated to a secondary Snowflake database, two things happen. First, the physical data of the cloned table is replicated (C)-Snowflake's replication feature copies the actual micro-partitions of data to the secondary account's storage, ensuring the secondary database is a fully functional replica with its own physical data copy. Second, the metadata pointers associated with the cloned table are also replicated (E)-this metadata includes partition maps, table statistics, and structural references that define how the data is organized and accessed. A read-only copy (A) is not accurate because replicated databases can be promoted to read-write. Replication failure (B) is incorrect-cloned tables replicate successfully. Additional storage costs to a secondary account (D) would depend on configuration, but the core mechanism involves metadata and physical data replication as described in C and E.

No community discussion yet for this question.