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.
A retail enterprise wants to establish a decentralized data-sharing architecture to publish curated demand-forecasting datasets and file assets to hundreds of vendor partners and internal domain teams. The data architecture team needs to implement a solution that fulfills the following operational and financial requirements:
Which combination of Google Cloud services and configurations should the enterprise implement?
This option creates authorized views directly inside the publisher's BigQuery project and provisions a dedicated flat-rate slot reservation in that same publisher project to handle all incoming queries from consumer accounts.
The publisher wanted to fully sponsor and cap all external compute costs centrally using a dedicated, isolated slot pool without requiring consumers to manage their own Google Cloud billing accounts.
This architecture combines Dataplex Universal Catalog for centralized metadata management and asset discovery with BigQuery sharing (Analytics Hub) listings and Requester Pays Cloud Storage buckets to enforce zero-copy data publishing and subscriber-funded compute.
This approach aligns with Google Cloud data mesh best practices by separating data storage from analytical compute, providing robust discovery, and automating cost attribution across organizational boundaries.
This approach defines BigLake external tables pointing to raw Cloud Storage objects and grants consumers direct Storage Object Viewer permissions on the source storage bucket without using a formal catalog or data exchange mechanism.
The goal was simply to allow internal developers temporary, direct file-level read access to unstructured bucket objects without a managed data product catalog.
This approach uses automated Dataflow ETL/ELT pipelines to extract data from publisher storage repositories and write distinct physical copies of datasets into every subscribing consumer's project.
Subscribers required fully disconnected, editable local copies of historical data snapshots that needed to operate in complete isolation from the upstream publisher environment.
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