An administrator has noticed that virtual machine VM2 in the vApp shown in the Exhibit is demonstrating poor performance. Which three changes, if performed separately, would improve the performance of

Removing the CPU limit on the vApp eliminates the container-level cap that restricts combined CPU access for all VMs inside it, allowing VM2 to consume cycles that were previously blocked by the aggregate limit.

The exhibit places the binding constraint at the vApp CPU limit, not at a separate parent resource pool limit, so removing a resource pool limit above the vApp would not change the CPU available to VM2.

Increasing VM1's CPU reservation raises the minimum CPU that must be held for VM1, which reduces the uncommitted pool available to VM2 and would worsen VM2's performance.

Powering off VM1 removes it as a CPU consumer within the vApp, freeing cycles inside the existing limit so VM2 can use a larger portion of the available allocation without any policy change.

Increasing VM2's CPU reservation establishes a guaranteed minimum entitlement for it, ensuring the hypervisor schedules those cycles for VM2 even under contention from VM1 or the vApp limit.