How does Morpheus handle public cloud service plans differently from private cloud service plans?

Question

Options

• APublic cloud service plans use predefined instance sizes, while private cloud plans allow custom
• BPrivate cloud service plans are locked to a single provider
• CPublic cloud service plans require manual instance provisioning
• DPrivate cloud service plans cannot be customized

• A
  91% (31)
• B
  3% (1)
• D
  6% (2)

Explanation

Option A is correct because in Morpheus, public cloud service plans (e.g., AWS, Azure, GCP) are tied to provider-defined instance types like t3.medium or Standard_D2s_v3 - you select from a fixed catalog the provider controls. Private cloud plans (VMware, Nutanix, etc.) let administrators define custom CPU, RAM, and storage combinations, giving full flexibility over sizing.

Distractor breakdown:

• B is wrong - private cloud plans are not locked to a single provider; Morpheus supports multiple private cloud integrations simultaneously.
• C is wrong - public cloud provisioning in Morpheus is automated, not manual; that's a core value proposition of the platform.
• D is wrong - private cloud plans are actually the more customizable option, the opposite of what D claims.

Memory tip: Think "public = pick from a menu (provider's menu), private = build your own" - public clouds dictate the options, private clouds give you the kitchen.

No community discussion yet for this question.