MENU
You are the database administrator of a Cloud SQL for PostgreSQL instance that has pgaudit disabled. Users are complaining that their queries are taking longer to execute and performance has degraded over the past few months. You need to collect and analyze query performance data to help identity slow-running queries. What should you do?
Suggested Answer: D
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
37 comments · newest first
LE
Leila
10 months ago
C might miss some important details, though.
MI
Mira
10 months ago
Definitely agree with D, Query Insights is super helpful!
TH
Theola
11 months ago
Wait, can we really trust the Query Insights data?
JU
Justine
11 months ago
A is also a good option, but not as detailed as D.
SH
Shaunna
11 months ago
I think option D is the best choice for tracking query performance.
NA
Nana
11 months ago
I feel like the Query Insights dashboard is the most direct way to find high execution times, but I can't recall if it requires any special setup.
RO
Roslyn
11 months ago
I practiced a question similar to this where we had to analyze logs. I wonder if using Logs Explorer would help pinpoint the slow queries.
FR
France
12 months ago
I think viewing Cloud SQL operations could give us some historical context, but it might not show the current slow queries.
LO
Lonny
12 months ago
I remember we talked about using Query Insights for performance issues, but I'm not sure if it's the best option here.
RU
Ruth
1 year ago
I'm feeling pretty confident about this one. The key is that pgaudit is disabled, so I can't use that. But the Query Insights dashboard sounds like the best option to get the query performance data I need to troubleshoot this issue.
ED
Edelmira
1 year ago
Okay, I think I've got this. Since pgaudit is disabled, I can't rely on that for query performance data. So I'll need to use the Logs Explorer to find the high-execution time queries. That should give me the information I need to identify the problem areas.
CA
Carmen
1 year ago
Hmm, I'm a bit unsure here. I'm not familiar with the Query Insights dashboard, so I'm not sure if that's the best approach. Maybe I should review the application logs first to see if I can spot any database calls that are causing issues.
EL
Elizabeth
1 year ago
This seems straightforward - I'd go with option D to use the Query Insights dashboard to identify the slow-running queries.
WY
Wynell
1 year ago
This question covers a lot of ground. I'll need to review my notes on DCO to make sure I select the two most relevant benefits. Better safe than sorry on this one.
JA
Janine
1 year ago
I bet the answer is D, but I'm also going to try option B just for fun. Who knows, maybe I'll find a hidden gem in those Logs Explorer queries!
SH
Sheridan
1 year ago
Sounds good, we can see which option was more effective in identifying slow-running queries.
IR
Iraida
1 year ago
Let's compare our findings after we analyze the data.
JE
Jesusita
1 year ago
I'm going to try option B as well, just to see if there's anything interesting in the Logs Explorer queries.
MI
Mitsue
1 year ago
User3: Sounds good, let's gather as much data as we can to identify those slow-running queries.
DE
Deeann
1 year ago
User2: I agree, but I'm curious about option B. Let's also try using Logs Explorer queries.
LI
Lilli
1 year ago
User1: I think D is the way to go. Let's check the Query Insights dashboard.
LI
Lili
1 year ago
I think D is the best option to identify high execution times.
PE
Pearly
1 year ago
A seems a bit too broad, doesn't it? I mean, sure, you can view Cloud SQL operations, but that's not going to give you the specific query performance data you need.
AN
Angella
1 year ago
A) View Cloud SQL operations to view historical query information.
BE
Berry
1 year ago
D) Use the Query Insights dashboard to identify high execution times.
AL
Alyce
1 year ago
B) White a Logs Explorer query to identify database queries with high execution times.
VI
Virgina
1 year ago
Haha, I'm not even going to bother with option C. Reviewing application logs to find database calls? That's like trying to find a needle in a haystack!
RA
Raina
1 year ago
Haha, I'm not even going to bother with option C. Reviewing application logs to find database calls? That's like trying to find a needle in a haystack!
AL
Almeta
1 year ago
B) White a Logs Explorer query to identify database queries with high execution times.
LE
Leota
1 year ago
A) View Cloud SQL operations to view historical query information.
TO
Torie
1 year ago
B looks like a good option too, but I'm not sure if it's as comprehensive as the Query Insights dashboard. I guess it depends on how much data you need to analyze.
GR
Gracia
2 years ago
I think the correct answer is D. The Query Insights dashboard provides detailed information on query performance, which is exactly what the question is asking for.
BU
Burma
1 year ago
D) Use the Query Insights dashboard to identify high execution times.
MA
Mariann
1 year ago
A) View Cloud SQL operations to view historical query information.
WI
William
2 years ago
I prefer option B. Writing a Logs Explorer query to identify database queries with high execution times seems more detailed to me.
CE
Celeste
2 years ago
I agree with Leslie. That seems like the most efficient way to analyze query performance data.
LE
Leslie
2 years ago
I think we should use the Query Insights dashboard to identify high execution times.