An administrator has noticed occasional performance degradation during peak usage times and needs to address this issue proactively by creating a mechanism that doesn't give data or outputs too…

Question

Options

• AImplement an alert specifying the metric, threshold, and duration.
• BImplement an alert with the default alert settings.
• CCreate a custom dashboard to visualize all alerts.
• DImplement an alert that notifies the IT team during off-peak hours.

• A
  79% (31)
• B
  5% (2)
• C
  3% (1)
• D
  13% (5)

Explanation

Option A is correct because in VCF Operations, an effective alert requires all three components - metric (what to monitor), threshold (the value that triggers the alert), and duration (how long the condition must persist before firing). The duration parameter is the critical piece that prevents alert fatigue: it ensures transient spikes don't flood the team with noise, directly addressing the "doesn't give data too often" requirement.

Option B is wrong because default alert settings are not tuned to the specific environment, which can result in too many false positives or missed issues - the opposite of what's needed. Option C is wrong because a dashboard is a visualization tool, not an alerting mechanism; it doesn't proactively notify anyone of anything. Option D is wrong because alerting only during off-peak hours defeats the purpose - performance degradation happens during peak usage, so that's precisely when you need notification.

Memory tip: Think of the three required components as MTD - Metric, Threshold, Duration. Duration is the "noise filter" that keeps the team from being overwhelmed, which is the core problem the question is testing.

No community discussion yet for this question.