A logistics firm wants three carriers to read a curated subset of its shipment tables. Each carrier should see only its own shipments, the firm must be able to revoke a carrier's access immediately, and no data should be copied into the carriers' environments. Which solution should the firm use?
Show answer and explanation
Answer: C
Analytics Hub lets a publisher share BigQuery data as listings that subscribers query in place, without copying data out of the publisher's project. Listings can be built on authorized views or datasets that filter rows and columns, so each carrier sees only its slice. The publisher can remove a subscription or change the listing to revoke access, and that change takes effect without moving any data. Exports and per-carrier copies create duplicates that cannot be recalled. Direct database access through a VPN ignores least privilege, since each carrier would reach far more than its own data.
Why the other options are wrong
- A. CSV exports leave copies on the recipients' side that the firm cannot retract, and they are refreshed only when someone reruns the job. This fails the requirement for immediate revocation.
- B. Separate projects with full copies multiply storage and create drifting duplicates of the data. Revoking access would mean deleting those copies, and each carrier would still hold more than its slice.
- D. A VPN login to production relies on database roles rather than a shareable curated layer, and it grants network reach into the production system. It does not follow least privilege and still needs carrier-specific restrictions.