An Architect needs to design a Snowflake account and database strategy to store and analyze large amounts of structured and semi-structured data. There are many business units and departments within…

Question

Options

• ACreate a single Snowflake account and database for all data storage and analysis needs,
• BSet up separate Snowflake accounts and databases for each department or business unit, to
• CUse Snowflake's data lake functionality to store and analyze all data in a central location, without
• DUse a centralized Snowflake database for core business data, and use separate databases for

• A
  2% (1)
• B
  10% (6)
• C
  6% (4)
• D
  82% (51)

Explanation

The best practice for balancing scalability, security, and cost efficiency in Snowflake is Option D: use a centralized Snowflake database for core/shared business data, and create separate databases for each department or business unit's domain-specific data. This model enables: (1) centralized governance and cost control within a single account, (2) data isolation and role-based access control per department database, and (3) cross-database queries where needed. Option A (single database for everything) creates governance and access control challenges at scale. Option B (separate accounts per department) is expensive, makes cross-department data sharing complex, and is operationally heavy. Option C (unstructured data lake with no organization) sacrifices the security and governance requirements.

No community discussion yet for this question.