PCD Question 53

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose C1

  By using Event_timestamp_Account_id as the row key, you can efficiently query for events within a specific time range for a given account. While Option B would allow you to query events for a specific account, it might not be as efficient for time-based queries.

• Chose B1

  Designing an appropriate row key for Cloud Bigtable requires considering the access patterns and ensuring that the read and write operations are spread evenly across the key space to avoid hotspots. B. Set Account_id_Event_timestamp as a key. This option is likely the best choice because: Combining Account_id with Event_timestamp in the row key would allow you to maintain a good level of data distribution while preserving the ability to query efficiently by Account_id and sort by Event_timestamp within each account. This aligns well with Bigtable’s strengths in handling large, scalable, and sparse datasets. By leading with Account_id, you group all events for a single account close together in the key space, which can be efficient for reads that are interested in the activity of a specific account.

• Chose B1

  I would go with B.