Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Database Engineer Topic 3 Question 49 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam
Question #: 49
Topic #: 3
[All Professional Cloud Database Engineer Questions]

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?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Isolating the user groups is an interesting idea, but it feels like overkill for this scenario. I'd try the Key Visualizer and Bigtable metrics first before resorting to that.
upvoted 0 times
...
Yolando
3 days ago
Definitely check the Bigtable metrics first to see if the table is hitting any resource limits. That could explain the daily performance spike.
upvoted 0 times
...
Isadora
5 days ago
The issue seems to be isolated to the new cohort of pilot users, so I'd start by checking the Key Visualizer to see if there's any hot-spotting or uneven data distribution causing the performance degradation.
upvoted 0 times
...
Ashanti
13 days ago
Adding more nodes to the Bigtable cluster could also be a good solution to improve performance.
upvoted 0 times
...
Floyd
16 days ago
I agree with Aron. That could help us identify the root cause of the poor performance.
upvoted 0 times
...
Aron
17 days ago
I think we should check the Cloud Monitoring table/bytes_used metric from Bigtable.
upvoted 0 times
...

Save Cancel