How do Morpheus Service Plans facilitate compute resource reconfiguration?

Question

Options

• ABy allowing administrators to modify instance sizes dynamically
• BBy restricting workloads to fixed resource allocations
• CBy disabling instance modifications after deployment
• DBy enforcing manual intervention for every change

• A
  94% (46)
• B
  4% (2)
• D
  2% (1)

Explanation

Morpheus Service Plans act as templates that define compute resource configurations (CPU, memory, storage) for instances, and they enable administrators to dynamically resize instances by applying a different plan - making A correct. This reconfiguration can happen post-deployment without rebuilding the instance, which is the core value of service plans.

Why the distractors fail:

• B is the opposite of the feature's purpose - service plans enable flexibility, not fixed restrictions.
• C contradicts reality; Morpheus specifically supports post-deployment modifications through plan changes.
• D describes a manual, ad-hoc process - service plans exist precisely to automate and standardize resource changes, reducing manual intervention.

Memory tip: Think of Service Plans as "T-shirt sizes" (S, M, L, XL) you can swap on a running instance - the plan defines the size, and switching plans reconfigures it dynamically.

No community discussion yet for this question.