Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A logistics company is modernizing its data analytics architecture on Google Cloud to track its delivery fleet. The company has defined the following requirements for its data pipeline:
Which data ingestion and transformation approach should the company implement?
Federation to external data sources is a data access method that allows BigQuery to run SQL queries directly against data stored in external repositories—such as Cloud Storage, Cloud Spanner, or Cloud SQL—without physically loading the data into native BigQuery storage first.
SELECT statements over external Cloud Storage files consumes BigQuery compute resources during query execution and generally yields slower query performance than querying native BigQuery tables.SELECT query.This option would be appropriate if the company had archival log files sitting in Cloud Storage that data analysts needed to inspect occasionally using SQL without building a dedicated ingestion pipeline to load the data into BigQuery.
Federated queries are useful for ad hoc data exploration and rapid prototyping, whereas high-throughput streaming analytics and high-concurrency BI dashboards require dedicated ingestion and transformation pipelines that land structured data into native BigQuery tables.
A batch Extract, Load, and Transform (ELT) pipeline is a data integration method that collects data over a specific period, transfers the raw data into a data warehouse on a recurring schedule, and then uses the data warehouse's internal compute engine to execute SQL transformations. In Google Cloud, BigQuery Data Transfer Service automates scheduled batch loads, while Dataform orchestrates SQL-based table transformations inside BigQuery.
This option would be the ideal choice if the company wanted to upload daily summary files of completed delivery routes every night and have data analysts use SQL inside BigQuery during off-peak hours to transform the raw records.
While ELT is widely recommended for standard cloud data warehousing due to its simplicity and ability to scale within BigQuery, organizations with strict real-time streaming preprocessing needs or tight warehouse resource isolation requirements rely on ETL with Dataflow instead.
A streaming Extract, Transform, and Load (ETL) pipeline is a data integration architecture that continuously ingests real-time event data, processes and reshapes that data in flight using an external processing engine, and writes the refined output into a target data warehouse. On Google Cloud, this pattern is commonly implemented by combining Pub/Sub for real-time message ingestion with Dataflow for serverless stream processing before loading the results into BigQuery.
Unlike batch ingestion, which introduces delays by waiting to accumulate data over scheduled intervals, streaming ingestion provides immediate visibility into fleet operations. Furthermore, choosing ETL over Extract, Load, and Transform (ELT) directly satisfies the requirement to prevent transformation workloads from competing with concurrent BigQuery reporting queries.
Reverse ETL is a downstream data integration process that extracts processed, analytical data out of a central data warehouse like BigQuery and exports it into external operational systems—such as Customer Relationship Management (CRM) platforms, relational databases, or cloud storage buckets—so business teams can act on insights. Batch load jobs, conversely, are scheduled or one-time operations that import static files (like CSV, JSON, or Parquet) into BigQuery.
This approach would be suitable if the company had already completed its analysis in BigQuery and needed to export calculated delivery pricing or route adjustments back into an operational Product Catalog Management (PCM) or dispatch database on a daily schedule.
In the data value chain, ETL and ELT are upstream processes that bring raw data from source systems into the data warehouse, whereas Reverse ETL (often used in operational feedback loops) is a downstream process that pushes warehouse insights back into operational environments.
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