Study guide

3.5 Network Policies, Network Rules, External Access & Private Connectivity

SnowPro Advanced: Architect ARA-C01

Track your progress as you read

Finished sections get a check mark.

1 Introduction: The ARA-C01 Exam

About the SnowPro Advanced: Architect (ARA-C01) Exam

2 Chapter 1: Account Strategy & Organization Architecture

1.1 Multi-Account Strategy & Snowflake Organizations 1.2 Snowflake Parameter Hierarchy & Configuration 1.3 Database and Schema Design Architecture

3 Chapter 2: Identity, Access Control & Storage Integrations

2.1 Role-Based Access Control Architecture & Hierarchy 2.2 Secondary Roles, Object Ownership & Delegated Administration 2.3 Cloud Storage Integrations & IAM Trust Policies 2.4 Identity Federation, SSO, SCIM & Authentication Policies

4 Chapter 3: Governance, Data Privacy, Network Security & Compliance

3.1 Column-Level Masking & Row Access Policies 3.2 Object Tagging, Tag-Based Masking & Audit Governance 3.3 Encryption, Key Management & Tri-Secret Secure 3.4 Aggregation Policies, Projection Policies & External Tokenization 3.5 Network Policies, Network Rules, External Access & Private Connectivity 3.6 Snowflake Editions & Compliance Architecture (PCI DSS, PII & PHI)

5 Chapter 4: Data Modeling in Snowflake

4.1 Dimensional Modeling: Star vs. Snowflake Schemas 4.2 Data Vault 2.0 Architecture in Snowflake 4.3 Relational Constraints & Query Optimizer Integration

6 Chapter 5: Data Sharing & Collaboration Solutions

5.1 Direct Data Sharing Architecture & Security 5.2 Managed Reader Accounts for External Consumers 5.3 Snowflake Marketplace, Data Exchange & Clean Rooms

7 Chapter 6: Multi-Cloud, Multi-Region & Business Continuity

6.1 Database & Account Replication Mechanics 6.2 Disaster Recovery Architecture & Client Redirect 6.3 Cross-Cloud Auto-Fulfillment & Listing Replication 6.4 Data Protection: Time Travel, Fail-safe & Storage Costs

8 Chapter 7: Environments, Lakehouse, DevOps & AI/ML Applications

7.1 Multi-Tier Environment Strategy & Zero-Copy Cloning 7.2 Data Lakehouse Architecture & Apache Iceberg 7.3 DataOps, CI/CD & Snowflake Git Integration 7.4 AI/ML Pipelines & Applications: Cortex AI, ML Functions, Snowpark Container Services, Streamlit & Native Apps

9 Chapter 8: Data Ingestion Architecture

8.1 Bulk Ingestion Architecture: COPY INTO Optimization 8.2 Snowpipe Continuous Automated Ingestion 8.3 Snowpipe Streaming & Real-Time Ingestion 8.4 Data Unloading Architecture & Cloud Export Patterns 8.5 Schema Detection, Schema Evolution & Source-Change Architecture

10 Chapter 9: Continuous Pipelines & Stream Transformation

9.1 Change Data Capture (CDC) with Snowflake Streams 9.2 Task Orchestration, DAGs & Serverless Scheduling 9.3 Declarative Data Pipelines with Dynamic Tables 9.4 Views, Materialized Views & Transformation Table Design

11 Chapter 10: Semi-Structured Data & Ecosystem Tooling

10.1 Semi-Structured Data: VARIANT, OBJECT & ARRAY Processing 10.2 Snowflake Ecosystem Connectors, Drivers & SQL API 10.3 Snowpark, User-Defined Functions & Stored Procedures

12 Chapter 11: Virtual Warehouse Architecture & Concurrency

11.1 Virtual Warehouse Architecture, Sizing & Credit Economics 11.2 Multi-Cluster Warehouses & Concurrency Scaling Policies 11.3 Warehouse Types & Query Acceleration Service

13 Chapter 12: Query Profiling & Performance Diagnostics

12.1 Query Profile Deep-Dive & Bottleneck Analysis 12.2 Memory Spilling, Warehouse Queuing & Timeout Governance 12.3 Three-Tier Caching Architecture & Result Reuse

14 Chapter 13: Storage Optimization, Cost Governance & Observability

