Exam Professional Cloud Architect topic 1 question 178 discussion

Option-C is correct: https://cloud.google.com/bigtable/docs/schema-design#row-keys

C. Review your RowKey strategy and ensure that keys are evenly spread across the alphabet. The RowKey is used to sort data within a Cloud Bigtable cluster. If the keys are not evenly spread across the alphabet, it can result in a hotspot and slow down queries. To prevent this from happening in the future, you should review your RowKey strategy and ensure that keys are evenly spread across the alphabet. This will help to distribute the data evenly across the cluster and improve query performance. Other potential solutions to consider include adding more nodes to the cluster or optimizing your query patterns. However, deleting records older than 30 days or advising clients to use HBase APIs instead of NodeJS APIs would not address the issue of a hotspot in the cluster.

C in the only answer that make sense.

C Is the Correct Answer

C https://cloud.google.com/bigtable/docs/overview#load-balancing

C is ok

C is the right answer

C is better option

Option-C is the better one.

The issue described is with "querying" meaning reading. Not writing. C: distributing across the Alphabet is good for Writing.

Suggest to study the following reference, it's important to design the row key pattern in Bigtable. https://cloud.google.com/bigtable/docs/overview#architecture https://cloud.google.com/bigtable/docs/overview#load-balancing

C looks good, I dont think we have to control number of nodes in Big table

Vote C

C. Review your RowKey strategy and ensure that keys are evenly spread across the alphabet.

correct row-key strategy improves performance

C is answer.Hot key/partitions are created due to improper row key design.

I think the ans is D