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 financial analytics firm is building an event-driven data ingestion pipeline. Whenever transaction batch files are uploaded to a Cloud Storage bucket, the system must immediately trigger an orchestration process that:
404 Not Found) and retries transient service faults with backoff, while raising unhandled exceptions.The organization requires a fully serverless, low-latency solution that minimizes operational management and isolates orchestration logic from business logic.
Which architecture should the data engineering team implement to meet these requirements?
GCSObjectsWithPrefixExistenceSensor to poll the bucket, triggering Cloud Run and Firestore using custom Python operators and Airflow retries.Cloud Composer is a fully managed workflow orchestration service built on Apache Airflow, primarily utilized for complex, scheduled batch ETL/ELT data pipelines across enterprise data ecosystems.
The workload consisted of complex, multi-hour batch data transformations and distributed Hadoop/Spark jobs that run on scheduled intervals with rich dependency graphs.
Cloud Run worker pools are compute instances tailored for continuous, non-HTTP, pull-based background processing (such as consuming continuous streaming events from Apache Kafka).
minInstances >= 1) to run; setting minimum instances to 0 prevents worker instances from starting.You were deploying continuous, non-HTTP background consumers for streaming message brokers like Apache Kafka where instances remain continuously active.
Application Integration is an Integration Platform as a Service (iPaaS) solution focused on enterprise application integration (EAI), point-to-point business data mapping, and SaaS connectivity (e.g., connecting Salesforce, ServiceNow, and ERP systems).
The pipeline required connecting Google Cloud services to third-party enterprise CRM/ERP SaaS platforms with visual data transformation mappings.
google.cloud.storage.object.v1.finalized events that routes directly to a Google Cloud Workflows definition, using built-in Google APIs connectors with try/except and switch blocks in YAML.Google Cloud Workflows combined with Eventarc provides a fully managed, serverless orchestration framework specifically designed for low-latency, event-driven microservice and API coordination. The orchestration state machine is declared in YAML or JSON, allowing developers to sequence services, manage states, and implement custom error-handling logic.
google.cloud.storage.object.v1.finalized event directly from Cloud Storage and routes it to the target workflow within milliseconds, executing the pipeline on demand without polling delays.googleapis.firestore.v1 and googleapis.run.v1), which handle authentication, request formatting, and API interaction natively.try/except constructs, conditional switch branching, and automated retry policies with exponential backoff directly within the YAML specification.e.code == 404) and dynamically directs the execution path or halts with custom messages.Unlike container-based orchestrators that introduce node provisioning latency or batch-oriented workflow tools, Google Cloud Workflows starts immediately upon receiving the Eventarc trigger, providing sub-second invocation times and native connector support for Google Cloud APIs.
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