What configurations are available for Monitoring Groups in Morpheus? (Select two.)

Question

Options

• AAssigning resources to specific monitoring policies
• BSetting alert thresholds for grouped resources
• CDisabling monitoring for selected instances
• DRestricting log collection to a single cloud provider

• A
  92% (24)
• C
  4% (1)
• D
  4% (1)

Explanation

Monitoring Groups in Morpheus allow administrators to organize resources and apply targeted configurations - two of the core functions are assigning resources to specific monitoring policies (A) and setting alert thresholds for grouped resources (B). Option A is correct because Monitoring Groups exist precisely to bind a collection of resources to a monitoring policy, enabling consistent oversight. Option B is correct because thresholds (e.g., CPU, memory, availability) can be defined at the group level, triggering alerts when grouped resources breach those limits.

Option C is wrong because disabling monitoring is an instance-level setting, not a configuration option exposed through Monitoring Groups. Option D is wrong because Morpheus is a multi-cloud platform - log collection is not restricted to a single provider, and that restriction is not a Monitoring Group feature.

Memory tip: Think of Monitoring Groups as a "policy + threshold bundle" - they group resources, assign them a policy, and set thresholds. If an answer sounds like it restricts or disables rather than organizes and alerts, it's likely a distractor.

No community discussion yet for this question.