What is the primary purpose of Morpheus' built-in logging and monitoring capabilities?

Question

Options

• ATo track infrastructure performance and detect issues proactively
• BTo automate cloud provider updates
• CTo disable real-time monitoring for performance optimization
• DTo restrict log access to administrators only

• A
  92% (45)
• B
  2% (1)
• C
  2% (1)
• D
  4% (2)

Explanation

Morpheus' built-in logging and monitoring capabilities exist to give operations teams visibility into their infrastructure - tracking performance metrics, capturing logs, and surfacing anomalies before they become outages, which is exactly what option A describes. Option B is wrong because automating cloud provider updates is a provisioning/automation feature, unrelated to observability. Option C is a contradiction - disabling monitoring would defeat the entire purpose of having it, and no real monitoring system promotes itself by being turned off. Option D is wrong because monitoring and logging tools are typically designed to democratize visibility across teams, not gate it behind admin-only access.

Memory tip: Think of Morpheus monitoring as a "health dashboard for your cloud" - its job is to watch and warn, which maps directly to tracking performance and detecting issues (A).

No community discussion yet for this question.