A Snowflake Architect is designing an application and tenancy strategy for an organization where strong legal isolation rules as well as multi-tenancy are requirements. Which approach will meet these

Question

Options

• ACreate accounts for each tenant in the Snowflake organization.
• BCreate an object for each tenant strategy if row level security is viable for isolating tenants.
• CCreate an object for each tenant strategy if row level security is not viable for isolating tenants.
• DCreate a multi-tenant table strategy if row level security is not viable for isolating tenants.

• A
  73% (22)
• B
  7% (2)
• C
  3% (1)
• D
  17% (5)

Explanation

Strong legal isolation requirements-such as regulatory compliance, data sovereignty, or contractual separation obligations-demand complete physical and logical separation between tenants, which only separate Snowflake accounts provide. Separate accounts have fully isolated compute, storage, metadata, and security boundaries. Even when RBAC can control access effectively within a shared account, it provides only logical isolation; legal obligations typically require account-level separation. Options B and C (object-per-tenant strategies) and Option D (multi-tenant tables) all share underlying account infrastructure, which does not satisfy strong legal isolation rules regardless of whether RBAC or row-level security is used.

No community discussion yet for this question.