SnowPro Advanced: Administrator free question 9 / 10 · Domain 5: Data Sharing and Snowflake Marketplace
A provider administrator ran DROP SHARE on SALES_S by mistake. They immediately recreated SALES_S with the same name and granted the same object privileges and the same consumer accounts again. Which statement about the databases consumers had created from the original SALES_S matches the documentation?
- The recreated share is a new share, and each consumer must create a new database from it
- The consumer databases remain for a period, and recreating the share within it keeps them readable as before
- The consumer databases are invalidated, but ALTER DATABASE ... REFRESH reconnects them to the recreated share
- Because the name is the same, the consumer databases become readable again once the grants are restored
Show the answer and explanation
Answer: A
Why this is correct
Dropping a share instantly invalidates all databases created from the share by consumer accounts, and all queries and other operations on those databases no longer work. The documentation says you can recreate the share with the same name afterward, but this does not restore any of the databases created from it. The recreated share is treated as a new share, and all consumer accounts must create a new database from the new share.
Why the other options are wrong
"Because the name is the same, the consumer databases become readable again once the grants are restored" … Even with the same name, the recreated share is a new share. Databases created from the original share were invalidated at the drop, and restoring grants does not bring them back.
"The consumer databases are invalidated, but ALTER DATABASE ... REFRESH reconnects them to the recreated share" … The databases are invalidated, but the documented way forward is not a refresh. The recreated share is treated as a new share, and every consumer account must create a new database from it.
"The consumer databases remain for a period, and recreating the share within it keeps them readable as before" … Dropping a share instantly invalidates the consumer databases. Recreating the share afterward, however quickly, does not restore them.
Design tip
A share can be dropped at any time, but doing so stops consumers' queries and other operations right away, which can disrupt their work. Before dropping a share, consider the downstream impact on every consumer account that uses it.