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 e-commerce platform requires a real-time event processing architecture on Google Cloud to detect fraudulent transactions and personalize user experiences. The technical architecture must meet the following specifications:
Which combination of Google Cloud services and Dataflow streaming pipeline configurations should you implement?
This pattern utilizes Cloud Datastream for message ingestion, static side inputs loaded from Cloud Storage at worker boot time, session windows, and a relational Cloud SQL database instance for serving.
You were migrating transaction logs from an external relational database into a centralized PostgreSQL warehouse with bounded reference lookup datasets.
This architecture combines Cloud Pub/Sub, Cloud Dataflow, and Cloud Bigtable to construct an end-to-end, horizontally scalable, low-latency streaming pipeline that natively manages out-of-order records, real-time enrichment, and windowed analytics.
Enrichment transform combined with the BigTableEnrichmentHandler performs point lookups against Cloud Bigtable. It includes built-in client-side throttling and exponential backoff to avoid overwhelming the database cluster.BigtableIO provides sub-10ms read/write response times required by high-concurrency real-time web applications.Enrichment transform natively manages throughput and rate limits against Bigtable.BigtableIO enables parallelized batch mutations directly into Bigtable tablets.This architecture completely satisfies the low-latency serving SLA (via Bigtable) and operational simplicity requirements (via Pub/Sub and Dataflow turnkey transforms) while preserving analytical accuracy across out-of-order distributed event streams.
This design uses Cloud Pub/Sub for ingestion, custom synchronous database calls inside a standard ParDo transform without rate limiting, global windowing, and an analytical lakehouse destination (Cloud Storage with BigLake Iceberg tables).
ParDo without client-side throttling or exponential backoff causes connection exhaustion and hot-spotting on the Bigtable cluster.The workload were an offline batch ingestion pipeline populating an open-format data lake where analytical queries are executed via SQL engines like BigQuery or Spark.
This approach relies on Managed Service for Apache Kafka, per-element federated BigQuery SQL queries for data enrichment, fixed tumbling windows that drop late data, and BigQuery as the serving sink.
The pipeline were designed for periodic batch reporting or analytical dashboards where data latency of minutes is acceptable and Kafka ecosystem compatibility is mandatory.
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