An administrator of a VMware Cloud Foundation (VCF) fleet is tasked to delegate the resource...

The vSphere 9.0 Resource Management documentation, included within VMware Cloud Foundation 9.0, specifies that Resource Pools are the mechanism to delegate compute resources within a cluster. A resource pool acts as a container of compute resources (CPU and memory) that can be subdivided and assigned to VMs or groups of VMs.

The documentation states:

“Resource pools provide resource isolation, control, and delegation. You can configure reservations, limits, and shares to ensure that mission-critical workloads (such as production VMs) receive guaranteed resources, while development or test workloads consume only available resources.”

This aligns directly with the requirements:

Power on only if resources are available → Achieved via reservations and limits.

Production VMs require guaranteed levels of resources → Enforced using reservations.

Three-tier apps with varying demand → Controlled using shares and limits across multiple resource pools.

Other options are incorrect:

vSphere Availability (A) provides failover, not resource governance.

VCF Operations (B) monitors resource usage but does not allocate or enforce it.

Dynamic Resource Scheduling (D) balances workloads but does not provide delegated, guaranteed allocations per department or application tier.

Thus, the correct feature is vSphere Resource Pools.