professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Ingest data directly using the BigQuery Data Transfer Service; orchestrate transformations using BigQuery scheduled queries; run custom Python scripts on Google Kubernetes Engine for data quality scans; manage lifecycle policies via scheduled cron jobs running bq CLI delete commands.
Ingest real-time and batch streams using Dataflow with dead-letter branching; orchestrate batch workflows with Cloud Composer; organize distributed assets using Dataplex data lakes and zones with auto data quality enabled; configure partition and table expiration in BigQuery alongside Cloud Storage lifecycle rules.
Ingest and process all records using Dataproc Spark jobs; orchestrate workflows with Vertex AI Pipelines; validate quality by creating BigQuery table clones; archive expired data by moving old partitions into BigQuery object tables.
Ingest clickstream events with Datastream directly into Cloud Storage; use Dataform to orchestrate batch and stream transformations; catalog assets in BigQuery sharing data exchanges; apply Cloud KMS key revocation after 90 days to retire expired datasets.
Ingest data directly using the BigQuery Data Transfer Service; orchestrate transformations using BigQuery scheduled queries; run custom Python scripts on Google Kubernetes Engine for data quality scans; manage lifecycle policies via scheduled cron jobs running bq CLI delete commands.
Ingest real-time and batch streams using Dataflow with dead-letter branching; orchestrate batch workflows with Cloud Composer; organize distributed assets using Dataplex data lakes and zones with auto data quality enabled; configure partition and table expiration in BigQuery alongside Cloud Storage lifecycle rules.
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.
Ingest and process all records using Dataproc Spark jobs; orchestrate workflows with Vertex AI Pipelines; validate quality by creating BigQuery table clones; archive expired data by moving old partitions into BigQuery object tables.
Ingest clickstream events with Datastream directly into Cloud Storage; use Dataform to orchestrate batch and stream transformations; catalog assets in BigQuery sharing data exchanges; apply Cloud KMS key revocation after 90 days to retire expired datasets.