SnowPro Advanced Architect study guide
SnowPro Advanced Architect · Work through your exam, one topic at a time.
The SnowPro Advanced: Architect credential is Snowflake's advanced-level certification for data platform professionals who design, secure, and operate solutions on the Snowflake Data Cloud. It sits above the associate-level core certification and is aimed at architects, senior data engineers, and platform leads who make design decisions rather than only writing queries: choosing warehouse and storage strategies, structuring roles and network policies, tuning workloads, governing data access, and enabling secure data sharing and pipelines across an organization. The SnowPro Advanced Architect study guide has 8 sections and about 2,206 words.
01Snowflake Architecture and Features
Snowflake separates storage, compute, and cloud services. Data lives in cloud object storage as immutable, compressed, columnar micro-partitions (roughly 50–500 MB uncompressed).
307 words, about 2 min02Account Management and Security
Privileges are granted to roles, roles to roles, and roles to users. The system roles - ACCOUNTADMIN, SECURITYADMIN, SYSADMIN, USERADMIN - should form a disciplined hierarchy: SYSADMIN owns warehouses and databases, SECURITYADMIN manages grants, USERADMIN manages users and roles, and ACCOUNTADMIN is break-glass.
299 words, about 1 min03Performance and Query Optimization
Optimization starts with the profile: look for partitions scanned versus total, bytes spilled to local or remote storage, join explosion, and queueing. Pruning is the highest-leverage fix.
265 words, about 1 min04Data Governance and Data Protection
Snowflake encrypts data at rest with AES-256 and in transit with TLS; Tri-Secret Secure adds customer key control. Time Travel (0–90 days, Enterprise and above) lets you query and restore historical data; Fail-safe is a fixed 7-day recovery window available only to Snowflake Support, not to users.
265 words, about 1 min05Data Sharing and Data Collaboration
A share is a set of grants on database objects. Providers grant USAGE on the database and schema plus SELECT on tables or views, then add consumers.
266 words, about 1 min06Data Engineering and Continuous Data Pipelines
Streams capture change data on tables, views, and directories. A standard stream tracks inserts, updates, and deletes; append-only streams track inserts only.
258 words, about 1 min07Data Movement and Ingestion
Ingestion centers on stages: internal (named, table, or user stage) and external (S3, GCS, Azure). PUT and GET upload and download files and work only through a client (SnowSQL, drivers, Snowpark), not the web worksheet.
260 words, about 1 min08Cost Management and Resource Optimization
Warehouses consume credits by size and runtime (per-second billing with a 60-second minimum per start and resumption). Cloud services consume credits only above 10% of daily warehouse credits.
286 words, about 1 min