In VMware Cloud Foundation 9.0, pricing policies are configured within VCF Operations (Costing and Chargeback).
From the VCF 9.0 documentation under Cost and Chargeback Configuration:
“Base Settings define the default cost drivers for CPU, memory, and storage that apply across clusters unless overridden by a custom policy.”
To meet the requirement:
CPU, memory, and storage pricing must be identical across all clusters.
A new policy named Resources must be created and applied globally.
Thus:
1️⃣ Create a new policy under Base Settings for resource cost (Option A)
This satisfies:
Same CPU, memory, and storage cost across clusters.
From the documentation regarding policy hierarchy:
“When a custom cost policy is set as default, it applies to all objects that do not have a more specific policy assigned.”
2️⃣ Set “Resources” as the default policy (Option E)
This ensures:
All clusters inherit this pricing model.
Other unspecified settings fall back to default behavior.
From documentation regarding overrides:
“Specific object types such as clusters can have additional cost components defined through child policies that override parent policy settings.”
3️⃣ Create a child policy under “Resources” for SAP HANA cluster VM setup charges (Option F)
This satisfies:
VM setup charges applied only to SAP HANA cluster.
Other clusters remain unaffected.
All other settings remain default.
Why Other Options Are Incorrect
B – Setting Default Policy as default contradicts requirement to create a new named policy “Resources.”
C – VM setup charges should not be in Base Settings (would apply globally).
D – Incorrect hierarchy; policies are structured under custom policy trees, not under “Default Policy” in this context.
Document References (VCF 9.0):
VMware Cloud Foundation 9.0 → VCF Operations → Costing and Chargeback
VMware Cloud Foundation 9.0 → Policy Inheritance and Overrides
VMware Cloud Foundation 9.0 → Base Settings and Custom Cost Policies
