A Snowflake Architect is creating a multi-account design strategy.
In which scenarios will this strategy be MOST cost-effective?
A separate Snowflake account is warranted when a boundary cannot be expressed within a single account. Differing PCI DSS compliance scopes (B) justify isolating regulated data in its own account, potentially with a different edition/features, so it is cost-effective to separate them. A Snowflake account integrates with a single Active Directory / IdP instance, so requiring different AD instances for dev/test/prod (D) forces multiple accounts. In contrast, distinct RBAC configurations (C) and per-user network policies (E) are easily handled with roles and network policies inside one account, and cloning across clouds (A) is not possible via CLONE at all (it needs replication). Therefore B and D.
Community Discussion