Which method can be used to identify why a server has been marked down by a Health Monitor?

Question

Options

• AMousing over the Health Score indicator of the Virtual Service
• BSearching for failed Health Monitor requests in Client Logs
• CClicking on the Health Monitor in Templates -> Profiles -> Health Monitors to open the Health
• DHealth Monitor in the Pool -> Server Analytics screen

• A
  4% (2)
• B
  18% (8)
• C
  7% (3)
• D
  71% (32)

Explanation

Option D is correct because the Pool → Server Analytics screen provides detailed Health Monitor data specific to individual servers, including the actual Health Monitor responses and failure reasons that caused a server to be marked down. Option A (mousing over the Health Score indicator on the Virtual Service) shows a high-level status summary, not the granular failure details from Health Monitor probes. Option B is wrong because Health Monitor failures are not recorded in Client Logs - Client Logs capture client-facing traffic, not backend probing activity. Option C is a distractor because viewing a Health Monitor template in Templates → Profiles shows the configuration of the monitor, not the runtime results of why a specific server failed.

Memory tip: Think "Pool → Server = Per-server proof" - when you need to know why a specific server was marked down, you drill into the Pool's server-level analytics where the Health Monitor's actual probe results live.

No community discussion yet for this question.