Study guide
1.1 Multi-Account Strategy & Snowflake Organizations
SnowPro Advanced: Architect ARA-C01
Track your progress as you read
Finished sections get a check mark.
1 Introduction: The ARA-C01 Exam
About the SnowPro Advanced: Architect (ARA-C01) Exam
2 Chapter 1: Account Strategy & Organization Architecture
1.1 Multi-Account Strategy & Snowflake Organizations 1.2 Snowflake Parameter Hierarchy & Configuration 1.3 Database and Schema Design Architecture
3 Chapter 2: Identity, Access Control & Storage Integrations
2.1 Role-Based Access Control Architecture & Hierarchy 2.2 Secondary Roles, Object Ownership & Delegated Administration 2.3 Cloud Storage Integrations & IAM Trust Policies 2.4 Identity Federation, SSO, SCIM & Authentication Policies
4 Chapter 3: Governance, Data Privacy, Network Security & Compliance
3.1 Column-Level Masking & Row Access Policies 3.2 Object Tagging, Tag-Based Masking & Audit Governance 3.3 Encryption, Key Management & Tri-Secret Secure 3.4 Aggregation Policies, Projection Policies & External Tokenization 3.5 Network Policies, Network Rules, External Access & Private Connectivity 3.6 Snowflake Editions & Compliance Architecture (PCI DSS, PII & PHI)
5 Chapter 4: Data Modeling in Snowflake
4.1 Dimensional Modeling: Star vs. Snowflake Schemas 4.2 Data Vault 2.0 Architecture in Snowflake 4.3 Relational Constraints & Query Optimizer Integration
6 Chapter 5: Data Sharing & Collaboration Solutions
5.1 Direct Data Sharing Architecture & Security 5.2 Managed Reader Accounts for External Consumers 5.3 Snowflake Marketplace, Data Exchange & Clean Rooms
7 Chapter 6: Multi-Cloud, Multi-Region & Business Continuity
6.1 Database & Account Replication Mechanics 6.2 Disaster Recovery Architecture & Client Redirect 6.3 Cross-Cloud Auto-Fulfillment & Listing Replication 6.4 Data Protection: Time Travel, Fail-safe & Storage Costs
8 Chapter 7: Environments, Lakehouse, DevOps & AI/ML Applications
7.1 Multi-Tier Environment Strategy & Zero-Copy Cloning 7.2 Data Lakehouse Architecture & Apache Iceberg 7.3 DataOps, CI/CD & Snowflake Git Integration 7.4 AI/ML Pipelines & Applications: Cortex AI, ML Functions, Snowpark Container Services, Streamlit & Native Apps
9 Chapter 8: Data Ingestion Architecture
8.1 Bulk Ingestion Architecture: COPY INTO Optimization 8.2 Snowpipe Continuous Automated Ingestion 8.3 Snowpipe Streaming & Real-Time Ingestion 8.4 Data Unloading Architecture & Cloud Export Patterns 8.5 Schema Detection, Schema Evolution & Source-Change Architecture
10 Chapter 9: Continuous Pipelines & Stream Transformation
9.1 Change Data Capture (CDC) with Snowflake Streams 9.2 Task Orchestration, DAGs & Serverless Scheduling 9.3 Declarative Data Pipelines with Dynamic Tables 9.4 Views, Materialized Views & Transformation Table Design
11 Chapter 10: Semi-Structured Data & Ecosystem Tooling
10.1 Semi-Structured Data: VARIANT, OBJECT & ARRAY Processing 10.2 Snowflake Ecosystem Connectors, Drivers & SQL API 10.3 Snowpark, User-Defined Functions & Stored Procedures
12 Chapter 11: Virtual Warehouse Architecture & Concurrency
11.1 Virtual Warehouse Architecture, Sizing & Credit Economics 11.2 Multi-Cluster Warehouses & Concurrency Scaling Policies 11.3 Warehouse Types & Query Acceleration Service
13 Chapter 12: Query Profiling & Performance Diagnostics
12.1 Query Profile Deep-Dive & Bottleneck Analysis 12.2 Memory Spilling, Warehouse Queuing & Timeout Governance 12.3 Three-Tier Caching Architecture & Result Reuse
14 Chapter 13: Storage Optimization, Cost Governance & Observability
13.1 Micro-Partitioning & Automatic Clustering 13.2 Search Optimization Service (SOS) & Point Lookup Acceleration 13.3 Resource Monitors, Financial Governance & Usage Observability 13.4 Warehouse Monitoring, Alerts, Event Tables & Performance Explorer
1.1 Multi-Account Strategy & Snowflake Organizations
Key Takeaways Explain This Topic AI
Snowflake organizations link an enterprise's accounts for consolidated billing, organization-wide usage views, account provisioning, and replication; multi-account organizations now administer this from a single organization account using the GLOBALORGADMIN role.
New accounts are provisioned via CREATE ACCOUNT specifying cloud provider, region, and edition; account URLs follow the standardized https://<orgname>-<accountname>.snowflakecomputing.com syntax.
Resource monitors are strictly account-scoped objects; they cannot be defined at the organization level or inherited across accounts in an organization.
SNOWFLAKE.ORGANIZATION_USAGE latency varies by view: STORAGE_DAILY_HISTORY is about 2 hours, ACCOUNTS and RATE_SHEET_DAILY about 24 hours, and USAGE_IN_CURRENCY_DAILY about 72 hours, versus 45 minutes to 3 hours for most ACCOUNT_USAGE views.
Organization users and organization user groups, created in the organization account and imported by each regular account, let one person or service exist in many accounts without re-creating the user object everywhere (Enterprise Edition).
Last updated: September 2026
1.1 Multi-Account Strategy & Snowflake Organizations
Designing an enterprise Snowflake architecture requires selecting between a consolidated single-account topology and a multi-account organization topology. For the SnowPro Advanced: Architect exam, you must evaluate the governance, security, billing, and operational trade-offs of both paradigms, and understand how to manage multi-account fleets using Snowflake Organizations , the organization account , and the GLOBALORGADMIN and ORGADMIN roles.
Enterprise Account Topology: Single-Account vs. Multi-Account
Historically, organizations deployed all workloads within a single Snowflake account, relying on Role-Based Access Control (RBAC) and database namespaces to separate environments. As enterprise data architectures mature, multi-account topologies have become the recommended standard for enterprise deployments.
Architectural Evaluation Dimensions
Environment Isolation (Dev, Test, Prod)
Single-Account: Environments are partitioned via naming conventions and databases (e.g., DEV_DB , TEST_DB , PROD_DB ). However, all environments share the same account-level metadata layer, account parameters, and user directory. A runaway query or catalog lock can impact production workloads.
Multi-Account: Provides complete physical and logical isolation. Development experiments, schema migrations, and destructive testing cannot corrupt production metadata or exhaust account-level cloud services resources.
Blast Radius Reduction
Single-Account: A compromised ACCOUNTADMIN credential or an errant administrative command (such as modifying an account-level network policy) affects every workload, user, and pipeline in the enterprise.
Multi-Account: Compartmentalizes the blast radius. If credentials in a Sandbox or Development account are compromised, production data and pipelines remain isolated behind separate authentication and network perimeters.
Compliance, Regulatory, and Data Residency Separation
Single-Account: All data must adhere to the highest common denominator of regulatory compliance. If an organization handles both general analytics and PCI-DSS, HIPAA, or FedRAMP regulated data, the entire single account falls under the stringent audit scope.
Multi-Account: Highly regulated workloads can reside in dedicated accounts with Snowflake Business Critical Edition (enabling Tri-Secret Secure customer-managed keys and private connectivity), while standard analytical workloads operate in an Enterprise Edition account to optimize licensing costs. Furthermore, accounts can be deployed to specific geographic regions (e.g., AWS Frankfurt vs. AWS Northern Virginia) to satisfy GDPR and national data sovereignty mandates.
Billing and Cost Allocation Boundaries
Single-Account: Cost allocation across business units requires complex tagging, resource monitor attribution, and retrospective queries against ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY .
Multi-Account: Each account receives distinct itemized billing metrics. Separate business units, subsidiaries, or cost centers can own individual accounts, establishing hard billing boundaries with zero cross-charge ambiguity.
Regional Presence and Cloud Diversity
Single-Account: Bound to a single cloud provider and region (e.g., AWS us-east-1 ).
Multi-Account: Enables multi-cloud and multi-region presence. An enterprise can run primary ingestion on AWS, analytics serving on Azure, and machine learning pipelines on GCP, seamlessly linked through organization-level data sharing and replication.
Topology Comparison Matrix
- Architectural Dimension Single-Account Topology Multi-Account Organization Topology
- Isolation Mechanism Logical (RBAC, Schemas, Databases) Physical & Logical (Separate Accounts)
- Blast Radius Account-wide (All environments impacted) Isolated to specific account boundary
Compliance Boundary Unified (Highest compliance bar applied to all) Modular (Per-account edition and certification)
- Edition Flexibility Single edition (e.g., Enterprise only) Mixed (Standard, Enterprise, Business Critical)
- Cost Attribution Tagging & warehouse chargeback queries Hard billing demarcation per account
- Administrative Overhead Centralized, lower operational overhead Requires organizational governance model
- Data Sharing Intra-account database grants Direct secure data sharing across accounts
Snowflake Organizations & The ORGADMIN Role
A Snowflake Organization is a first-class management entity that links multiple Snowflake accounts owned by a single enterprise customer. The Organization framework enables consolidated billing, centralized account provisioning, cross-region replication, and cross-account telemetry.
Organization Administrators: GLOBALORGADMIN and ORGADMIN
Snowflake currently offers two ways to perform organization-level tasks, and the difference matters when you design a multi-account estate:
Approach Where it runs Architectural guidance
GLOBALORGADMIN in the organization account The single organization account — a special account used for organization-wide tasks Snowflake's recommended approach for multi-account organizations. Only one organization account exists per organization (Enterprise Edition).
ORGADMIN in an ORGADMIN-enabled regular account A normal account where the role has been enabled Being phased out for multi-account organizations; Snowflake says it will give at least three months' notice before retiring it.
Key facts about the legacy ORGADMIN path:
The first account in an organization has ORGADMIN enabled; an organization administrator can enable it in other accounts with ALTER ACCOUNT <account_name> SET IS_ORG_ADMIN = TRUE; (account-name format only, not the locator).
By default the role can be enabled in at most eight accounts, and it can never be enabled in a reader account . -- Recommended: organization-level work from the organization account
USE ROLE GLOBALORGADMIN;
- - Legacy path: enable ORGADMIN in another regular account
- USE ROLE ORGADMIN;
- ALTER ACCOUNT analytics_prod SET IS_ORG_ADMIN = TRUE;
The organization account is also where Snowflake exposes premium views in ORGANIZATION_USAGE (for example, organization-wide QUERY_HISTORY and TAG_REFERENCES ) and where you create organization users .
Declarative Account Provisioning
An organization administrator can programmatically provision new Snowflake accounts using SQL (or Snowsight) instead of raising support tickets or using cloud provider consoles. USE ROLE ORGADMIN;
- - Create a new production account in Azure Western Europe on Business Critical edition
- CREATE ACCOUNT prod_emea_bi
- ADMIN_NAME = org_sec_admin
- ADMIN_PASSWORD = 'TemporaryInitialStrongPassword2026!'
- EMAIL = 'data-governance@enterprise.com'
- EDITION = BUSINESS_CRITICAL
- REGION = azure_westeurope
- COMMENT = 'Primary EMEA Business Intelligence account with HIPAA/GDPR compliance';
- - List all accounts currently registered within the organization
- SHOW ACCOUNTS;
- Cloud Provider and Region Specification Syntax
When executing CREATE ACCOUNT , the REGION parameter uses a standardized cloud-and-region format:
- Cloud Provider Region Identifier Example Syntax in CREATE ACCOUNT
- Amazon Web Services (AWS) US East (N. Virginia) aws_us_east_1
- Amazon Web Services (AWS) Europe (Frankfurt) aws_eu_central_1
- Microsoft Azure East US 2 (Virginia) azure_eastus2
- Microsoft Azure West Europe (Netherlands) azure_westeurope
- Google Cloud Platform (GCP) US Central 1 (Iowa) gcp_us_central1
- Google Cloud Platform (GCP) Europe West 4 (Netherlands) gcp_europe_west4
- Organization Users: One Identity Across Many Accounts
Users are normally account-scoped objects, so a person who needs access to five accounts traditionally needs five user objects. Organization users (Enterprise Edition) remove that duplication:
In the organization account, a global organization administrator creates an organization user ( TYPE = PERSON or TYPE = SERVICE ) and adds it to an organization user group .
The group is made available to selected regular accounts.
Each regular account's administrator imports the organization user group , which adds its organization users to that account; existing same-name users can be linked after import. USE ROLE GLOBALORGADMIN;
- CREATE ORGANIZATION USER etl_pipeline
- EMAIL = 'data-platform@example.com'
- TYPE = SERVICE;
Architect Tip: Organization users simplify provisioning, but authorization is still decided inside each account by its own roles and grants. Combine organization users (or SCIM from your identity provider) with a consistent role model in every account.
Account Identifiers: Account Locator vs. Organization URL
Understanding how Snowflake identifies and routes connections to accounts is critical for architecting client connection strings, driver configurations, and disaster recovery failover.
1. Legacy Account Locator Format
The Account Locator (historically called the Account Name ) is an immutable, system-generated alphanumeric identifier (e.g., XY12345 or XY12345.us-east-1 ).
Connection URL: https://xy12345.us-east-1.snowflakecomputing.com
Architectural Drawback: Account locators are tied directly to the physical cloud provider and region where the account was born. If an account is replicated to another region or cloud for disaster recovery, the replica has a completely different account locator. Client applications hardcoded to account locators cannot fail over without code or configuration modifications.
2. Organization Account Name Format (Modern Standard)
Under Snowflake Organizations, accounts receive a user-defined account name within the organization namespace.
- Connection URL: https://<orgname>-<accountname>.snowflakecomputing.com
- Example: https://acme_corp-prod_analytics.snowflakecomputing.com
Architectural Advantages:
Fully decoupled from underlying cloud provider and region details.
Highly human-readable and standardized across CI/CD pipelines.
Stays the same if the account's locator format is unfamiliar to users, but it still identifies one specific account .
3. Connection URLs for Client Redirect
An account URL cannot redirect traffic to a different account. For business continuity, Client Redirect uses a separate connection object with its own URL: https://<orgname>-<connection_name>.snowflakecomputing.com . During a failover you promote the connection in the secondary account, and clients that use the connection URL are routed there without changing their connection strings (Business Critical Edition or higher; see Section 6.2). -- Renaming an account identifier within an organization
- USE ROLE ORGADMIN;
- ALTER ACCOUNT old_staging_account RENAME TO nonprod_stage;
Exam Trap: Renaming an account modifies its Organization URL ( <orgname>-<newaccountname> ), but the underlying Account Locator remains permanently unchanged. Historical logs in ACCOUNT_USAGE and support tickets often continue to reference the immutable Account Locator.
Organizational Telemetry: ORGANIZATION_USAGE vs. ACCOUNT_USAGE
Snowflake provides centralized auditing and cost monitoring across all accounts in the organization via the ORGANIZATION_USAGE schema in the shared SNOWFLAKE database. The schema is available in the organization account (including premium views) and in a regular account that has ORGADMIN enabled.
Comparing Metadata Schemas
- Telemetry Metric SNOWFLAKE.ACCOUNT_USAGE SNOWFLAKE.ORGANIZATION_USAGE
- Scope Current single account only All accounts in the entire Organization
Required Role ACCOUNTADMIN (or granted access) GLOBALORGADMIN in the organization account, or ORGADMIN in an ORGADMIN-enabled account
Data Latency 45 minutes to 3 hours for most views Varies by view: about 2 hours ( STORAGE_DAILY_HISTORY ), 24 hours ( ACCOUNTS , RATE_SHEET_DAILY ), 72 hours ( USAGE_IN_CURRENCY_DAILY )
Data Retention 365 days (1 year) 365 days (1 year)
Primary Views QUERY_HISTORY , WAREHOUSE_METERING_HISTORY , LOGIN_HISTORY ACCOUNTS , USAGE_IN_CURRENCY_DAILY , RATE_SHEET_DAILY , STORAGE_DAILY_HISTORY
Key ORGANIZATION_USAGE Views for Architects
ACCOUNTS : Lists all active, deleted, and pending accounts in the organization, including their editions, cloud regions, creation timestamps, and account locators.
USAGE_IN_CURRENCY_DAILY : Displays daily credit consumption translated into contract currency across all accounts, broken down by compute, cloud services, and storage.
RATE_SHEET_DAILY : Details contractual pricing and credit rates per service type across accounts.
STORAGE_DAILY_HISTORY : Tracks daily storage usage (active storage, Time Travel, and Fail-safe) across all accounts in the organization. -- Enterprise cross-account spend audit over the past 30 days
USE ROLE GLOBALORGADMIN; -- or ORGADMIN in an ORGADMIN-enabled account
- SELECT
- account_name,
- region,
- service_type,
- usage_date,
- usage_in_currency,
- credits_billed
- FROM snowflake.organization_usage.usage_in_currency_daily
- WHERE usage_date >= DATEADD('day', -30, CURRENT_DATE())
- ORDER BY usage_date DESC, credits_billed DESC;
- Cross-Account Administrative Considerations & Exam Traps
When architecting multi-account governance models, consider the following boundary rules:
1. Resource Monitor Inheritance (CRITICAL EXAM TRAP)
Resource Monitors are strictly account-scoped objects.
There is NO organization-level resource monitor that can cap credits across multiple accounts.
An architect cannot create a resource monitor in the primary account and apply it to a secondary account.
Solution: Resource monitors must be defined and applied independently within each individual account by an ACCOUNTADMIN .
2. Cross-Account Data Sharing
Accounts in the same organization located within the same cloud region can share data instantly using standard Secure Data Sharing without copying data or paying data transfer fees.
Accounts in different regions or clouds cannot directly query a standard secure share without replication. The data provider must establish a Replication Group or enable Cross-Cloud Auto-Fulfillment to replicate data to the consumer's region before sharing.
3. User Identity & Authentication
Users are scoped to individual accounts. An identity named JSMITH in Account A is technically distinct from JSMITH in Account B.
Enterprise architects integrate a centralized Identity Provider (IdP) via SAML 2.0 SSO , automate provisioning with SCIM , and can use organization users to avoid re-creating the same person or service in every account.