How do Managed Service Providers (MSPs) use subtenants in Morpheus?

Question

Options

• ATo provide isolated environments for their customers within a shared Morpheus deployment
• BTo eliminate the need for multi-cloud management
• CTo restrict automation capabilities for cloud deployments
• DTo create a single access point for all customers with identical settings

• A
  88% (22)
• B
  8% (2)
• C
  4% (1)

Explanation

MSPs use subtenants in Morpheus to give each customer their own isolated environment - separate users, roles, resources, and visibility - all within a single shared Morpheus deployment, making option A correct. Option B is wrong because subtenants have nothing to do with eliminating multi-cloud management; Morpheus actually embraces multi-cloud. Option C is wrong because subtenants don't restrict automation - each tenant can still leverage Morpheus's full automation capabilities within their isolated space. Option D is wrong because the entire point of subtenants is the opposite: customers get distinct, customizable environments rather than a single shared configuration.

Memory tip: Think of subtenants like apartments in a building - the MSP owns the building (the Morpheus instance), but each customer has their own locked unit with their own keys, furniture, and settings.

No community discussion yet for this question.