Study guide

3.6 Snowflake Editions & Compliance Architecture (PCI DSS, PII & PHI)

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

3.6 Snowflake Editions & Compliance Architecture (PCI DSS, PII & PHI)

Key Takeaways Explain This Topic AI

Standard, Enterprise, Business Critical, and Virtual Private Snowflake (VPS) editions are cumulative: each includes every feature of the edition below it.

Enterprise Edition adds multi-cluster warehouses, extended Time Travel up to 90 days, periodic rekeying, masking, row access, aggregation and projection policies, classification, ACCESS_HISTORY, materialized views, search optimization, and query acceleration.

Business Critical Edition adds Tri-Secret Secure, private connectivity, failover/failback and Client Redirect, and support for PHI (HIPAA/HITRUST), PCI DSS, and regulated public-sector workloads such as FedRAMP and ITAR.

Before storing PHI, a signed business associate agreement (BAA) must be in place with Snowflake, and the account must be Business Critical or higher.

VPS runs Business Critical features in a completely separate Snowflake environment that shares no hardware with accounts outside the VPS.

Last updated: September 2026

Why Editions Are an Architecture Decision

The edition determines per-credit and storage prices and which security, governance, and continuity features exist. Because editions are chosen per account, architects often mix them inside one organization: a Business Critical account for regulated data, Enterprise accounts for general analytics, and sometimes Standard for sandboxes (Section 1.1).

Feature-to-Edition Map (Exam Essentials)

  • Capability Standard Enterprise Business Critical VPS
  • Automatic encryption, MFA, SSO/federation, OAuth, network policies ✔ ✔ ✔ ✔
  • Time Travel up to 1 day; 7-day Fail-safe ✔ ✔ ✔ ✔
  • Database and share replication ✔ ✔ ✔ ✔
  • Extended Time Travel (up to 90 days) ✔ ✔ ✔
  • Multi-cluster warehouses ✔ ✔ ✔
  • Masking, row access, aggregation and projection policies; external tokenization ✔ ✔ ✔
  • Sensitive data classification; ACCESS_HISTORY ✔ ✔ ✔
  • Periodic rekeying ✔ ✔ ✔
  • Materialized views, search optimization, query acceleration ✔ ✔ ✔
  • Tri-Secret Secure (customer-managed key) ✔ ✔
  • Private connectivity (PrivateLink, Private Link, PSC) ✔ ✔
  • Account object replication, failover/failback, Client Redirect ✔ ✔
  • PHI (HIPAA/HITRUST CSF), PCI DSS, FedRAMP/ITAR public-sector support ✔ ✔
  • Dedicated metadata store and compute pool, isolated environment ✔

Features available in every edition include Snowpark, Streamlit in Snowflake, dynamic tables, external and Iceberg tables, schema detection and evolution, external functions and external access, clustering with automatic maintenance, and resource monitors.

Exam Trap: "Replication requires Business Critical" is only half true. Database and share replication work in all editions ; replicating other account objects (users, roles, warehouses, network policies, integrations) and failover/failback require Business Critical.

  • Compliance Scenarios
  • Personal Data (PII)

PII rules (for example GDPR or state privacy laws) are met with governance design more than with an edition switch:

Classify data to find PII, then protect it with tag-based masking, row access policies, and projection or aggregation policies (Enterprise).

Keep regional data in accounts deployed in the required cloud region; replicate only what policy permits.

Use ACCESS_HISTORY (Enterprise) to prove who read which columns, and Time Travel retention settings plus deletion processes to honor retention limits.

Protected Health Information (PHI)

Snowflake supports PHI subject to HIPAA and HITRUST CSF only on Business Critical Edition or higher .

A signed business associate agreement (BAA) between the customer and Snowflake must be in place before any PHI is stored.

Typical architecture: a dedicated Business Critical account for clinical data, private connectivity, Tri-Secret Secure if the organization wants control of a key, and shares or replication to other accounts only for de-identified data.

Payment Card Data (PCI DSS)

PCI DSS support is a Business Critical capability.

Reduce scope: tokenize card numbers before loading (External Tokenization, Section 3.4) so most accounts and roles never touch real card data.

Isolate the cardholder-data environment in its own account, restrict inbound access with private connectivity and network policies, and restrict unloading with PREVENT_UNLOAD_TO_INLINE_URL and storage-integration-only stages (Section 8.4).

Government and Regulated Regions

Business Critical supports public-sector workloads such as FedRAMP and ITAR (in the appropriate government regions) and IRAP Protected data in specified Asia Pacific regions.

Organizations that mix government and commercial regions ("hybrid organizations") should place the organization account in the regulated region, because organization-level features can move metadata between regions.

Virtual Private Snowflake (VPS)

VPS includes everything in Business Critical but runs in a completely separate Snowflake environment with its own metadata store and compute pool; it shares no hardware with accounts outside the VPS and encrypts internal traffic between its components. It suits institutions whose risk policies prohibit multi-tenant infrastructure.

  • Designing for Cost and Compliance Together Organization
  • ├── prod_phi (Business Critical, AWS us-east-1) PHI, BAA signed, PrivateLink, Tri-Secret Secure
  • ├── prod_general (Enterprise, AWS us-east-1) De-identified analytics via secure share
  • └── dev_sandbox (Standard or Enterprise) Synthetic or masked data only

Only the account that must meet the regulation pays Business Critical prices, and data leaves it only through controls the architect chooses (secure views, aggregation policies, de-identification pipelines).

Mapping Requirements to Snowflake Controls

Compliance questions on the exam usually hide a requirement inside a scenario. This table translates common requirement phrases into the Snowflake capability and minimum edition:

  • Requirement in the scenario Snowflake control Minimum edition
  • "Customer must hold and be able to revoke an encryption key" Tri-Secret Secure Business Critical

"No traffic over the public internet" AWS PrivateLink / Azure Private Link / Google Cloud PSC plus network policy on endpoint IDs Business Critical

"Recover within minutes from a regional outage without changing connection strings" Failover groups + Client Redirect Business Critical

  • "Mask PII for most roles, reveal for privacy officers" Masking policies (often tag-based) Enterprise
  • "Analysts may only see their region's rows" Row access policies Enterprise
  • "Partners may only see aggregates of at least N records" Aggregation policies Enterprise
  • "Prove who read a sensitive column last quarter" ACCESS_HISTORY Enterprise
  • "Keep 60 days of history for accidental-change recovery" DATA_RETENTION_TIME_IN_DAYS = 60 Enterprise
  • "Re-encrypt data whose keys are over a year old" Periodic rekeying Enterprise
  • "Store PHI" BAA plus Business Critical account Business Critical
  • "Card data in scope for PCI DSS" Business Critical account; tokenization to shrink scope Business Critical
  • "No shared hardware with other customers" Virtual Private Snowflake VPS

Two recurring reasoning patterns:

Pick the lowest edition that satisfies every stated requirement. If a scenario needs masking and 30-day Time Travel but nothing from Business Critical, Enterprise is the correct, cheaper answer.

Isolate regulated workloads in their own account. Because edition is per account, a single Business Critical account can host regulated data while other accounts in the organization stay on Enterprise or Standard, connected through secure shares or replication of de-identified data.

Loading diagram... Selecting an Edition from Requirements