You need to design a Bigtable schema to store IoT sensor data with frequent writes and queries by device and time range. Which row key design is best?

hard📝 Application Q8 of 15

GCP - Cloud Firestore and Bigtable

A<code>timestamp#deviceID</code> for natural time ordering

B<code>deviceID#reverseTimestamp</code> to avoid hotspots and enable time range scans

C<code>deviceID#timestamp</code> for simple ordering

D<code>randomUUID</code> for even distribution

Step-by-Step Solution

Solution:

Step 1: Consider write hotspots
Using timestamp prefix causes hotspots; reversing timestamp avoids this.
Step 2: Support time range queries
DeviceID prefix groups data by device; reverse timestamp orders recent data first.
Final Answer:
deviceID#reverseTimestamp to avoid hotspots and enable time range scans -> Option B
Quick Check:
Reverse timestamp + deviceID prefix = A [OK]

Quick Trick: Use reverse timestamps to prevent hotspots [OK]

Common Mistakes:

Using timestamp prefix causing hotspots
Ignoring query patterns
Choosing random keys losing query efficiency

Master "Cloud Firestore and Bigtable" in GCP

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More GCP Quizzes

You need to design a Bigtable schema to store IoT sensor data with frequent writes and queries by device and time range. Which row key design is best?

Step 1: Consider write hotspots

Step 2: Support time range queries

Final Answer:

Quick Check:

Want More Practice?