Which two statements are true about using MySQL Enterprise Monitor Query Analyzer? (Choose two.)

Question

Options

• AThe single query QRTi pie chart in the Query Analyzer view is based on the average execution of
• BIt is possible to retrieve a normalized statement, but never the exact statement that was executed.
• CIt is possible to configure the Query Analysis built-in advisor to get notified about slow query
• DIt is possible to list and analyze statements in an arbitrary graph range selection from timeseries
• EIt is possible to import data into the Query Analyzer from heterogeneous sources, such as CSV.

• A
  29% (8)
• B
  11% (3)
• C
  46% (13)
• E
  14% (4)

Explanation

C is correct because the Query Analyzer includes a built-in advisor that can be configured to trigger alerts when queries exceed defined thresholds, enabling proactive notification about slow or problematic queries - this is a core monitoring feature of MySQL Enterprise Monitor.

D is correct because the Query Analyzer's timeseries graphs allow you to click and drag to select an arbitrary time range, then drill down to analyze only the statements executed during that window - a key feature for correlating query behavior with performance incidents.

A is wrong because the QRTi (Query Response Time index) pie chart reflects aggregated data across the selected time range, not just the average execution of a single query.

B is wrong because Query Analyzer can retrieve exact statements (via the Performance Schema or proxy-based collection), not just normalized versions - normalized statements are the default view, but the exact statement is also accessible.

E is wrong because Query Analyzer collects data from MySQL instances through its agents or the Performance Schema; it does not support importing from heterogeneous external sources like CSV files.

Memory tip: Think "Configure alerts, Drag to select" - the two interactive/configurable capabilities of Query Analyzer that make it useful for real-time investigation and proactive monitoring.

No community discussion yet for this question.