Which of the following are the best resources for monitoring potential server issues? (Choose two.)

Question

Options

• AUser connections
• BFirewall usage
• CIndex usage
• DCPU usage
• EQuery execution
• FMemory usage

• A
  4% (2)
• D
  94% (51)
• E
  2% (1)

Explanation

CPU usage (D) and Memory usage (F) are the best resources for monitoring potential server issues because they directly reflect the server's health and capacity - high CPU or memory consumption signals resource exhaustion, performance degradation, or runaway processes that can lead to outages or slowdowns.

Why the others are wrong:

• A (User connections): Useful for capacity planning, but connection count alone doesn't indicate a server problem - a server can have many connections and still be healthy.
• B (Firewall usage): A network security concern, not a server performance or health metric.
• C (Index usage): A query optimization concern for database tuning, not a direct indicator of server-level issues.
• E (Query execution): Relevant for slow query analysis, but it's a symptom-level metric - CPU and memory are the underlying resources that reveal why queries are slow.

Memory tip: Think of the server as a human worker - if they're overheating (CPU) or overwhelmed (Memory), the whole operation breaks down. Those are your two core vitals to watch, just like a doctor checks temperature and blood pressure first.

No community discussion yet for this question.