
Ultimate access to all questions.
An IoT service utilizes Bigtable for storing timeseries data. However, it's observed that write operations are predominantly occurring on a single node instead of being uniformly distributed across all nodes. What might be the underlying cause of this issue?
A
Incorrect configuration of replication
B
Employing an excessive number of columns in your data schema
C
Selection of an inappropriate GCP load balancer type preceding Bigtable
D
Utilization of a row key that results in temporally proximate data being directed to a single node, rather than being evenly spread out