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 data platform receives real-time transaction events via Pub/Sub and writes them directly into BigQuery using a BigQuery subscription with use_topic_schema enabled. To implement strict data contract governance across upstream producers and analytical downstream tables, the engineering team must satisfy the following architectural requirements:
Which architectural configuration should the team implement?
This solution establishes an end-to-end data contract by binding an Apache Avro or Protocol Buffer schema directly to a Pub/Sub topic, enforcing structural validation at the ingestion boundary while leveraging native BigQuery subscription schema compatibility and dead-letter topics for deterministic failure handling.
use_topic_schema is set on a BigQuery subscription, Pub/Sub checks compatibility with the BigQuery table schema. String fields mapped to TIMESTAMP, DATETIME, DATE, TIME, NUMERIC, or BIGNUMERIC columns must adhere strictly to BigQuery formatting rules; otherwise, BigQuery refuses the row.CloudPubSubDeadLetterSourceDeliveryErrorMessage attribute, providing the exact reason the message failed to load into BigQuery.This architecture enforces contract boundaries natively across serverless Google Cloud services without provisioning intermediate compute clusters, ensuring strict schema governance and automated dead-letter forensics.
BigQuery time travel provides access to data stored in BigQuery from any point within the past seven days, while table snapshots create point-in-time, read-only copies of tables for long-term backup and recovery against human errors.
use_table_schema expects incoming JSON messages to align with BigQuery fields, but without a dead-letter topic, delivery failures stall processing.An operator accidentally ran an unintended UPDATE or DELETE statement on a curated BigQuery table and needed to restore historical data beyond standard undo operations.
AEAD encryption functions in BigQuery use cryptographic keysets to encrypt and decrypt individual cell values at the column level. Cloud KMS audit logs track administrative operations and cryptographic key usage requests.
The scenario required client-side column encryption using Tink keysets to ensure that analysts without specific decryption keys could not view sensitive plaintext data in BigQuery.
Data Catalog tag templates allow organizations to attach business, technical, or governance metadata tags to assets like tables and columns. Query labels attach key-value session metadata to SQL queries for cost tracking, auditing, and entitlement tracking.
You needed to document business ownership, track data sharing agreements under compliance frameworks like CDMC, or monitor user query purposes in BigQuery audit logs.
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