According to the SnowPro Advanced: Architect documents and learning resources, the ways that
Snowflake databases that are created from shares differ from standard databases that are not
created from shares are:
Shared databases are read-only. This means that the data consumers who access the shared
databases cannot modify or delete the data or the objects in the databases. The data providers who
share the databases have full control over the data and the objects, and can grant or revoke
privileges on them1.
Shared databases cannot be cloned. This means that the data consumers who access the shared
databases cannot create a copy of the databases or the objects in the databases. The data providers
who share the databases can clone the databases or the objects, but the clones are not automatically
shared2.
Shared databases are not supported by Time Travel. This means that the data consumers who access
the shared databases cannot use the AS OF clause to query historical data or restore deleted
data. The data providers who share the databases can use Time Travel on the databases or the
objects, but the historical data is not visible to the data consumers3.
The other options are incorrect because they are not ways that Snowflake databases that are created
from shares differ from standard databases that are not created from shares. Option B is incorrect
because shared databases do not need to be refreshed in order for new data to be visible. The data
consumers who access the shared databases can see the latest data as soon as the data providers
update the data1. Option E is incorrect because shared databases will not have the PUBLIC or
INFORMATION_SCHEMA schemas without explicitly granting these schemas to the share. The data
consumers who access the shared databases can only see the objects that the data providers grant to
the share, and the PUBLIC and INFORMATION_SCHEMA schemas are not granted by default4. Option
F is incorrect because shared databases cannot be created as transient databases. Transient
databases are databases that do not support Time Travel or Fail-safe, and can be dropped without
affecting the retention period of the data. Shared databases are always created as permanent
databases, regardless of the type of the source database5. Reference: Introduction to Secure Data
Sharing | Snowflake Documentation, Cloning Objects | Snowflake Documentation, Time Travel |
Snowflake Documentation, Working with Shares | Snowflake Documentation, CREATE DATABASE |
Snowflake Documentation