Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise publishes shared data listings using BigQuery Analytics Hub. A subscriber team in caller project analytics-subscriber (Project R) has subscribed to a listing and provisioned a linked dataset in project subscriber-warehouse (Project L). The underlying shared dataset contains views in project subscriber-warehouse that reference underlying base tables hosted in project source-storage (Project V).
Each project resides in a separate, isolated VPC Service Controls perimeter. Queries executed by analysts in Project R against the linked dataset views are currently failing due to perimeter violations.
Which VPC Service Controls ingress and egress rules must you configure to allow users in Project R to query the views while maintaining perimeter security across all projects?
This configuration establishes a direct two-way bridge between the caller project (Project R) and the linked dataset project (Project L), allowing queries against standard physical tables that reside entirely within Project L.
The query targeted standard BigQuery tables located directly within the linked dataset's shared perimeter rather than views referencing base tables located in an external perimeter project.
VPC Service Controls allows organizations to establish fine-grained security perimeters around Google Cloud resources, including BigQuery Analytics Hub, to prevent data exfiltration. When BigQuery queries span multiple perimeters across caller projects, linked datasets, and underlying source datasets containing base tables, specific directional ingress and egress rules must be defined to bridge perimeter boundaries.
When an analyst queries a view in a linked dataset where the view, caller, and base tables are distributed across separate perimeters:
This configuration accurately aligns with the multi-perimeter architecture rules required by Analytics Hub when views and underlying base tables reside in separate projects and service perimeters.
This configuration attempts to link Project L directly to Project V at the project level, assuming that communication between the linked dataset and the base table project is sufficient for BigQuery queries.
Project R). If Project R does not have explicit egress rules targeting Project L and Project V, the caller cannot initiate jobs against resources across the perimeters.Queries were executed entirely inside Project L by local service accounts without any external calling projects or client tools involved.
This configuration manages communication between the caller project (Project R) and the Data Exchange host project (Project E), which is the perimeter configuration required during the initial listing subscription lifecycle step.
Project L) and the underlying storage (Project V), not the exchange catalog metadata project (Project E).The requirement was specifically to allow users in Project R to discover and subscribe to a new listing hosted on a private data exchange in Project E.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated