What is a key step in configuring a custom instance type in Morpheus?

Question

Options

• ADefining the instance layout and resource specifications
• BAssigning it to a predefined automation workflow
• CManually deploying each instance type individually
• DRestricting the instance type to only private cloud environments

• A
  88% (37)
• B
  2% (1)
• C
  7% (3)
• D
  2% (1)

Explanation

Configuring a custom instance type in Morpheus requires defining the instance layout and resource specifications (A) because the layout determines how the instance is structured - including the container or VM configuration, resource sizing (CPU, memory, storage), and provisioning behavior that Morpheus uses to deploy consistently across environments.

Why the distractors are wrong:

• B is incorrect because automation workflows are an optional, separate concern - they can be associated with an instance type later but are not a required configuration step.
• C is wrong because Morpheus's purpose is centralized, template-driven provisioning; manually deploying each instance defeats that entirely.
• D is incorrect because custom instance types in Morpheus can be scoped to any cloud (public, private, or hybrid) - restricting to private clouds only is not a configuration requirement.

Memory tip: Think of "layout" as the blueprint - just like a building can't be constructed without architectural plans, an instance type can't be provisioned without a defined layout and resource spec. If you remember "Layout = Blueprint", option A will always stand out.

No community discussion yet for this question.