An administrator has been tasked with configuring VCF Operations to set the pricing for Virtual Machines deployed by customers using VCF Automation. The administrator edits the Default Policy and enables the pricing engine. Which three additional steps must the administrator perform to complete this task? (Choose three.)
Answer
- A. Configure the Provider Pricing settings. Correct
- B. Add Recurring Charges for each VM tag.
- C. Configure the VC Pricing settings.
- D. Add a slab for each of the predefined VM sizes. Correct
- E. Set the CPU Rate to vCPU Count Based. Correct
- F. Apply a tag to each VM based on their size.
Explanation
The requirement is provider-side pricing for VMs consumed through VCF Automation Organizations, with charging based on assigned vCPU count and different rates by VM size. In VCF Operations, this maps to Provider Pricing, not vCenter pricing or tag-based additional charges. The official workflow states that Provider Pricing is configured from Infrastructure Operations > Configurations > Policy Definition > Edit Policy > Provider Pricing, where the administrator activates the pricing engine and configures Region Quota settings. For CPU charging, the Compute Rate section provides the option CPU GHz Based / vCPU Count Based, and the administrator must select vCPU Count Based because the business rule is based on assigned vCPUs, not GHz consumption. The same section supports Base Rate Slabs, which allow different base rates depending on the number of CPUs used; each slab uses a “greater than or equal” threshold and a base rate. Therefore, slabs should be created for Small, Medium, and Large VM ranges. Tags and recurring tag charges are unnecessary because VM size is determined directly from vCPU count.Reference topic: Objective 4.4 – Cost Management in VCF Operations / Provider Pricing / Rate Cards / Chargeback.