Chapter 1 of 4 · Snowflake ARA-C01

Accounts and Security

Account strategy, parameters, RBAC, data policies, governance, network, encryption and sign in.

  • 17topics
  • 1 h 25 minfast track
  • 8diagrams and exhibits
  • 25%of the exam

Topics in this chapter

Take them in order, or jump to the one you need.

  1. 1Account and Database Strategy - One Account or ManyDecide between one Snowflake account and many: benefits, limits, isolation, cross-account features, constraints and the use cases…5 min
  2. 2Snowflake Parameters - Account, Object, Session and the HierarchyLearn the three Snowflake parameter types, how account, object and session parameters override each other, and how to set them…Diagram5 min
  3. 3Security Architecture, RBAC Hierarchy, Inheritance and Database RolesDesign a layered Snowflake security architecture and build the RBAC hierarchy: privilege inheritance, future grants, managed…5 min
  4. 4System Roles, Functional and Access Roles, and Secondary RolesKnow the Snowflake system roles and best practices, how functional roles differ from access roles, and how secondary roles…Diagram5 min
  5. 5Data Access, Storage Integrations and Secure ViewsControl data access in Snowflake: storage integrations for cloud storage without credentials, secure views that hide logic and…Diagram6 min
  6. 6Data Governance and Column-Level Security - Masking and TokenizationProtect sensitive columns with Dynamic Data Masking and external tokenization: policy syntax, conditional and tag based masking…5 min
  7. 7Row-Level Security, Aggregation and Projection PoliciesRestrict rows with row access policies and protect privacy with aggregation and projection policies: syntax, mapping tables…Diagram5 min
  8. 8Data Lineage, Dependencies and Object TaggingTrace data with Snowflake lineage, OBJECT_DEPENDENCIES and ACCESS_HISTORY, and classify it with object tags, inheritance…5 min
  9. 9Compliance, Editions, PCI and PII/PHIPick the right Snowflake edition for compliance: what Business Critical adds for PCI DSS, PHI and HIPAA, and how editions differ…5 min
  10. 10Security Principles and EncryptionApply Snowflake security principles and know encryption: key hierarchy, 30 day rotation, rekeying, Tri-Secret Secure and…5 min
  11. 11Network Security, Network Policies and Their PrivilegesRestrict who can reach Snowflake with network policies: allowed and blocked lists, precedence, activation safeguards, internal…Diagram5 min
  12. 12Network Rules and External Network AccessUse network rules and external access integrations so UDFs and procedures can call outside services safely, with allowed hosts…5 min
  13. 13Private Connectivity - AWS PrivateLink, Azure Private Link, Google PSCKeep Snowflake traffic off the public internet with AWS PrivateLink, Azure Private Link or Google Private Service Connect, and…Diagram5 min
  14. 14User, Role and Grants Provisioning and SCIMProvision users, roles and grants at scale: system roles, SCIM with Okta or Entra ID, managed access schemas, future grants and…5 min
  15. 15Authentication Methods and Authentication PoliciesChoose Snowflake authentication methods per user type and enforce them with authentication policies: methods, client types, MFA…4 min
  16. 16Federated Authentication, SSO and OAuthDesign SSO with SAML2 or OIDC and choose between Snowflake OAuth and External OAuth: security integrations, roles, token…Diagram5 min
  17. 17Multi-Factor Authentication and Key-Pair AuthenticationEnforce MFA for people and key-pair authentication for services: passkeys, TOTP, Duo, MFA caching, RSA keys, rotation and public…5 min

About this chapter

What this chapter covers

Accounts and Security is the chapter on how an Architect lays out Snowflake accounts, controls who can do what, and protects data. For the SnowPro Advanced: Architect ARA-C01 exam it tests design decisions rather than definitions: one account or several, which role design, which policy, and why.

Questions are scenarios that start with "An Architect needs to ...". They are single answer, multiple select or interactive, and the right answer usually hinges on one trade-off such as isolation against administration effort, or an edition requirement.

How the topics fit together

Security is built in layers, and each layer has its own tools.

Account strategyregions, editionsconfigured byParametersaccount, object, sessionaccess throughRBACroles, database rolesdata protected byPoliciesmasking, row access, privacydescribed byGovernancetags, lineage
  • Account strategy decides when one account is enough and when residency, edition or isolation needs more.
  • Parameters set behavior at account, object and session level, and the lowest level wins.
  • RBAC builds the role tree: system roles, access roles, functional roles, database roles and secondary roles.
  • Data access and security cover storage integrations and secure views.
  • Governance covers masking, tokenization, row access, aggregation and projection policies, lineage and tags.
  • Compliance, network and authentication protect the front door and the edition; they continue on the later pages of this chapter.
Exam tip

Most policy features here (masking, row access, aggregation, projection, lineage, tag propagation) need Enterprise Edition or higher. When a scenario names a Standard account, expect an edition upgrade to be part of the answer.

How to use these pages

Each topic page has the same shape, so you can skim for what you need.

  • What it is: the idea in plain words.
  • How it works: the mechanism, with diagrams, SQL and comparison tables.
  • Common mistakes: the classic traps.
  • What to remember for the exam: the facts to memorize.
  • Check yourself: three questions to test your understanding.

Read the pages in order the first time. The policy pages reuse the roles and tags from the earlier ones.

Ready for more practice?

The full Snowflake ARA-C01 question bank has 687 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.