Question

A data provider wants to share a curated subset of a large customer transactions table with a consumer account in the same region. The provider must ensure that consumers cannot see the underlying table structure or query columns that were excluded, and that no data is physically copied to the consumer. Which approach correctly satisfies all of these requirements when adding objects to a share?

Accepted Answer

Create a secure view that selects only the required columns and rows, then grant SELECT on that secure view to the share

Answer

Add the base transactions table directly to the share and rely on column-level masking policies to hide excluded columns

Answer

Create a materialized view over the transactions table and add the materialized view to the share so results are precomputed

Answer

Clone the transactions table into the consumer's account and grant SELECT on the cloned copy