GCP Professional Data Engineer Practice Question

Analytics Hub lets a publisher create a data exchange and add listings that reference BigQuery datasets. When a subscriber accepts a listing, BigQuery automatically creates a read-only linked dataset in the subscriber's project; queries run there without copying data and stay current because the data remains in the publisher project.
To hide the customer_email column, the publisher can expose an authorized view (or apply column-level security) inside the shared dataset. The franchisee only receives access to the view, so the sensitive column is never visible. Granting the franchisee group the analyticshub.subscriber role on the exchange lets them subscribe to the listing.
The other options copy data out of the publisher project or rely on manual transfers, which break the publisher-subscriber pattern and increase operational overhead.