nerdexam
Google

ASSOCIATE-CLOUD-ENGINEER · Question #321

The core business of your company is to rent out construction equipment at large scale. All the equipment that is being rented out has been equipped with multiple sensors that send event information e

The correct answer is D. Ingest the data into Bigtable. Create a row key based on the event timestamp.. For high-throughput sensor data with consistent, atomic, time-based retrieval, Bigtable is the ideal choice due to its massive scalability, low-latency access, and suitability for time-series data using appropriately designed row keys.

Submitted by asante_acc· Mar 30, 2026Planning and configuring a cloud solution

Question

The core business of your company is to rent out construction equipment at large scale. All the equipment that is being rented out has been equipped with multiple sensors that send event information every few seconds. These signals can vary from engine status, distance traveled, fuel level, and more. Customers are billed based on the consumption monitored by these sensors. You expect high throughput - up to thousands of events per hour per device - and need to retrieve consistent data based on the time of the event. Storing and retrieving individual signals should be atomic. What should you do?

Options

  • ACreate files in Cloud Storage as data comes in.
  • BCreate a file in Filestore per device, and append new data to that file.
  • CIngest the data into Cloud SQL. Use multiple read replicas to match the throughput.
  • DIngest the data into Bigtable. Create a row key based on the event timestamp.

How the community answered

(17 responses)
  • A
    12% (2)
  • B
    6% (1)
  • C
    29% (5)
  • D
    53% (9)

Why each option

For high-throughput sensor data with consistent, atomic, time-based retrieval, Bigtable is the ideal choice due to its massive scalability, low-latency access, and suitability for time-series data using appropriately designed row keys.

ACreate files in Cloud Storage as data comes in.

Creating individual files in Cloud Storage for every few seconds of data from thousands of devices would lead to an overwhelming number of small files and poor performance for querying or retrieving specific time-based events consistently and atomically.

BCreate a file in Filestore per device, and append new data to that file.

Filestore is a managed file service (NFS), primarily for applications requiring shared file systems, not designed for high-throughput, low-latency individual event ingestion and atomic operations at scale. Appending to files would also lead to contention and poor performance for thousands of concurrent writes.

CIngest the data into Cloud SQL. Use multiple read replicas to match the throughput.

Cloud SQL, while a relational database, would struggle with the extremely high write throughput (thousands of events per hour per device across many devices) and scale of this time-series workload, even with read replicas, as the primary instance would become a bottleneck for writes, and it's not optimized for this type of data ingestion pattern.

DIngest the data into Bigtable. Create a row key based on the event timestamp.Correct

Bigtable is a massively scalable, low-latency NoSQL database ideal for high-throughput time-series data like sensor events. Creating a row key based on the event timestamp (or a combination with device ID) allows for efficient and consistent retrieval of data based on time, while Bigtable's atomic row operations ensure individual signals are stored and retrieved consistently.

Concept tested: Choosing a database for high-throughput time-series data

Source: https://cloud.google.com/bigtable/docs/overview

Topics

#Bigtable#row key design#time-series data#high throughput IoT

Community Discussion

No community discussion yet for this question.

Full ASSOCIATE-CLOUD-ENGINEER Practice