What is a key component when creating a self-service catalog item in Morpheus?

Question

Options

• ADefining service plans and instance types
• BDisabling workflow automation
• CPreventing users from modifying templates
• DLimiting deployment to on-premises environments

• A
  96% (22)
• B
  4% (1)

Explanation

Defining service plans and instance types (A) is correct because these elements form the foundation of a self-service catalog item in Morpheus - they determine the compute resources, sizing options, and deployment configurations that end users can select when provisioning from the catalog. Without service plans and instance types, users would have no structured way to choose and deploy infrastructure.

Why the distractors are wrong:

• B is wrong because workflow automation is a core feature of catalog items, not something to disable - it enables repeatable, governed deployments.
• C is wrong because self-service catalogs typically allow users to customize templates within defined parameters; locking them out defeats the purpose.
• D is wrong because Morpheus is a multi-cloud platform and catalog items are designed to deploy across cloud and on-premises environments, not restricted to one.

Memory tip: Think of a catalog item like a restaurant menu item - the service plan is the portion size and the instance type is the dish itself. You must define both before a customer (user) can order (deploy).

No community discussion yet for this question.