How does Morpheus handle incident management?

Question

Options

• ABy creating and tracking alerts based on system performance issues
• BBy enforcing manual log review processes
• CBy disabling all user notifications
• DBy allowing only one active incident at a time

• A
  90% (26)
• C
  7% (2)
• D
  3% (1)

Explanation

Morpheus handles incident management by creating and tracking alerts based on system performance issues (A), which is core to its monitoring and operations platform functionality - it automates the detection of anomalies, generates incidents from alert thresholds, and tracks their lifecycle through resolution.

Why the distractors are wrong:

• B is incorrect because Morpheus automates alerting and incident detection rather than enforcing manual log review, which would defeat the purpose of an operations platform.
• C is the opposite of correct behavior - Morpheus is designed to send notifications to keep teams informed of incidents, not disable them.
• D is incorrect because Morpheus can manage multiple concurrent incidents, not just one; real-world environments routinely have simultaneous issues across different services.

Memory tip: Think of Morpheus as an automated watchdog - its job is to watch system performance, bark (alert) when something goes wrong, and keep a record of every incident until it's resolved. If it disabled notifications or only watched one thing at a time, it would be a pretty useless watchdog.

No community discussion yet for this question.