Zero-copy cloning in Snowflake creates a metadata-only snapshot of databases, schemas, or tables, enabling rapid environment refreshes without duplicating data. However, not all dependent objects behave identically during cloning.
Pipes that reference external stages are not cloned because external stages depend on credentials and integrations that may not exist or be valid in the cloned environment (Answer C). This is a documented Snowflake behavior and an important consideration when cloning production environments into development.
Regarding privileges, a cloned database inherits privileges granted on child objects (such as schemas and tables), but it does not inherit privileges granted directly on the source database itself (Answer E). This design prevents unintended access escalation and ensures that security must be explicitly re-granted at the database level.
Understanding these nuances is essential for SnowPro Architect candidates when designing environment promotion strategies and managing data lifecycle processes using cloning.
=========