Course contents

SnowPro Core COF-C03 Study GuidePart 3: Access control and securityExam Focus: Part 3

Exam Focus: Part 3

Exam Focus · Part 3

Grants decide what a role may do; policies decide what it sees. Pick the control that fits.

Know these cold

TopicRemember
Grant directionPrivileges → roles → users. The parent role inherits; nothing flows down
System rolesACCOUNTADMIN inherits SECURITYADMIN (which inherits USERADMIN) and SYSADMIN. All inherit PUBLIC
Custom rolesGrant them to SYSADMIN, or it can't manage their objects
One SELECT needsUSAGE on warehouse, database and schema, plus SELECT on the object
ALL vs FUTUREALL: objects that exist now. FUTURE: objects created later
Managed access schemaOnly the schema owner or MANAGE GRANTS can grant on its objects
Database roleGranted to account roles and shares. Never to users, never active in a session
Sign-inPeople with passwords need MFA. SERVICE users: key pair, OAuth, workload identity, PAT
Network policyIntegration > user > account, one applies. Blocked wins on overlap
Masking, row accessEnterprise+. Row access drops rows first; masking then hides values

Traps

  • Myth Setting DEFAULT_ROLE gives the user that role.Fact Defaults only point. GRANT ROLE gives access.
  • Myth ACCOUNTADMIN always sees unmasked values.Fact No role is exempt unless the policy body says so.
  • Myth Database-level and schema-level future grants combine.Fact Schema-level ones win, and the database-level ones are ignored there.
Before you turn the page
  • Draw the system role tree and say which way privileges flow.
  • List the four privileges one SELECT needs.
  • Say which policy hides rows, which hides values, and which runs first.