Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-908 Topic 14 Question 93 Discussion

Actual exam question for Oracle's 1Z0-908 exam
Question #: 93
Topic #: 14
[All 1Z0-908 Questions]

You are having performance issues with MySQL instances. Those servers are monitored with MySQL Enterprise Monitor.

Using Query Analyzer, where do you begin to look for problem queries?

Show Suggested Answer Hide Answer
Suggested Answer: B, D, E

Contribute your Thoughts:

Beula
2 months ago
Wait, you're telling me MySQL has an 'Enterprise Monitor'? Does that come with a complimentary fedora and a lifetime supply of energy drinks?
upvoted 0 times
Leslee
15 days ago
C) Look for queries with big prolonged spikes in row activity/access graph in the times series graph.
upvoted 0 times
...
Joye
16 days ago
B) Look for queries with low total latency times in the Latency section in the times series graph.
upvoted 0 times
...
Alva
1 months ago
A) Sort the ''Exec\' column and check for SQL queries with low Query Response Time index (QRTi) values.
upvoted 0 times
...
...
Maurine
2 months ago
B seems the most logical choice. Latency times are a clear indicator of where the issues lie. Who needs all that fancy 'Exec' column sorting, anyway?
upvoted 0 times
Jennie
1 months ago
I prefer A, sorting the 'Exec' column for low QRTi values can also be helpful in identifying problematic queries.
upvoted 0 times
...
Brandon
1 months ago
I think D could also be a good option. Sorting the 'Exec' column for high QRTi values might help pinpoint problem queries.
upvoted 0 times
...
Sunshine
1 months ago
I agree, B does seem like the most logical choice. Latency times are a clear indicator of where the issues lie.
upvoted 0 times
...
...
Viola
2 months ago
C sounds like the best option to me. Checking for those big spikes in row activity/access is a surefire way to find the culprits.
upvoted 0 times
...
Jeniffer
2 months ago
I think A is the way to go. Sort by low QRTi values? That's counterintuitive, but I guess it makes sense if we're looking for the problem queries.
upvoted 0 times
Elke
1 months ago
User1: Let's give it a try and see what we find.
upvoted 0 times
...
Teresita
1 months ago
User3: I agree, it helps identify queries that are causing performance issues.
upvoted 0 times
...
Madonna
1 months ago
User2: Yeah, that's a good starting point to find problem queries.
upvoted 0 times
...
Danilo
1 months ago
User1: I think A is the way to go. Sort by low QRTi values?
upvoted 0 times
...
...
Janna
2 months ago
D is the correct answer. We want to sort the 'Exec' column and look for queries with high QRTi values, as those are the problematic ones causing performance issues.
upvoted 0 times
Kristeen
2 months ago
User 2: Thanks for the tip! I'll make sure to focus on those queries first.
upvoted 0 times
...
Destiny
2 months ago
User 1: D is the correct answer. We want to sort the 'Exec' column and look for queries with high QRTi values, as those are the problematic ones causing performance issues.
upvoted 0 times
...
...
Tamera
2 months ago
I prefer looking for queries with big prolonged spikes in row activity/access graph. It can help pinpoint the problematic queries more effectively.
upvoted 0 times
...
Carri
2 months ago
I agree with Ulysses. It's important to identify queries that are causing performance issues.
upvoted 0 times
...
Ulysses
3 months ago
I think I would begin by sorting the 'Exec' column and checking for SQL queries with low Query Response Time index values.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77