A vApp is performing poorly and an administrator determines that the memory resources are low. How should the administrator resolve this issue?

vApps support memory reservations at the container level, configurable through the Edit Settings dialog on the existing vApp without any rebuild required. Setting a reservation at the vApp level instructs the resource scheduler to hold the specified amount of memory for the entire vApp, directly addressing the low-memory performance problem in the most straightforward way.

Configuring reservations individually on each VM bypasses the vApp-level resource pool abstraction and does not use the intended vApp resource management model for collective resource guarantees.

Rebuilding the vApp is unnecessary because memory reservations are editable on an existing vApp through its settings, making this approach disruptive without any technical benefit.

Like option C, rebuilding the vApp is not required, and assigning per-VM reservations rather than a vApp-level reservation still fails to use the vApp resource container model as intended.