Question 250
A database team reports a successful correction for this problem: A TimeSeries Bigtable workload uses only a leading timestamp in its row key and struggles at high ingestion rates. What evidence supports closing the incident?
Explanation
Correct Answer
Peak writes distribute across tablets while key-range retrieval remains workable. The observed state validates the proposed fix: Combine appropriate identifying or salted prefixes with temporal ordering for the required reads. It addresses this cause: The sequential row-key pattern creates write hotspots despite available cluster capacity.
Incorrect Answers
This finding belongs with a situation in which a gaming service requires atomic updates to many related entities but proposes distributing them across independent Bigtable rows. The required acceptance finding here is that peak writes distribute across tablets while key-range retrieval remains workable.
This finding belongs with a situation in which a high-throughput PostgreSQL-compatible analytics-heavy transactional application needs a managed service optimized for demanding reads. The required acceptance finding here is that peak writes distribute across tablets while key-range retrieval remains workable.
This finding belongs with a situation in which an application proposes storing high-dimensional embeddings in a small PostgreSQL instance without sizing index memory. The required acceptance finding here is that peak writes distribute across tablets while key-range retrieval remains workable.