What are use cases for virtual images in Morpheus? (Select two.)

Question

Options

• ACreating repeatable OS templates
• BAutomating security patch deployments
• CRestricting instance scaling
• DReducing provisioning time for new workloads

• A
  87% (48)
• B
  4% (2)
• C
  9% (5)

Explanation

Virtual images in Morpheus act as pre-configured, reusable machine images that serve as the foundation for instance provisioning. A is correct because virtual images are essentially OS templates - you build them once with your desired configuration, and teams can repeatedly deploy identical environments from them. D is correct because provisioning from a pre-built image skips the time-consuming OS installation and base configuration steps, making new workload deployment significantly faster.

B is wrong because security patching is handled through Morpheus automation tasks, workflows, or policies - not virtual images, which are static snapshots. C is wrong because scaling behavior is governed by Morpheus policies and instance configurations, not by the image itself.

Memory tip: Think of virtual images as "golden stamps" - you stamp out identical copies quickly (D) from a master template (A). Patching and scaling are operational concerns handled elsewhere in Morpheus, not at the image layer.

No community discussion yet for this question.