Study guide
3.2 Core Workflows and Decision Points
SnowPro Core Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SnowPro Core Orientation and Exam Strategy
1.1 Current SnowPro Core Exam Facts 1.2 Eligibility, Registration, and Scheduling 1.3 Blueprint Domains and Weighting 1.4 Editions, Question Style, and Score Report Thinking 1.5 Study Calendar and Hands-On Practice Plan
2 Chapter 2: Snowflake AI Data Cloud Features and Architecture
2.1 Snowflake AI Data Cloud Features and Architecture Overview 2.2 Core Workflows and Decision Points 2.3 Scenario Practice for Snowflake AI Data Cloud Features and Architecture 2.4 Common Traps in Snowflake AI Data Cloud Features and Architecture 2.5 Practice Drills and Readiness Markers
3 Chapter 3: Account Management and Data Governance
3.1 Account Management and Data Governance Overview 3.2 Core Workflows and Decision Points 3.3 Scenario Practice for Account Management and Data Governance 3.4 Common Traps in Account Management and Data Governance 3.5 Practice Drills and Readiness Markers
4 Chapter 4: Data Loading, Unloading, and Connectivity
4.1 Data Loading, Unloading, and Connectivity Overview 4.2 Core Workflows and Decision Points 4.3 Snowpipe, External Tables, and Storage Integrations 4.4 Bulk Unloading and Semi-Structured Data 4.5 Connectors, Drivers, and Snowsight Loading
5 Chapter 5: Performance Optimization, Querying, and Transformation
5.1 Performance Optimization, Querying, and Transformation Overview 5.2 Core Workflows and Decision Points 5.3 Micro-Partitions, Pruning, Clustering, and the Query Profile 5.4 Search Optimization, Materialized Views, and Query Best Practices 5.5 Transformations: ELT, Streams & Tasks, and Semi-Structured Data
6 Chapter 6: Data Collaboration
6.1 Secure Data Sharing Architecture 6.2 Creating Shares, Granting Objects, and Reader Accounts 6.3 Snowflake Marketplace, Listings, and Data Exchange 6.4 Secure Views, Cross-Region Sharing, and Governance 6.5 Choosing the Right Sharing Method and Readiness Drills
7 Chapter 7: Final Review and Test Day
7.1 Timed Practice Strategy 7.2 Last-Week Review Map 7.3 Exam-Day Checklist 7.4 After the Exam and Next Steps
3.2 Core Workflows and Decision Points
Key Takeaways Explain This Topic AI
The default role hierarchy is ACCOUNTADMIN > (SECURITYADMIN + SYSADMIN); SECURITYADMIN inherits USERADMIN; every role ultimately rolls up to PUBLIC at the bottom.
ORGADMIN manages organization-level tasks (creating accounts); ACCOUNTADMIN is the top account role and should be limited and protected with MFA.
USERADMIN creates and manages users and roles; SECURITYADMIN manages grants globally; SYSADMIN creates databases, schemas, and warehouses.
Future grants (GRANT ... ON FUTURE) automatically apply a privilege to objects created later in a schema or database.
Role inheritance means a parent role automatically holds every privilege of the child roles granted to it; users switch roles with USE ROLE.
Last updated: October 2026
The System-Defined Role Hierarchy
Snowflake ships with six system-defined roles that cannot be dropped and have built-in privileges. The exam tests their responsibilities and their position in the hierarchy precisely.
Role Responsibility
ORGADMIN Organization-level operations: create and manage accounts, view organization usage. Not in the account-role tree.
ACCOUNTADMIN Top-level account role. Inherits SECURITYADMIN and SYSADMIN. Views and manages billing and credit data. Not a superuser. Should be limited.
SECURITYADMIN Manages grants globally (MANAGE GRANTS), monitors and manages users/roles. Inherits USERADMIN.
USERADMIN CREATE USER and CREATE ROLE privileges; manages users and roles it owns.
SYSADMIN Creates and manages databases, schemas, and warehouses . All custom roles should be granted to SYSADMIN.
PUBLIC Automatically held by every user; default low-level role. Any object granted to PUBLIC is visible to everyone.
The default inheritance is: ACCOUNTADMIN sits above both SYSADMIN and SECURITYADMIN ; SECURITYADMIN sits above USERADMIN ; and everything rolls up from PUBLIC at the bottom. ACCOUNTADMIN therefore inherits all privileges below it.
Role Inheritance and Custom Roles
Role inheritance means that if role A is granted to role B, then B automatically holds every privilege of A. This is how privileges aggregate. Snowflake's recommended pattern is to build custom roles for business functions (e.g., ANALYST , DATA_ENGINEER ), grant object privileges to those custom roles, and then grant the custom roles to SYSADMIN . That way SYSADMIN — and therefore ACCOUNTADMIN — can manage everything, while end users hold only the narrow custom role they need.
Switching and activating roles
A user can be granted many roles but uses one primary (current) role at a time, activated with USE ROLE my_role . Secondary roles can be activated with USE SECONDARY ROLES ALL , letting a session combine privileges across roles. The role that creates an object becomes its owner and holds OWNERSHIP, which can be transferred with GRANT OWNERSHIP .
Standard grant workflow
To give an analyst read access to a schema's tables:
USE ROLE USERADMIN; then CREATE ROLE ANALYST;
USE ROLE SECURITYADMIN; then GRANT USAGE ON DATABASE sales TO ROLE ANALYST; and GRANT USAGE ON SCHEMA sales.public TO ROLE ANALYST;
- GRANT SELECT ON ALL TABLES IN SCHEMA sales.public TO ROLE ANALYST;
- GRANT ROLE ANALYST TO USER jdoe; and GRANT ROLE ANALYST TO ROLE SYSADMIN;
Future Grants and Decision Points
GRANT SELECT ON ALL TABLES IN SCHEMA ... covers tables that exist now . To automatically cover tables created later , you need a future grant : GRANT SELECT ON FUTURE TABLES IN SCHEMA sales.public TO ROLE ANALYST;
Remember: a future grant defined at the schema level takes precedence over one defined at the database level for objects in that schema, and ALL + FUTURE together cover both existing and new objects.
Which role for which task — the decision table
- Task Correct role
- Create a new account in the organization ORGADMIN
- Create a database or warehouse SYSADMIN
- Create a user or a role USERADMIN
- Grant a role to a user across the account SECURITYADMIN (has MANAGE GRANTS)
- View account billing / set a resource monitor at account level ACCOUNTADMIN
- ACCOUNTADMIN discipline
Because ACCOUNTADMIN is the most powerful role (it configures account-level parameters and can view and manage billing and credit data), Snowflake recommends: assign it to a limited number of people, but at least two users , require multi-factor authentication for those users, and do not make it anyone's default role. It is not a superuser, though: it sees and manages objects only through privileges held by it or roles below it, which is why custom roles should be granted up to SYSADMIN. Many exam stems reward choosing the least-privileged role that still completes the task rather than reaching for ACCOUNTADMIN.
Revoking, Inspecting, and Common Workflow Traps
Grants are reversed with REVOKE . Revoking a privilege from a role removes it from every user and child role that inherited it, which can have a wider blast radius than expected. To inspect the current state, use the metadata commands: SHOW GRANTS TO ROLE analyst (privileges a role holds), SHOW GRANTS TO USER jdoe (roles a user has), and SHOW GRANTS ON TABLE customers (everyone who can touch an object). These commands are themselves test material — know which one answers "who can read this table?" ( SHOW GRANTS ON ... ) versus "what can this role do?" ( SHOW GRANTS TO ROLE ... ).
The default-role nuance
Each user has a default role ( DEFAULT_ROLE ) that activates at login, but a user can USE ROLE to switch to any role granted to them. A user who "cannot see" an object often simply has the wrong current role active — not a missing grant. The fix is USE ROLE , not a new GRANT. Stems frequently bury this distinction.
Workflow checklist
- Goal Command sequence
- New read role CREATE ROLE > GRANT USAGE (db, schema) > GRANT SELECT > GRANT ROLE to user and to SYSADMIN
Cover future objects GRANT ... ON FUTURE ...
- Hand off an object GRANT OWNERSHIP ... COPY CURRENT GRANTS
- Audit access SHOW GRANTS ON / TO ROLE / TO USER
Working this checklist mechanically prevents the two most common mistakes: forgetting the USAGE chain, and forgetting to grant the new custom role up to SYSADMIN so administrators retain control.