13.1 Micro-Partitioning & Automatic Clustering 13.2 Search Optimization Service (SOS) & Point Lookup Acceleration 13.3 Resource Monitors, Financial Governance & Usage Observability 13.4 Warehouse Monitoring, Alerts, Event Tables & Performance Explorer

3.5 Network Policies, Network Rules, External Access & Private Connectivity

Key Takeaways Explain This Topic AI

Network rules are schema-level objects that group network identifiers; network policies use them for inbound (INGRESS) control, and external access integrations use EGRESS rules to let UDFs and procedures reach approved hosts.

Network policies can be applied to the account, a user, or a security integration; the most specific wins (security integration over user over account), and blocked lists are evaluated before allowed lists.

Private-endpoint rule types (AWSVPCEID, AZURELINKID, GCPPSCID) take precedence over IPv4/IPv6 rules for requests arriving over private connectivity.

AWS PrivateLink, Azure Private Link, and Google Cloud Private Service Connect require Business Critical Edition or higher and use dedicated privatelink hostnames resolved through private DNS.

SYSTEM$ALLOWLIST and SYSTEM$ALLOWLIST_PRIVATELINK return the hostnames and ports clients must reach, and SnowCD uses that output to diagnose connectivity.

Last updated: September 2026

Network Security in Two Directions

The blueprint's objective 1.3 lists network policies, network rules, external access, access control privileges, and private connectivity . Architects should separate the two directions of traffic:

Direction Control Object type

Inbound to Snowflake (users, drivers, internal stages) Network policy that references network rules (or legacy IP lists) Account-level network policy; schema-level network rules

Outbound from Snowflake code (UDFs, procedures, Snowpark Container Services) External access integration that references egress network rules and secrets Account-level integration; schema-level network rules and secrets

Private paths in either direction PrivateLink / Private Link / Private Service Connect Cloud endpoints + Snowflake configuration (Business Critical+)

Network Rules

A network rule is a schema-level object that groups network identifiers. It does not say whether traffic is allowed; the feature that uses it decides that.

  • TYPE Identifiers Typical MODE
  • IPV4 / IPV6 IP addresses or CIDR ranges (IPv6 on AWS only) INGRESS
  • AWSVPCEID AWS VPC endpoint IDs INGRESS or INTERNAL_STAGE
  • AZURELINKID Azure private endpoint LinkIDs INGRESS
  • GCPPSCID Google Cloud PSC connection IDs INGRESS

HOST_PORT / PRIVATE_HOST_PORT Domain names with optional ports EGRESS CREATE NETWORK RULE security.rules.corp_vpn

  • MODE = INGRESS TYPE = IPV4
  • VALUE_LIST = ('198.51.100.0/24');
  • CREATE NETWORK RULE security.rules.prod_vpce
  • MODE = INGRESS TYPE = AWSVPCEID
  • VALUE_LIST = ('vpce-0a1b2c3d4e5f67890');
  • Network Policies

A network policy restricts inbound access using ALLOWED_NETWORK_RULE_LIST and BLOCKED_NETWORK_RULE_LIST (the older ALLOWED_IP_LIST and BLOCKED_IP_LIST still work, but Snowflake recommends network rules). CREATE NETWORK POLICY corp_access

ALLOWED_NETWORK_RULE_LIST = ('security.rules.corp_vpn', 'security.rules.prod_vpce');

  • ALTER ACCOUNT SET NETWORK_POLICY = corp_access; -- SECURITYADMIN or higher
  • ALTER USER svc_loader SET NETWORK_POLICY = loader_only; -- user-level override

Evaluation rules that are frequently tested:

Blocked before allowed. Blocked entries are applied first; if an identifier is in an allowed rule, other identifiers of the same type are implicitly blocked.

Most specific policy wins. A policy on a security integration (for example an OAuth or SAML integration) overrides a user policy, which overrides the account policy. The more general policy is not evaluated at all for that request.

Private endpoints win over IP rules. For a request arriving over private connectivity, AWSVPCEID / AZURELINKID rules in the allowed list take precedence, and IPv4/IPv6 rules are ignored.

Internal stages. On AWS, ENFORCE_NETWORK_RULES_FOR_INTERNAL_STAGES = TRUE lets network rules also protect internal stages.

