Snowflake database replication synchronizes supported database objects and data between the primary and secondary accounts. However, it does not replicate every database-level configuration parameter.
Option A is correct because the DATA_RETENTION_TIME_IN_DAYS parameter can be configured independently at the secondary database level.
Snowflake explicitly documents that database-level parameter settings on secondary databases are not overwritten by replication refreshes from the primary database.
For example, an appropriately authorized administrator can configure:
ALTER DATABASE APP_DB
SET DATA_RETENTION_TIME_IN_DAYS = 60;
This establishes a 60-day database-level retention setting on the secondary while leaving the primary database's 30-day setting unchanged.
Option B is unsuitable because schema-level parameters explicitly configured on the primary database can be replicated and overwrite the corresponding secondary schema settings.
Option C changes the primary configuration and does not meet the requirement to extend retention only on the secondary.
Option D changes the primary database's retention rather than the secondary's.
Both accounts use Enterprise Edition, which permits Time Travel retention of up to 90 days for permanent objects.
Technical qualification: If APP_SCHEMA or its tables already have an explicitly configured 30-day retention period, changing the secondary database default does not automatically override those settings. Such inherited and explicitly replicated parameters must be examined before claiming that every table will retain 60 days of history. Increasing retention also cannot recover historical versions already purged.
Official Snowflake references: Introduction to Database Replication Across Multiple Accounts — Parameters; ALTER DATABASE; Understanding & Using Time Travel.