How can Morpheus administrators customize self-service catalog items?

Question

Options

• ABy using custom inputs, blueprints, and workflows
• BBy enforcing static configurations only
• CBy restricting automation features
• DBy requiring manual provisioning approvals

• A
  90% (28)
• B
  3% (1)
• D
  6% (2)

Explanation

Option A is correct because Morpheus's self-service catalog is designed around flexibility: administrators can define custom inputs (user-facing form fields), attach blueprints (infrastructure templates), and chain workflows (automated task sequences) to create rich, tailored provisioning experiences for end users.

• B is wrong because enforcing static configurations defeats the purpose of self-service - the whole value is dynamic, user-driven customization.
• C is wrong because Morpheus's catalog leverages automation features rather than restricting them; automation is central to its catalog functionality.
• D is wrong because requiring manual approvals is an optional governance layer, not a customization mechanism, and it contradicts the self-service model.

Memory tip: Think of catalog customization as "I-B-W" - Inputs collect user data, Blueprints define what gets built, Workflows automate what happens - all three together make a catalog item truly self-service.

No community discussion yet for this question.