What happens when a Blueprint is executed in Morpheus?

Question

Options

• AThe blueprint modifies existing resources without confirmation
• BThe blueprint files are copied to all user accounts
• CThe infrastructure or application is provisioned based on predefined configurations
• DThe process must be restarted manually for every update

• A
  3% (1)
• C
  92% (33)
• D
  6% (2)

Explanation

When a Blueprint is executed in Morpheus, it acts as a reusable template that automates the provisioning of infrastructure or applications according to predefined configurations - think of it as a recipe that Morpheus follows to spin up environments consistently and repeatably.

Why the distractors are wrong:

• A is incorrect because Blueprints provision new resources, not silently modify existing ones - Morpheus respects change management workflows.
• B is incorrect because Blueprints are not file distribution tools; they define infrastructure/app topology, not user account content.
• D is incorrect because the entire value of Blueprints is automation - manual restarts per update would defeat the purpose of the tool entirely.

Memory tip: Think of a Blueprint like a building architect's blueprint - the architect doesn't change an existing building or hand out copies to tenants; they hand the plan to a builder (Morpheus) who constructs something new from scratch based on the design. "Blueprint = Build from plan."

No community discussion yet for this question.