A Snowflake Architect is designing a multi-tenant application strategy for an organization in the Snowflake Data Cloud and is considering using an Account Per Tenant strategy. Which requirements will

Question

Options

• AThere needs to be fewer objects per tenant.
• BSecurity and Role-Based Access Control (RBAC) policies must be simple to configure.
• CCompute costs must be optimized.
• DTenant data shape may be unique per tenant.
• EStorage costs must be optimized.

• A
  6% (2)
• B
  75% (27)
• C
  6% (2)
• E
  14% (5)

Explanation

The Account Per Tenant strategy involves creating separate Snowflake accounts for each tenant within the multi-tenant application. This approach offers a number of advantages. Option B: With separate accounts, each tenant's environment is isolated, making security and RBAC policies simpler to configure and maintain. This is because each account can have its own set of roles and privileges without the risk of cross-tenant access or the complexity of maintaining a highly granular permission model within a shared environment. Option D: This approach also allows for each tenant to have a unique data shape, meaning that the database schema can be tailored to the specific needs of each tenant without affecting others. This can be essential when tenants have different data models, usage patterns, or application customizations.

No community discussion yet for this question.