Snowflake database replication incurs costs associated with transferring changed data and performing replication operations. These expenses are attributed to the target account containing the secondary database.
Option B is correct because the volume of modified table data affects the amount of information that must be synchronized. Large INSERT, UPDATE, DELETE, and data-loading operations can increase replication activity and its associated charges.
Option C is correct because the secondary database's refresh frequency influences the overall replication workload. More frequent synchronization can create additional replication processing and transfer activity.
Snowflake explicitly identifies changed data volume and refresh frequency as the principal variables influencing monthly replication charges.
Option A concerns the frequency of individual source modifications rather than the documented billing dimensions. Numerous small changes and a smaller number of large changes can produce very different replication volumes.
Option D describes aspects of cross-region data movement, which can affect transfer pricing, but it is not the general cost-driver formulation requested by the question.
Option E is incorrect because replication is performed using Snowflake-managed resources rather than the primary account's virtual warehouse configuration.
Current-version qualification: Snowflake now documents multiple replication billing modes, including Replication Classic, Optimized Refresh, and RPO Assurance. Their compute charging models differ, but replicated data volume and refresh behavior remain important cost considerations.
Official Snowflake references: Understanding Replication Cost: Estimating and Controlling Costs.
Submit