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 is architecting an enterprise data platform on Google Cloud to ingest both real-time clickstream events and daily batch transactional files from acquired entities. The platform design must satisfy the following technical requirements:
Which architectural approach satisfies all of these requirements while adhering to Google Cloud best practices?
This option relies on BigQuery Data Transfer Service for ingestion, native BigQuery scheduled queries for transformations, custom-built quality validation scripts hosted on Google Kubernetes Engine (GKE), and scheduled bq CLI scripts for object deletion.
The scenario required simple, periodic scheduled batch migrations of external SaaS or database tables directly into BigQuery without streaming or deep transformation needs.
This architecture combines Dataflow for unified stream/batch data processing, Cloud Composer for workflow orchestration, Dataplex for decentralized data governance and automated quality validation, and native BigQuery and Cloud Storage lifecycle management policies for compliance and data retention.
This approach aligns with Google Cloud reference architectures for enterprise data platforms, ensuring scalability, low operational overhead, robust data governance, and automated lifecycle compliance.
This configuration proposes running Dataproc (Apache Spark) clusters for data processing, using Vertex AI Pipelines for enterprise orchestration, relying on BigQuery table clones for quality validation, and using BigQuery object tables for partition archival.
The workload focused strictly on orchestrating Machine Learning training experiments and model evaluations using containerized components.
This option uses Datastream for ingestion, Dataform for transformations and pipeline orchestration, BigQuery sharing (Analytics Hub) for data cataloging, and Cloud KMS key destruction/revocation as a data lifecycle mechanism.
The workload primarily consisted of replicating relational database tables into BigQuery and modeling SQL transformations inside the data warehouse.
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