What are best practices for managing self-service catalog items in Morpheus? (Select two.)

Question

Options

• ARegularly updating catalog items to reflect changes in infrastructure requirements
• BEnforcing RBAC policies to control user access
• CRestricting customization options for all users
• DPreventing integration with Infrastructure as Code (IaC) tools

• A
  81% (44)
• C
  11% (6)
• D
  7% (4)

Explanation

Managing self-service catalog items in Morpheus effectively requires two foundational practices: keeping items current and controlling who can access them.

A is correct because infrastructure environments evolve constantly - cloud costs change, new instance types become available, and organizational standards shift. Catalog items that aren't updated become stale, lead to misconfigurations, and erode user trust in the self-service portal.

B is correct because Role-Based Access Control (RBAC) ensures users only see and consume catalog items appropriate for their role, preventing unauthorized provisioning, cost overruns, or security exposures.

C is wrong because restricting all customization defeats the purpose of self-service. Controlled customization (within guardrails) is a feature, not a risk - Morpheus is designed to allow flexible options scoped by role.

D is wrong because IaC integration (Terraform, Ansible, etc.) is actually a strength of Morpheus catalog items, enabling repeatable, version-controlled infrastructure. Blocking it would reduce consistency and automation.

Memory tip: Think "ACE the catalog" - Always update, Control access (RBAC), Empower users within guardrails. The two wrong answers both describe restricting things that should actually be enabled.

No community discussion yet for this question.