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 analytics team needs to automate a recurring multi-step extract, transform, and load (ETL) pipeline across multiple disparate systems. The pipeline has the following requirements:
Which Google Cloud orchestration solution should the team choose to meet these requirements?
BigQuery Scheduled Queries is a native feature within BigQuery that allows users to automate the recurring execution of SQL queries on a predefined schedule (such as hourly, daily, or custom intervals) without provisioning external infrastructure.
The scenario required a simple, serverless way to run a recurring SQL transformation query to aggregate daily sales tables directly inside BigQuery without any external system dependencies or custom Python code.
Cloud Composer is a fully managed data workflow orchestration service built on the open-source Apache Airflow platform. It provides organizations with an enterprise-grade environment to author, schedule, coordinate, and monitor complex data pipelines across hybrid and multi-cloud environments using pure Python code.
Cloud Composer is the ideal choice when business requirements dictate high integration complexity, complex task dependencies, Python-based workflow definition, and multi-system data pipeline management across diverse operational environments.
Dataproc Workflow Templates provide a lightweight mechanism for orchestrating sequences of Apache Spark, PySpark, Apache Hive, Apache Hadoop, or Presto jobs on Google Cloud Dataproc clusters, handling automated cluster lifecycle management.
The requirement specifically called for running a sequence of Spark and PySpark jobs on an ephemeral Dataproc cluster with automated cluster creation and tear-down to optimize infrastructure costs.
Workflows is a fully managed, serverless orchestration platform that links Google Cloud services and external HTTP-based APIs together in an execution order defined in YAML or JSON format.
The scenario described an event-driven, low-latency microservices pipeline coordinating serverless HTTP endpoints and Cloud Functions using a lightweight YAML-defined workflow with minimal execution cost.
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