An administrator is tasked with setting up pricing for their VMware vSphere Foundation (VVF) environment. The accounting team has decided to charge users in 't-shirt sizes' for vCPU in the following…

Question

Options

• ABase rate storage per GB.
• BBase rate slabs.
• CBase rate CPU per GHz.
• DBase rate CPU per vCPU.

• A
  2% (1)
• B
  88% (53)
• C
  7% (4)
• D
  3% (2)

Explanation

Base rate slabs (option B) is correct because the "t-shirt sizing" model groups vCPU counts into defined ranges (1-2, 3-4, 5-8) and assigns a flat rate per slab/tier - not a per-unit rate. This is exactly what the slab pricing method is designed for: bucketing resource quantities into bands where any value within a band is charged the same price.

Why the distractors are wrong:

• A (storage per GB) - this charges by storage capacity, completely unrelated to vCPU allocation.
• C (CPU per GHz) - this bills based on clock speed/frequency, not vCPU count ranges.
• D (CPU per vCPU) - this charges a flat rate for each individual vCPU, which would produce different costs for 1 vs. 2 vCPUs; it doesn't support range-based t-shirt sizing.

Memory tip: Think of "slabs" like concrete slabs - flat surfaces that cover a range. If your workload falls anywhere on that slab, you pay the same price. T-shirt sizes = slabs, because both group things into fixed ranges rather than counting each unit individually.

No community discussion yet for this question.