What are important considerations when configuring a custom instance type in Morpheus? (Select two.)

Question

Options

• ADefining resource allocations (CPU, memory, storage)
• BRemoving support for cloud-based deployments
• CAssigning appropriate layouts to the instance
• DManually approving every instance request

• A
  78% (18)
• B
  4% (1)
• D
  17% (4)

Explanation

When configuring a custom instance type in Morpheus, defining resource allocations (A) ensures the instance has the correct CPU, memory, and storage specs to meet workload requirements - this is foundational to any instance type definition. Assigning layouts (C) is equally critical because layouts define the underlying technology stack, provisioning targets, and deployment options tied to that instance type; without them, the instance type cannot be provisioned.

Option B is wrong because Morpheus is designed to support multi-cloud deployments - removing cloud support contradicts the platform's core purpose. Option D is wrong because Morpheus uses automated approval workflows and policies; requiring manual approval for every request is an antipattern that defeats the platform's self-service model.

Memory tip: Think "Resources + Layouts = Ready to Launch" - you always need both the what (resource allocations) and the how (layouts) to make a custom instance type functional in Morpheus.

No community discussion yet for this question.