Question 790
A database team wants evidence that it fixed this issue: A Bigtable schema stores all meter readings under a single row key and update contention rises as ingestion expands. Which result would verify success?
Explanation
Correct Answer
Concurrent meter writes scale without one oversized hot row. The observed state validates the proposed fix: Redesign the row-key and column-family layout for device-level distribution and required reads. It addresses this cause: Data modeling concentrates independent time series into one logical row.
Incorrect Answers
This finding relates to a situation in which a multinational application needs continued transactional availability after one region fails but its Spanner database was deployed regionally. The current remediation must instead show that concurrent meter writes scale without one oversized hot row.
This finding belongs with a situation in which a Spanner table uses increasing integer identifiers and write throughput collapses as a hot key range forms. The required acceptance finding here is that concurrent meter writes scale without one oversized hot row.
Even if this observation were recorded, it would support a case where a deployment service account holds broad project edit privileges because it needs to create one managed database instance. It would not verify that concurrent meter writes scale without one oversized hot row.