What happens when a cloned table is replicated to a secondary database? (Choose two.)
What happens when a cloned table is replicated to a secondary database? (Choose two.)
When a cloned table is replicated to a secondary database, a read-only copy of the cloned tables is stored in the secondary database. Additionally, what is replicated are the metadata pointers to the cloned tables, not the physical data. This allows the cloned tables to be accessed in the secondary database without duplicating the physical storage of the data.
When a cloned table is replicated to a secondary database, the physical data is also replicated, increasing the data storage usage for your account. https://docs.snowflake.com/en/user-guide/database-replication-considerations.html#:~:text=Replication%20and%20Cloning,-Cloned%20objects%20are&text=However%2C%20when%20a%20cloned%20table,storage%20usage%20for%20your%20account.
Answers C&D are correct. For C read this: Cloned objects are replicated physically rather than logically to secondary databases. That is, cloned tables in a standard database do not contribute to the overall data storage unless or until DML operations on the clone add to or modify existing data. However, when a cloned table is replicated to a secondary database, the physical data is also replicated, increasing the data storage usage for your account. https://docs.snowflake.com/en/user-guide/account-replication-considerations#replication-and-cloni For D , read this : Charges based on replication are divided into two categories: data transfer and compute resources. Both categories are billed on the target account (i.e. the account that stores the secondary database or secondary replication/failover group that is refreshed). https://docs.snowflake.com/en/user-guide/account-replication-cost
Answer is correct
Option A, "A read-only copy of the cloned tables is stored," is not entirely correct because the data is replicated, not just stored. Option B, "The replication will not be successful," is not correct because the replication will be successful if it is configured correctly. Option D, "Additional costs for storage are charged to a secondary account," is not correct because the cost of storage is charged to the primary account, not the secondary account.
Options are not Clear . Going through the link - https://docs.snowflake.com/en/user-guide/account-replication-considerations#replication-and-cloning C is certainly correct , D if we remove secondary from the option
Replication and Cloning Cloned objects are replicated physically rather than logically to secondary databases. That is, cloned tables in a standard database do not contribute to the overall data storage unless or until DML operations on the clone add to or modify existing data. However, when a cloned table is replicated to a secondary database, the physical data is also replicated, increasing the data storage usage for your account. https://docs.snowflake.com/en/user-guide/account-replication-considerations#replication-and-cloni
Answers C&D are correct. For C read this: Cloned objects are replicated physically rather than logically to secondary databases. That is, cloned tables in a standard database do not contribute to the overall data storage unless or until DML operations on the clone add to or modify existing data. However, when a cloned table is replicated to a secondary database, the physical data is also replicated, increasing the data storage usage for your account. https://docs.snowflake.com/en/user-guide/account-replication-considerations#replication-and-cloni For D , read this : Charges based on replication are divided into two categories: data transfer and compute resources. Both categories are billed on the target account (i.e. the account that stores the secondary database or secondary replication/failover group that is refreshed). https://docs.snowflake.com/en/user-guide/account-replication-cost
Correct
CD are correct
A and E are correct