What is the primary purpose of custom inputs in Morpheus?

Question

Options

• ATo create predefined templates for user roles
• BTo allow users to input dynamic values for provisioning and automation
• CTo limit the customization of instance configurations
• DTo enforce static configurations across all deployments

• B
  90% (26)
• C
  3% (1)
• D
  7% (2)

Explanation

Custom inputs in Morpheus are designed to make provisioning workflows flexible by letting users supply dynamic values at runtime - such as hostnames, environment variables, or configuration parameters - rather than hardcoding them into a template. This makes option B correct: custom inputs exist precisely to capture user-provided values that drive provisioning and automation tasks.

Why the distractors are wrong:

• A is incorrect because custom inputs are not about defining user roles; role management is handled through Morpheus's role and permission system.
• C is the opposite of what custom inputs do - they expand customization, not restrict it.
• D contradicts the core concept entirely; static configurations are the problem custom inputs solve, not something they enforce.

Memory tip: Think of custom inputs as "fill-in-the-blank fields" on a form - they turn a rigid template into a flexible, user-driven workflow. If it's dynamic and user-supplied, it's a custom input.

No community discussion yet for this question.