Q: 6
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 method:
Small (1-2 vCPU)
Medium (3-4 vCPU)
Large (5-8 vCPU)
Which rate method is used for this configuration?
Options
Discussion
Makes sense to go with B here. T-shirt sizes use banded ranges, so base rate slabs is what fits best instead of per unit charges like D. If anyone's seen differently let me know, but this aligns with cost practice.
Option B is correct here. The t-shirt size approach is a slab or banded rate, not per-vCPU or per-GB. Option D traps you if you think "per vCPU" applies, but they're grouping vCPUs into sizes. Pretty sure that's how they expect you to map it.
Think it's D since they're charging per vCPU, not by group sizes. Trap could be B.
Not D, it's B. T-shirt sizing matches slabs, not per-vCPU billing. Trap is thinking D fits.
I get why D looks right since it's about vCPU counts, so D here.
D , since it's asking for vCPU and the t-shirt sizes break down by vCPU count. Easy to think B if you miss that part.
B, had something like this in a mock and the t-shirt size bands were specifically labeled as slabs there.
Its B. T-shirt sizing means using slabs or bands, not per vCPU. Pretty sure that's how VMware labels this kind of pricing, saw similar on a practice set.
Maybe B here, since the t-shirt sizing uses vCPU ranges, which matches what slabs do. I saw similar logic in lab guides and practice tests, but not 100% sure if VMware always calls it that.
Had something like this in a mock-B lines up with t-shirt sizing for those vCPU bands.
Be respectful. No spam.
