Study guide

6.3 Cross-Cloud Auto-Fulfillment & Listing Replication

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

6.3 Cross-Cloud Auto-Fulfillment & Listing Replication

Key Takeaways Explain This Topic AI

Standard Snowflake Secure Data Sharing cannot cross cloud or region boundaries because it relies on intra-region metadata pointers without physical data movement.

Cross-Cloud Auto-Fulfillment delivers a listing's data product to other regions through a Snowflake-managed secure share area (SSA) and keeps it refreshed without manual replication.

The data provider pays for cross-cloud data egress, serverless replication compute credits, and remote cloud storage; the consumer pays only for the virtual warehouse compute used to query the local share.

Auto-Fulfillment replicates data locally into the consumer's target region, eliminating cross-region network latency and enabling high-performance local micro-partition pruning.

Refreshes can be interval-based (one minute to eight days), schedule-based, or triggered on demand with SYSTEM$TRIGGER_LISTING_REFRESH; private listings fulfill after target consumers get the listing and public listings after a consumer in a region gets it.

Last updated: September 2026

6.3 Cross-Cloud Auto-Fulfillment & Listing Replication

Snowflake's native Secure Data Sharing is renowned for its zero-copy architecture: a provider grants access to database objects via a share, and consumers instantly query the data without copying files, spinning up extraction jobs, or paying storage fees. However, this zero-copy primitive relies fundamentally on shared cloud storage metadata within a single physical cloud region.

When a provider on AWS US East (N. Virginia) needs to share datasets with a customer on Azure West Europe or GCP US Central (Iowa), direct metadata-only sharing is physically impossible because cloud object storage systems (AWS S3, Azure Blob, GCS) cannot cross cloud network boundaries without data transfer. To solve this challenge at global scale, Snowflake engineered Cross-Cloud Auto-Fulfillment .

Cross-Cloud Sharing Challenge & Auto-Fulfillment Architecture ┌────────────────────────────────────────────────────────────────────────────────────────┐

  • │ Snowflake Cross-Cloud Auto-Fulfillment │
  • │ │
  • │ Data Provider Account (AWS us-west-2) │
  • │ • Publishes Global Marketplace Listing or Private Share │
  • │ • Configures Auto-Fulfillment Refresh (interval, schedule, or trigger) │
  • │ │
  • │ Snowflake Autonomous Control Plane │
  • │ ┌────────────────────────────────────────────────┐ │
  • │ │ • Monitors Consumer Listing Requests │ │
  • │ │ • Provisions Secure Share Areas (SSA) │ │
  • │ │ • Manages Autonomous Serverless Replication │ │
  • │ └────────────────────────────────────────────────┘ │
  • │ │ │ │
  • │ Automated Egress ▼ ▼ Automated Egress │
  • │ ┌──────────────────────────────────────────┐ ┌──────────────────────────────────┐ │
  • │ │ Azure West Europe Secure Share Area │ │ GCP us-central1 Secure Share Area│ │
  • │ │ • Local Read-Only Database Replica │ │ • Local Read-Only Replica │ │
  • │ │ • Local Secure Share │ │ • Local Secure Share │ │
  • │ └──────────────────────────────────────────┘ └──────────────────────────────────┘ │
  • │ │ │ │
  • │ ▼ Local Zero-Copy Share ▼ Local Share │
  • │ ┌──────────────────────────────────────────┐ ┌──────────────────────────────────┐ │
  • │ │ Consumer Account A (Azure West Europe) │ │ Consumer Account B (GCP) │ │
  • │ │ • Queries data via LOCAL warehouse │ │ • Queries data via LOCAL wh │ │
  • │ │ • Zero cross-region network latency │ │ • Zero cross-region latency │ │
  • │ └──────────────────────────────────────────┘ └──────────────────────────────────┘ │
  • └────────────────────────────────────────────────────────────────────────────────────────┘
  • The Fundamental Barrier: Intra-Region vs. Cross-Cloud Sharing

Intra-Region Sharing (Standard Secure Data Sharing) :

Provider and consumer reside in the same cloud provider and same geographical region (e.g., both in AWS us-east-1 ).

Zero data movement: the consumer's virtual warehouse accesses the provider's underlying immutable S3 micro-partitions directly via cloud services metadata pointers.

No storage duplication, no data transfer charges.

Cross-Region / Cross-Cloud Sharing (The Requirement for Auto-Fulfillment) :

Provider and consumer reside in different regions (e.g., AWS us-east-1 to AWS eu-west-1 ) or different cloud providers (e.g., AWS to Azure or GCP).

Object storage perimeters prevent direct cross-cloud micro-partition queries.

Without Auto-Fulfillment : The provider would have to create accounts in every consumer region, replicate databases with replication groups, keep them refreshed, and create local shares in each account.

With Auto-Fulfillment : Snowflake provisions and manages a secure share area (SSA) in each needed region and keeps the data product refreshed.

How Auto-Fulfillment Works

The provider creates a Listing (either publicly on the Snowflake Marketplace or privately for specific consumer accounts).

When a consumer in a remote region gets the listing (or, for private listings, once the specified consumers get it), Snowflake transfers the data product to a secure share area (SSA) that Snowflake manages in that region. If the product already exists there, access is immediate.

The data product can be a share or a Native App application package ; a database used by several listings is fulfilled only once per region.

