Study SnowPro COF-C02 Authentication and Network Policies: key concepts, common traps, and exam decision cues.
This lesson matters because Snowflake security questions usually start with a simple split: who is connecting, how they authenticate, and what network restrictions apply. If you jump straight to grants, you often solve the wrong problem.
| If the scenario is mostly about… | Strongest first fit |
|---|---|
| how a user signs in | authentication |
| where connections are allowed from | network policy |
| broad secure-baseline behavior | security principles |
| Question shape | First lane |
|---|---|
| who is this principal and how do they prove identity? | authentication |
| where is the connection coming from? | network policy |
| what can the principal do after sign-in? | authorization, usually roles and grants |
This order matters because Snowflake often gives answer choices from all three lanes in the same question.
| If the scenario shows… | Strong reading |
|---|---|
| SSO or key-pair language | authentication pattern is under test |
| allowed IP ranges | network policy is under test |
| secure-by-default design | principle-based security reasoning matters |
A user can fail to access Snowflake for different reasons:
Strong answers identify the failing layer first instead of throwing every security control at the problem.
| Trap | Better rule |
|---|---|
| treating network restrictions like role grants | connection source and permission scope are different lanes |
| assuming stronger authentication automatically grants more privilege | authentication proves identity, not authorization |
| answering every security question with the same control | choose the control that owns the requirement |
| Scenario clue | Stronger answer shape |
|---|---|
| “must sign in through SSO or key pair” | authentication path |
| “only certain IP ranges may connect” | network policy |
| “secure baseline with least exposure” | principle-led control choice |
| “signed in successfully but action still denied” | probably not authentication anymore |