You designed a data warehouse in BigQuery to analyze sales data. You want a self-serving, low-maintenance, and cost- effective solution to share the sales dataset to other business units in your…

Question

Options

• ACreate an Analytics Hub private exchange, and publish the sales dataset.
• BEnable the other business units' projects to access the authorized views of the sales dataset.
• CCreate and share views with the users in the other business units.
• DUse the BigQuery Data Transfer Service to create a schedule that copies the sales dataset to the other business units' projects.

• A
  79% (46)
• B
  5% (3)
• C
  12% (7)
• D
  3% (2)

Explanation

Analytics Hub private exchange is purpose-built for exactly this scenario - it lets business units self-discover and subscribe to published datasets without requiring the data owner to manually grant access each time. Subscribers query the source data directly (no copying), keeping costs low and data always current, which makes it low-maintenance by design.

Why the distractors fail:

• B (Authorized views): Authorized views are a valid security pattern but require the admin to manually create and authorize each view per project - not self-serving, and grows in maintenance as units are added.
• C (Shared views): Similar problem to B - granting view access to individual users or projects is a manual, per-user process that doesn't scale and requires ongoing management.
• D (Data Transfer Service): Physically copies data to each business unit's project, which duplicates storage costs and introduces data freshness lag - the opposite of cost-effective and low-maintenance.

Memory tip: Think of Analytics Hub as an internal "data marketplace." The publisher lists the dataset once; consumers browse the catalog and subscribe themselves - no ticket to IT required. If a question mentions self-service + low-maintenance + sharing across org boundaries in BigQuery, Analytics Hub is almost always the answer.

No community discussion yet for this question.