HPE0-G04 · Question #68
What are common use cases for self-service catalog items in Morpheus? (Select two.)
The correct answer is A. Rapid provisioning of virtual machines and applications B. Automating IT service requests. Self-service catalog items in Morpheus exist to empower users to provision resources and automate workflows on their own - making A (rapid VM/app provisioning) and B (automating IT service requests) the natural fit, since both reduce bottlenecks by letting teams act without…
Question
What are common use cases for self-service catalog items in Morpheus? (Select two.)
Options
- ARapid provisioning of virtual machines and applications
- BAutomating IT service requests
- CPreventing users from deploying new instances
- DLimiting configuration options for administrators only
How the community answered
(41 responses)- A90% (37)
- C7% (3)
- D2% (1)
Explanation
Self-service catalog items in Morpheus exist to empower users to provision resources and automate workflows on their own - making A (rapid VM/app provisioning) and B (automating IT service requests) the natural fit, since both reduce bottlenecks by letting teams act without waiting on IT.
C is wrong because a self-service catalog is designed to enable deployments, not prevent them - access controls and policies handle restriction, not catalog items. D is wrong because self-service catalogs are built for end users, not administrators; admins already have full access, so limiting options to them contradicts the purpose of self-service entirely.
Memory tip: Think "self-service = speed + automation for end users." If a choice blocks or restricts, it's the opposite of what a catalog item does.
Topics
Community Discussion
No community discussion yet for this question.