Lockout protection. Snowflake prevents activating an account-level policy that would block the administrator's current IP address; check SELECT CURRENT_IP_ADDRESS(); first.

Outbound Access: External Access Integrations

UDFs and stored procedures cannot reach the internet by default. To let handler code call an approved API:

Create an egress network rule ( MODE = EGRESS , TYPE = HOST_PORT ) listing the allowed hosts.

Store credentials in a secret (for example TYPE = GENERIC_STRING or OAuth2).

Create an external access integration that references the network rules and allowed secrets.

Create the function or procedure with EXTERNAL_ACCESS_INTEGRATIONS = (...) and SECRETS = (...) . CREATE NETWORK RULE security.rules.fx_api

  • MODE = EGRESS TYPE = HOST_PORT
  • VALUE_LIST = ('api.exchangerates.example.com:443');

CREATE SECRET security.secrets.fx_key TYPE = GENERIC_STRING SECRET_STRING = '...';

  • CREATE EXTERNAL ACCESS INTEGRATION fx_api_access
  • ALLOWED_NETWORK_RULES = (security.rules.fx_api)
  • ALLOWED_AUTHENTICATION_SECRETS = (security.secrets.fx_key)
  • ENABLED = TRUE;

Any call to a host that is not in an allowed rule is denied. Administrators audit calls in the EXTERNAL_ACCESS_HISTORY view. External access is available in all editions; routing it over private connectivity requires Business Critical Edition and ACCOUNTADMIN . External access integrations have largely replaced external functions (which route calls through a cloud API gateway) for new designs.

Access Control Privileges Behind These Objects

Creating network policies and account-level integrations is an administrative task ( SECURITYADMIN / ACCOUNTADMIN or roles granted CREATE NETWORK POLICY / CREATE INTEGRATION ).

Developers need USAGE on an external access integration and READ on the secrets it allows before they can reference them in a function.

Network rules and secrets are schema objects, so ownership and USAGE on the governance schema decide who can change them.

Private Connectivity

AWS PrivateLink , Azure Private Link , and Google Cloud Private Service Connect let clients reach Snowflake through a private endpoint in the customer's own network instead of the public internet. They require Business Critical Edition (or higher).

Clients connect to a privatelink hostname , such as <orgname>-<account_name>.privatelink.snowflakecomputing.com , which private DNS in the customer network resolves to the endpoint.

Private connectivity can also cover internal stages , outbound traffic to external stages and external volumes , and the connection to the key management service used by Tri-Secret Secure.

Combine private endpoints with a network policy that allows only the approved endpoint IDs, so traffic from any other path is rejected.

SYSTEM$ALLOWLIST() (public endpoints) and SYSTEM$ALLOWLIST_PRIVATELINK() return the hostnames and ports that firewalls must allow; the SnowCD tool uses that output to test connectivity.

Worked Scenario: Layering Network Controls

A multinational bank has three access paths: employees on the corporate VPN, ETL services running in an AWS VPC connected by PrivateLink, and a partner analytics tool that authenticates with External OAuth.

  • Access path Control Why
  • Employees on VPN Account-level policy allowing an IPV4 rule with the VPN egress ranges Default for everyone

ETL service users User-level policy allowing only an AWSVPCEID rule for the ETL VPC endpoint Stricter than the account policy; service users cannot connect from anywhere else

Partner tool via External OAuth Network policy attached to the security integration allowing only the partner's published IP ranges The integration-level policy overrides both user and account policies for that path

Internal stages ENFORCE_NETWORK_RULES_FOR_INTERNAL_STAGES = TRUE with an AWSVPCEID rule File uploads and downloads follow the same private path (AWS)

Design checks that often appear as exam distractors:

Only one network policy can be active on the account at a time; activating a new one replaces the old.

A user-level policy replaces (does not add to) the account policy for that user, so it must include every path that user legitimately needs.

Before activating any policy, confirm that the administrator's current IP or private endpoint is in the allowed list — Snowflake rejects activation otherwise.

Monitor denied logins in LOGIN_HISTORY and inventory policies and rules with NETWORK_POLICIES , NETWORK_RULES , and NETWORK_RULE_REFERENCES views.

Loading diagram... Inbound and Outbound Network Controls in Snowflake