A developer designed a Bigtable schema with row keys as userID#sessionID. They notice uneven tablet sizes. What is a likely schema design issue?

medium📝 Debug Q7 of 15

GCP - Cloud Firestore and Bigtable

A developer designed a Bigtable schema with row keys as userID#sessionID. They notice uneven tablet sizes. What is a likely schema design issue?

AColumn families are missing

BSessionID is random, causing uneven data distribution

CUserID is too long

DTimestamps are not included

Step-by-Step Solution

Solution:

Step 1: Understand row key components
SessionID is likely random, causing scattered writes.
Step 2: Recognize uneven tablet sizes
Random sessionIDs cause uneven data distribution across tablets.
Final Answer:
SessionID is random, causing uneven data distribution -> Option B
Quick Check:
Random key parts cause uneven tablets = C [OK]

Quick Trick: Avoid random parts early in row keys [OK]

Common Mistakes:

Master "Cloud Firestore and Bigtable" in GCP

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More GCP Quizzes