Later changes are synchronized according to the refresh configuration. For paid listings delivered to other regions, and for private listings to consumers in other regions, auto-fulfillment is the required mechanism.

Configuration, Fulfillment Groups & Refresh Schedules

Data providers configure Cross-Cloud Auto-Fulfillment through the Snowsight UI under Data Products > Provider Studio, or programmatically when managing listing objects.

Refresh Frequency & Data Freshness

The provider defines the replication schedule that governs how frequently updates in the primary database synchronize to target fulfillment regions:

Interval-based refresh: a cadence from one minute to eight days , set in Provider Studio or SQL; each completed refresh starts the next interval.

Schedule-based refresh: a cron-style schedule so consumers get updates at predictable times (interval and schedule cannot both apply).

Trigger-based refresh: SYSTEM$TRIGGER_LISTING_REFRESH (SQL only) refreshes on demand — ideal right after an upstream ETL pipeline finishes.

Managed compute: fulfillment runs on Snowflake-managed resources, not a provider warehouse.

When Fulfillment Happens

Listing type When Snowflake fulfills to a new region Cost implication

Private listing After the specified consumer accounts in that region get the listing Costs accrue only for regions you target

Public Marketplace listing After a consumer in that region gets the listing Costs follow real demand

Region already fulfilled Consumers get the data immediately Refresh costs continue while the product is available there

Telemetry & Auditing Auto-Fulfillment

Providers track fulfillment cost and activity with views such as:

SNOWFLAKE.DATA_SHARING_USAGE.LISTING_AUTO_FULFILLMENT_REFRESH_DAILY — refresh activity and credits by region.

SNOWFLAKE.DATA_SHARING_USAGE.LISTING_AUTO_FULFILLMENT_DATABASE_STORAGE_DAILY — storage used in remote regions.

SNOWFLAKE.ORGANIZATION_USAGE.LISTING_AUTO_FULFILLMENT_USAGE_HISTORY — organization-wide fulfillment usage (about 72 hours latency).

SNOWFLAKE.DATA_SHARING_USAGE.LISTING_ACCESS_HISTORY and LISTING_CONSUMPTION_DAILY — which consumers use the listing. -- Review auto-fulfillment refresh activity for the last 30 days

  • SELECT *
  • FROM snowflake.data_sharing_usage.listing_auto_fulfillment_refresh_daily
  • WHERE usage_date >= DATEADD('day', -30, CURRENT_DATE())
  • ORDER BY usage_date DESC;

Cost Attribution & Economic Model

A paramount concept tested on the SnowPro Advanced: Architect exam is the strict demarcation of costs between the data provider and the data consumer in Cross-Cloud Auto-Fulfillment.

Cost Allocation Breakdown ┌────────────────────────────────────────┐ ┌────────────────────────────────────────┐

  • │ PROVIDER EXPENSES │ │ CONSUMER EXPENSES │
  • │ │ │ │
  • │ • Cloud Provider Data Egress │ │ • Virtual Warehouse Compute Credits │
  • │ (Network transfer from source cloud) │ │ (Running queries against local share)│
  • │ • Serverless Replication Credits │ │ │
  • │ (Snapshot deltas & transport) │ │ CONSUMER PAYS ZERO STORAGE FEES │
  • │ • Target Cloud Storage Fees │ │ CONSUMER PAYS ZERO EGRESS FEES │
  • │ (Replicated micro-partitions in │ │ CONSUMER PAYS ZERO REPLICATION FEES │
  • │ each remote fulfillment region) │ │ │
  • └────────────────────────────────────────┘ └────────────────────────────────────────┘
  • Detailed Cost Responsibilities

Cost Component Responsible Party Description & Rationale

Data Egress Charges Provider Network egress charges billed by the primary cloud provider as micro-partitions leave the primary region.

Replication Compute Provider Serverless compute credits consumed by Snowflake's replication engine during scheduled refresh runs.

Target Region Storage Provider Storage for the data product in each remote region's secure share area.

Query Compute Consumer Virtual warehouse credits consumed when querying the shared tables. Queries execute on the consumer's local warehouse.

Architectural Tradeoff: Remote Storage vs. Cross-Region Query Latency

Why does Snowflake duplicate micro-partitions to remote regions instead of executing federated cross-region queries over the network?

Local Query Performance : Because the data product is stored in the consumer's region, the consumer's warehouse reads local storage and gets the same pruning and caching behavior as for local tables.

Elimination of Per-Query Egress : If queries were federated across regions dynamically, every single consumer query would incur high network latency and trigger unpredictable data egress charges. Auto-Fulfillment incurs egress once during scheduled batch syncs.

Architectural Comparison: Sharing & Replication Mechanisms

Architectural Mechanism Use Case Setup Complexity Failover / DR Capable? Cost Model

Direct Secure Data Sharing Intra-region data sharing across accounts in the same cloud and region Minimal ( CREATE SHARE ) No Consumer pays query compute; Provider pays primary storage only

Cross-Cloud Auto-Fulfillment External consumers, Marketplace listings, multi-region SaaS distribution Automated via Listings No Provider pays remote storage, egress, and replication compute; Consumer pays query compute

Failover Groups (DR) Enterprise internal disaster recovery and high availability High (declarative DDL, client redirect) Yes (Supports promotion to primary) Replicating account pays egress, replication compute, and secondary storage

Loading diagram... Cross-Cloud Auto-Fulfillment Flow