In what scenarios are custom inputs useful in Morpheus? (Select two.)

Question

Options

• AProvisioning dynamic virtual machines based on user selections
• BLimiting deployment configurations to a single cloud provider
• CAutomating workload scaling based on user-defined thresholds
• DBlocking all changes to predefined instance templates

• A
  82% (27)
• B
  12% (4)
• D
  6% (2)

Explanation

Custom inputs in Morpheus are designed to make provisioning and automation dynamic and user-driven, which is exactly what options A and C represent. A is correct because custom inputs let users select values (like VM size, OS, or network) at provisioning time, so the same template can produce different VMs based on what the user enters. C is correct because custom inputs can capture user-defined thresholds (like CPU percentage or instance count) that feed into automation tasks or workflows, enabling flexible, policy-driven scaling without hardcoding values.

B is wrong because custom inputs do the opposite - they increase flexibility across multiple clouds rather than locking deployments to one provider. D is wrong because custom inputs enable changes and variability in templates, not block them; restricting templates would undermine the whole point of the feature.

Memory tip: Think of custom inputs as "fill-in-the-blank fields on a provisioning form" - they're useful whenever you need a human (or process) to supply a value that varies per deployment, whether that's a VM spec (A) or a scaling threshold (C). If an answer removes flexibility or locks things down, it contradicts the purpose of custom inputs.

No community discussion yet for this question.