HPE0-G04 · Question #20
What are fundamental provisioning concepts in Morpheus? (Select two.)
The correct answer is A. Instances as deployable workloads B. Layouts for defining resource configurations. In Morpheus, Instances represent the fundamental deployable unit - a workload (VM, container, app stack) that users provision into an environment, making A correct. Layouts define the underlying resource configuration for an Instance type (CPU, memory, storage, network), acting…
Question
What are fundamental provisioning concepts in Morpheus? (Select two.)
Options
- AInstances as deployable workloads
- BLayouts for defining resource configurations
- CStatic network assignments only
- DEliminating the need for cloud APIs
How the community answered
(45 responses)- A91% (41)
- C4% (2)
- D4% (2)
Explanation
In Morpheus, Instances represent the fundamental deployable unit - a workload (VM, container, app stack) that users provision into an environment, making A correct. Layouts define the underlying resource configuration for an Instance type (CPU, memory, storage, network), acting as the blueprint that drives provisioning behavior, making B correct.
C is wrong because Morpheus supports dynamic network assignments and IPAM integrations, not just static assignments - static-only would be a significant limitation the platform explicitly avoids. D is wrong because Morpheus relies on cloud APIs (AWS, Azure, VMware, etc.) to orchestrate resources; it abstracts them into a unified UI but absolutely does not eliminate them.
Memory tip: Think "I-L" - Instances are what you deploy, Layouts are how you define it. If an answer suggests Morpheus removes cloud dependencies or restricts networking, it's describing the opposite of what the platform does.
Topics
Community Discussion
No community discussion yet for this question.