MENU
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?
Suggested Answer: C
Get Premium Professional Cloud Database Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
JU
Justine
11 months ago
Not sure if isolating user groups will really solve the problem.
FR
Freeman
11 months ago
Wait, why are only the pilot users affected? That’s weird!
RO
Rose
11 months ago
Adding more nodes seems like overkill without checking the metrics first.
NA
Nada
11 months ago
Definitely agree, metrics can reveal a lot about performance issues.
TE
Tegan
12 months ago
I think checking the Cloud Monitoring metrics is a solid first step.
AR
Arlene
12 months ago
Adding more nodes seems like a quick fix, but I wonder if it would actually solve the problem or just mask it temporarily.
LE
Leonida
1 year ago
I feel like using Key Visualizer could give us insights into the data access patterns, but I can't recall if it directly addresses performance issues.
LE
Leonida
1 year ago
Checking the Cloud Monitoring metrics sounds familiar; I think it could help identify if there's a resource issue.
LO
Louvenia
1 year ago
I remember we discussed isolating user groups in a similar practice question, but I'm not sure if that's the best first step here.
SU
Sunshine
1 year ago
This seems straightforward to me. The new pilot users are the ones experiencing the performance issues, so I'd start by isolating them to a separate Bigtable instance. That should help narrow down the problem.
LE
Leila
1 year ago
I've seen issues like this before with Bigtable. My strategy would be to use the Key Visualizer tool to get a better understanding of the data distribution and potential hotspots. That should help point me in the right direction.
VI
Vilma
1 year ago
I'm a bit confused by this question. There are a few different options, but I'm not sure which one is the best approach. Maybe I'll try to eliminate the obvious wrong answers first.
TO
Tony
1 year ago
Okay, let's see. The key here is to isolate the issue and figure out what's causing the performance problems for the new pilot users. I think I'll start by checking the Cloud Monitoring metrics.
SO
Solange
1 year ago
Hmm, this seems like a tricky one. I'll need to think through the different options carefully to figure out the best approach.
CA
Callie
1 year ago
Hmm, I bet the new pilot users are all trying to access the same dataset at the same time. Key Visualizer to the rescue!
FA
Fatima
1 year ago
User 3: Once we pinpoint the issue, we can add more nodes to the Bigtable cluster if needed.
BR
Brande
1 year ago
User 2: Good idea. We can use Key Visualizer to identify any hotspots causing the poor performance.
HI
Hillary
1 year ago
User 1: Let's check the Cloud Monitoring table/bytes_used metric from Bigtable.
KA
Karol
1 year ago
I'm going to go with the Key Visualizer. It's the most targeted tool for identifying data skew or hotspots, which sounds like the likely culprit here.
PE
Pedro
1 year ago
User 3: Adding more nodes to the Bigtable cluster could also help improve performance.
MI
Mirta
1 year ago
Lazaro: Let's try Key Visualizer first and see if that helps pinpoint the problem.
YU
Yun
1 year ago
User 3: Adding more nodes to the Bigtable cluster could also help with the poor performance issue.
JO
Johnna
1 year ago
User 2: I'm going to go with the Key Visualizer. It's the most targeted tool for identifying data skew or hotspots, which sounds like the likely culprit here.
LA
Lazaro
1 year ago
User 2: I think Key Visualizer might be more helpful in this situation. It can identify data skew or hotspots.
NO
Nohemi
1 year ago
User 1: Have you checked the Cloud Monitoring table/bytes_used metric from Bigtable?
BR
Brittney
1 year ago
User 1: Have you tried checking the Cloud Monitoring table/bytes_used metric from Bigtable?
DE
Delsie
2 years ago
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.
FA
Fausto
1 year ago
Let's start by checking the Cloud Monitoring table/bytes_used metric from Bigtable and using Key Visualizer.
VA
Valentin
1 year ago
I agree, isolating the user groups seems like a drastic solution.
YO
Yolando
2 years ago
Definitely check the Bigtable metrics first to see if the table is hitting any resource limits. That could explain the daily performance spike.
IS
Isadora
2 years 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.
AS
Ashanti
2 years ago
Adding more nodes to the Bigtable cluster could also be a good solution to improve performance.
FL
Floyd
2 years ago
I agree with Aron. That could help us identify the root cause of the poor performance.
AR
Aron
2 years ago
I think we should check the Cloud Monitoring table/bytes_used metric from Bigtable.