What is the primary purpose of a layout in Morpheus?

Question

Options

• ATo define the structural arrangement of cloud regions
• BTo specify the configuration and resources of an instance deployment
• CTo manage permissions for different instance types
• DTo replace provisioning scripts in automation

• A
  3% (1)
• B
  94% (32)
• C
  3% (1)

Explanation

In Morpheus, a layout defines the configuration and resources tied to an instance deployment - including the technology stack, memory/CPU, disks, network settings, and provisioning scripts - making it the blueprint for how an instance is built and deployed. Option A is wrong because cloud region structure is handled by cloud integrations and infrastructure configuration, not layouts. Option C is wrong because permissions are managed through roles and policies, not layouts. Option D is wrong because layouts actually include provisioning scripts rather than replacing them - scripts are embedded within the layout as part of the deployment definition.

Memory tip: Think of a layout as a blueprint for a single instance - it answers "what does this thing look like when deployed?" just as a building blueprint answers "what does this structure look like when built?"

No community discussion yet for this question.