Topic 1 Question 72
Your organization stores marketing data such as customer preferences and purchase history on Bigtable. The consumers of this database are predominantly data analysts and operations users. You receive a service ticket from the database operations department citing poor database performance between 9 AM-10 AM every day. The application team has confirmed no latency from their logs. A new cohort of pilot users that is testing a dataset loaded from a third-party data provider is experiencing poor database performance. Other users are not affected. You need to troubleshoot the issue. What should you do?
Isolate the data analysts and operations user groups to use different Bigtable instances.
Check the Cloud Monitoring table/bytes_used metric from Bigtable.
Use Key Visualizer for Bigtable.
Add more nodes to the Bigtable cluster.
ユーザの投票
コメント(3)
- 正解だと思う選択肢: C
First step of performance troubleshooting is to use Key Visualizer https://cloud.google.com/bigtable/docs/performance#troubleshooting
👍 4chelbsik2022/12/27 B: Check the Cloud Monitoring table/bytes_used *** metric from Bigtable. Read throughput The number of bytes per second of response data sent. This metric refers to the full amount of data that is returned after filters are applied.
Write throughput The number of bytes per second that were received when data was written.
👍 1pk3492022/12/24C. The test data set is likely to have poor row key design. When loaded into the database, that data is probably hitting the same node and causing a hot spot. Addng more nodes will not solve a hot spot. Eliminate D. Neither will creating a new instance (A). B might be of interest, but is not the primary tool to diagnose Bigtable performance problems. For that, use Key Visualizer. Best answer is C. https://cloud.google.com/bigtable/docs/keyvis-overview
👍 1dynamic_dba2023/03/13
シャッフルモード