What considerations need to be taken when using database cloning as a tool for data lifecycle management in a development environment? (Choose two.)
What considerations need to be taken when using database cloning as a tool for data lifecycle management in a development environment? (Choose two.)
When using database cloning as a tool for data lifecycle management in a development environment, it's important to consider that any pipes in the source referring to internal stages are not cloned. Additionally, the clone inherits all granted privileges of all child objects in the source object, excluding the database itself.
Correct answer is B & E, only pipes referencing external stages are cloned, and the clone inherits all grants to child objects but not the database itself
Answer should be B & E. https://docs.snowflake.com/en/user-guide/object-clone When a database or schema is cloned, any pipes in the source container that reference an internal (i.e. Snowflake) stage are not cloned. However, any pipes that reference an external stage are cloned. If the source object is a database or schema, the clone inherits all granted privileges on the clones of all child objects contained in the source object: Note that the clone of the container itself (database or schema) does not inherit the privileges granted on the source container.