How does Morpheus organize infrastructure groups?

Question

Options

• ABy linking them to specific cloud integrations
• BBy limiting them to only on-premises resources
• CBy allowing only a single group per tenant
• DBy enforcing static resource allocations

• A
  90% (55)
• B
  2% (1)
• C
  3% (2)
• D
  5% (3)

Explanation

Morpheus organizes infrastructure groups by linking them to specific cloud integrations, allowing a single group to span multiple cloud providers, on-premises environments, and other infrastructure types - making groups a flexible logical boundary rather than a physical one. Option B is wrong because groups are not restricted to on-premises resources; they can include public clouds, private clouds, and hybrid setups. Option C is wrong because Morpheus supports multiple groups per tenant, enabling teams or projects to be segmented independently. Option D is wrong because Morpheus is designed for dynamic resource provisioning, not static allocation - one of its core value propositions is elasticity.

Memory tip: Think of a Morpheus group as a "cloud address book entry" - it points to cloud integrations and doesn't care whether those clouds are physical or virtual, local or remote.

No community discussion yet for this question.