Exam Focus · Part 3
Grants decide what a role may do; policies decide what it sees. Pick the control that fits.
Know these cold
| Topic | Remember |
|---|---|
| Grant direction | Privileges → roles → users. The parent role inherits; nothing flows down |
| System roles | ACCOUNTADMIN inherits SECURITYADMIN (which inherits USERADMIN) and SYSADMIN. All inherit PUBLIC |
| Custom roles | Grant them to SYSADMIN, or it can't manage their objects |
| One SELECT needs | USAGE on warehouse, database and schema, plus SELECT on the object |
| ALL vs FUTURE | ALL: objects that exist now. FUTURE: objects created later |
| Managed access schema | Only the schema owner or MANAGE GRANTS can grant on its objects |
| Database role | Granted to account roles and shares. Never to users, never active in a session |
| Sign-in | People with passwords need MFA. SERVICE users: key pair, OAuth, workload identity, PAT |
| Network policy | Integration > user > account, one applies. Blocked wins on overlap |
| Masking, row access | Enterprise+. 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.

