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 ingestion pipeline processes streaming transactional data that is staged in Cloud Storage before undergoing complex transformations orchestrated by Cloud Composer. Recent schema deviations and malformed payloads have corrupted downstream analytics tables, leading to pipeline halts and unrecoverable data.
You need to architect an automated recovery and reprocessing workflow that satisfies the following operational requirements:
Which architecture should you implement?
This architecture combines Google Cloud Pub/Sub dead-letter topics (DLTs), Cloud Storage Object Versioning, and managed Apache Airflow orchestration via Cloud Composer deployed through secure continuous integration and delivery (CI/CD) pipelines.
This option uses attribute-based Pub/Sub message filtering to discard non-matching payloads, relies on Cloud Storage soft delete, and allows manual editing of DAGs directly in the environment's Cloud Storage bucket by engineers.
Unparseable data could be safely discarded without audit requirements and manual ad-hoc operational fixes were explicitly mandated.
This solution introduces an AlloyDB Omni relational database deployment to capture streaming transactions, relies on PostgreSQL continuous WAL archiving for point-in-time recovery, and uses manual script execution from Cloud Shell.
pg_restore scripts fails the requirement for automated orchestration using tools like Cloud Composer.The primary architecture was centered on an on-premises or containerized PostgreSQL/AlloyDB Omni database needing database point-in-time recovery (PITR) following physical host failure.
This approach relies solely on native subscriber retries with exponential backoff for streaming messages, applies bucket Retention Locks (WORM compliance) to protect storage objects, and has Cloud Composer DAGs directly read the underlying Airflow metadata database for state tracking.
The scenario required immutable compliance storage (WORM) and simple transient network error retry handling rather than bad data isolation and automated reprocessing.
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