Answer-first summary for fast verification
Answer: The UUID type selected generates sequentially ordered strings.
The correct answer is D because using a UUID that generates sequentially ordered strings can lead to hot-spotting. Opting for UUID version 4, which utilizes a random number generator, is recommended. Issues such as the length of the row key column's name, column families configuration, or the presence of secondary indexes do not contribute to hot-spotting. For more details, refer to [Google Cloud's Bigtable documentation](https://cloud.google.com/bigtable/docs/performance).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Despite designing a row key with a UUID prefix to prevent hot-spotting in your Bigtable clusters, you're experiencing unexpected hot-spotting during data writes. What might be the underlying issue?
A
The row key column's name is excessively long.
B
Incorrect configuration of column families.
C
Write operations are being slowed down by secondary indexes.
D
The UUID type selected generates sequentially ordered strings.
No comments yet.