nerdexam
Google

PROFESSIONAL-DATA-ENGINEER · Question #235

You work for a global shipping company. You want to train a model on 40 TB of data to predict which ships in each geographic region are likely to cause delivery delays on any given day. The model will

The correct answer is A. BigQuery. BigQuery is the right choice because it natively integrates with BigQuery ML (for training and running predictions at scale on 40 TB+ datasets) and has built-in geospatial functions (via ST_ functions for GeoJSON/geography types) - covering both requirements in a single managed s

Submitted by femi9· Mar 30, 2026Designing data processing systems

Question

You work for a global shipping company. You want to train a model on 40 TB of data to predict which ships in each geographic region are likely to cause delivery delays on any given day. The model will be based on multiple attributes collected from multiple sources. Telemetry data, including location in GeoJSON format, will be pulled from each ship and loaded every hour. You want to have a dashboard that shows how many and which ships are likely to cause delays within a region. You want to use a storage solution that has native functionality for prediction and geospatial processing. Which storage solution should you use?

Options

  • ABigQuery
  • BCloud Bigtable
  • CCloud Datastore
  • DCloud SQL for PostgreSQL

How the community answered

(23 responses)
  • A
    70% (16)
  • B
    9% (2)
  • C
    4% (1)
  • D
    17% (4)

Explanation

BigQuery is the right choice because it natively integrates with BigQuery ML (for training and running predictions at scale on 40 TB+ datasets) and has built-in geospatial functions (via ST_* functions for GeoJSON/geography types) - covering both requirements in a single managed service designed for analytical workloads.

Cloud Bigtable (B) is a high-throughput NoSQL store great for time-series and IoT telemetry ingestion, but it has no native ML or geospatial processing - you'd need to move data elsewhere to do predictions.

Cloud Datastore (C) is a transactional NoSQL document database suited for small-to-medium operational data; it scales poorly to 40 TB analytical workloads and lacks ML or geospatial capabilities.

Cloud SQL for PostgreSQL (D) supports PostGIS for geospatial queries, but it is an OLTP database not designed for petabyte-scale analytics or native ML model training, making it the wrong fit for this scale.

Memory tip: Think "BigQuery = Big Analytics + BigQuery ML + Big Geospatial." Whenever an exam question combines large-scale data, ML predictions, and geospatial processing in one sentence, BigQuery is almost always the answer.

Topics

#BigQuery#Geospatial Processing#Machine Learning#Data Warehousing

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-DATA-ENGINEER Practice