Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data engineering team runs batch Dataflow pipelines to process daily analytics data. They want to implement an automated, event-driven architecture that invokes a containerized application hosted on Cloud Run whenever a Dataflow job changes state (such as completing or failing) to perform post-processing cleanup and logging. The Cloud Run target requires authenticated requests.
How should the team configure the pipeline trigger to satisfy these requirements?
Cloud SQL is a fully managed relational database service (MySQL, PostgreSQL, SQL Server) built for transactional workloads (OLTP). It is a database storage engine, not an event-receiving compute endpoint.
The requirement involved database provisioning and schema administration where an administrative user needed complete control over Cloud SQL instance configurations.
This configuration listens for object-level changes inside Cloud Storage buckets (such as google.cloud.storage.object.v1.finalized or deleted) and routes those storage events to downstream destinations like Cloud Run.
roles/pubsub.publisher) role allows publishing messages to Pub/Sub topics, but it does not grant Eventarc the required authorization to invoke an authenticated Cloud Run service.roles/run.invoker) role to the trigger's service account, authenticated Cloud Run invocations will fail with permission errors.The scenario required initiating a data pipeline automatically upon the arrival of a new raw data file uploaded to a Cloud Storage bucket rather than reacting to a Dataflow job's termination.
Eventarc is a fully managed Google Cloud eventing service that captures events from Google Cloud sources, custom applications, or third-party platforms and routes them asynchronously to specified targets. When integrated with Cloud Dataflow, Eventarc captures state changes (such as JOB_STATE_DONE, JOB_STATE_FAILED, or JOB_STATE_RUNNING) as direct event notifications without requiring custom polling scripts or complex manual notification channels.
roles/run.invoker) role via the --service-account parameter.
Using Eventarc to directly bind Dataflow state transitions to an authenticated Cloud Run service represents Google Cloud's recommended architectural pattern for event-driven orchestration. It decouples the data processing engine from downstream reporting and maintenance systems, providing a resilient, secure, and low-latency solution.
Cloud Scheduler is a fully managed enterprise cron job service that triggers recurring tasks at predetermined intervals (such as every 5 minutes or hourly) over HTTP/S endpoints, Pub/Sub topics, or App Engine applications.
roles/dataflow.admin) role gives full control over Dataflow pipelines, violating the principle of least privilege when only invocation of a Cloud Run service is required.roles/run.invoker) is specifically required to trigger authenticated Cloud Run services, not Dataflow administration roles.The scenario required recurring batch processing initiated at fixed calendar times (e.g., triggering a maintenance job every Sunday at midnight) rather than reacting dynamically to job lifecycle state transitions.
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