What triggers alerts in Morpheus' monitoring system?

Question

Options

• ABreached thresholds or performance anomalies
• BPeriodic user login attempts
• CNetwork hardware updates
• DManual configuration changes only

• A
  93% (40)
• B
  5% (2)
• C
  2% (1)

Explanation

Morpheus' monitoring system triggers alerts when breached thresholds or performance anomalies are detected, which is the standard behavior of enterprise monitoring platforms - they continuously measure metrics and fire alerts when values exceed defined limits or deviate unexpectedly from baselines.

Why the distractors are wrong:

• B (Periodic user login attempts) - Login events are tracked by authentication/audit systems, not performance monitoring.
• C (Network hardware updates) - Hardware changes are configuration management events, not monitoring triggers.
• D (Manual configuration changes only) - If alerts required manual triggers, the monitoring system would be pointless; automation is the whole value.

Memory tip: Think of monitoring systems like a smoke alarm - they're always watching passively and only "alert" when something crosses a danger threshold (smoke level too high = performance metric too high). The keyword "threshold" is your anchor for any monitoring question.

No community discussion yet for this question.