A MySQL server is monitored using MySQL Enterprise Monitor's agentless installation. Which three features are available with this installation method? (Choose three.)

Question

Options

• AMySQL Replication monitoring
• Bnetwork-related information and network characteristics
• CMySQL Query Analysis data
• DCPU utilization
• Esecurity-related advisor warnings
• Foperating system memory utilization
• Gdisk usage and disk characteristics including disk advisors warnings

• B
  3% (1)
• C
  90% (35)
• D
  3% (1)
• F
  5% (2)

Explanation

With agentless installation, MySQL Enterprise Monitor connects directly to the MySQL instance over a network using JDBC/SQL-no software is installed on the host OS. This means it can only collect data MySQL itself exposes through SQL queries, Information Schema, or Performance Schema: Query Analysis data (C) from performance_schema, security advisor warnings (E) from inspecting MySQL configuration and privileges, and disk-related advisors (G) via MySQL's own datadir and tablespace metadata.

Why the distractors are wrong:

• A (Replication monitoring): Full replication topology monitoring requires a locally installed agent to reliably track replication threads and lag across hosts.
• B (Network characteristics) and D (CPU utilization) and F (OS memory utilization): These are all operating system-level metrics. Without an agent running on the host, the monitor has no access to OS internals-only MySQL-exposed data.

Memory tip: Think "agentless = MySQL-only view." If the metric lives inside MySQL (queries, security config, disk via MySQL metadata), agentless can see it. If the metric lives in the OS (CPU, RAM, raw network stats), you need the agent installed on that machine.

No community discussion yet for this question.