How can custom inputs be used in Morpheus?

Question

Options

• ATo override system-level policies
• BTo provide user-defined values for provisioning instances
• CTo replace all default configurations with static inputs
• DTo restrict workflow execution to specific users

• A
  4% (2)
• B
  92% (45)
• C
  2% (1)
• D
  2% (1)

Explanation

Custom inputs in Morpheus are user-defined variables that allow administrators to create flexible, reusable provisioning templates where end users can supply specific values (such as instance names, sizes, or environment tags) at deployment time - making option B correct. Option A is wrong because custom inputs don't interact with system-level policy enforcement; that's handled by roles and tenants. Option C is wrong because custom inputs extend default configurations with dynamic values rather than replacing them with static ones - in fact, they're the opposite of static. Option D is wrong because restricting workflow execution to specific users is a function of role-based access control (RBAC), not custom inputs.

Memory tip: Think of custom inputs as "form fields on a provisioning wizard" - they exist purely to collect user-supplied data that gets injected into the deployment, not to control access or override policies.

No community discussion yet for this question.