How do virtual images function in Morpheus?

Question

Options

• AThey act as predefined snapshots for provisioning new instances
• BThey replace API calls for provisioning
• CThey provide automatic scaling for container workloads
• DThey restrict access to certain virtual machines

• A
  90% (37)
• B
  5% (2)
• C
  2% (1)
• D
  2% (1)

Explanation

In Morpheus, virtual images are pre-configured templates - essentially saved disk images - that serve as the blueprint from which new instances are provisioned, making option A correct. When you provision a new workload, Morpheus pulls from these stored images to spin up consistent, repeatable environments quickly.

Why the distractors are wrong:

• B is incorrect because virtual images don't replace API calls; Morpheus still uses APIs extensively for orchestration - images are a data artifact, not a communication layer.
• C is incorrect because automatic scaling for containers is handled by orchestration engines (like Kubernetes) and Morpheus scaling policies, not by virtual images themselves.
• D is incorrect because access control in Morpheus is managed through roles, groups, and policies - not through virtual images.

Memory tip: Think of a virtual image as a "cookie cutter" - the cutter (image) doesn't bake the cookie or decide who gets one; it just defines the shape of every new instance stamped from it.

No community discussion yet for this question.