What considerations need to be taken when using database cloning as a tool for data lifecycle management in a development environment? (Select TWO).

Question

Options

• AAny pipes in the source are not cloned.
• BAny pipes in the source referring to internal stages are not cloned.
• CAny pipes in the source referring to external stages are not cloned.
• DThe clone inherits all granted privileges of all child objects in the source object, including the
• EThe clone inherits all granted privileges of all child objects in the source object, excluding the

• A
  89% (41)
• B
  4% (2)
• D
  4% (2)
• E
  2% (1)

Explanation

When cloning a database in Snowflake, pipes are a key consideration. Answer A is correct: pipes defined in the source database are not cloned as part of the database clone operation - they must be recreated manually in the cloned environment. Answer C is correct: specifically, pipes that reference external stages are not cloned because external stages point to external cloud storage locations (S3, Azure Blob, GCS) that exist outside the Snowflake object hierarchy and cannot be implicitly included. Answer B is incorrect - pipes referencing internal stages follow different behavior. Answers D and E (truncated) relate to privilege inheritance, but the privilege behavior for cloned child objects is that the clone does NOT inherit the source's granted privileges on child objects; the cloning account/role owns the clone.

No community discussion yet for this question.