A vApp is running out of compute resources when overall activity is high within the resource pool. At other times, everything is fine. What should be done to resolve this issue?

Increasing the resource pool's Shares only adjusts the relative priority when competing for resources but does not guarantee that additional physical resources will actually be available to the vApp during contention.

The Expandable Reservation Type allows a vApp or resource pool to draw resources beyond its own configured reservation from the parent pool whenever demand spikes, which directly addresses intermittent exhaustion during high-activity periods. Because the problem only occurs under load, this setting provides dynamic access to additional capacity without requiring a permanent reservation increase across the entire pool hierarchy.

Setting the CPU and Memory Limit to Unlimited removes the cap on maximum usage but does not help the vApp obtain resources it cannot access due to reservation constraints in a contended environment.

Creating a new resource pool with the same hardware configuration adds no new physical compute resources and therefore would not resolve the shortage during peak periods.