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 be addressed with this approach? (Choose two.)
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 be addressed with this approach? (Choose two.)
Using an Account Per Tenant (APT) strategy helps to ensure that security and Role-Based Access Control (RBAC) policies can be simplified and efficiently managed, as each tenant has its own separate account with distinct access controls. Additionally, this strategy is particularly beneficial when the tenant data shape may be unique per tenant, as each account can be tailored to the specific data requirements and structures of each tenant without interference or complexity arising from shared resources.
I would choose B and D... https://developers.snowflake.com/wp-content/uploads/2021/05/Design-Patterns-for-Building-Multi-Tenant-Applications-on-Snowflake.pdf
I agree here.
changing to B&D
I think we can exclude C & E cause they are not requirements well solved by using APT, I'm not sure about A, but it seems unnecessary to use APT with few objects. Potential is A cause RBAC is not required to isolate tenant ( Refer Part Three: Evaluating Tenancy Models in https://developers.snowflake.com/wp-content/uploads/2021/05/Design-Patterns-for-Building-Multi-Tenant-Applications-on-Snowflake.pdf). And the left is D, I think it's reasonable to use APT
C & D. Compute costs are to be considered when using multiple accounts, D for data shape being different
Answer is C,E and is validated
I think its A&D