What is the primary function of App Monitors in Morpheus?

Question

Options

• ATo monitor application health and performance metrics
• BTo override cloud provider logs
• CTo manage authentication settings for applications
• DTo limit application scalability

• A
  90% (18)
• C
  5% (1)
• D
  5% (1)

Explanation

App Monitors in Morpheus serve as health-check and performance-tracking tools that continuously observe the availability and responsiveness of deployed applications - making A correct. Morpheus uses App Monitors to alert on downtime, track uptime metrics, and integrate with its overall observability framework, which is core to its platform management capabilities.

Why the distractors are wrong:

• B is wrong because Morpheus doesn't override cloud provider logs - it may aggregate or surface them, but overriding is not a monitoring function.
• C is wrong because authentication is handled through Morpheus's Identity Source and Role settings, not App Monitors.
• D is wrong because App Monitors have nothing to do with scalability limits; scaling is controlled through instance types, policies, and provisioning settings.

Memory tip: Think of App Monitors as the "pulse check" for your apps - just like a heart monitor tracks vital signs, App Monitors track application health. If it's about watching the app, it's a monitor; authentication, scaling, and logs are managed elsewhere.

No community discussion yet for this question.