An administrator created a new cost-based pricing card and attached it to a VMware Cloud on AWS (VMC) resource. When the administrator checked the pricing of a VM after the cost calculation had…

Question

Options

• AA zero value was used for one of the Basic Charges in the pricing card.
• BOnly rate-based pricing cards are applied with VMC.
• CThe cost calculation needs to run twice, when using VMC.
• DPricing cards are not supported with VMC resources.

• A
  9% (5)
• B
  72% (42)
• C
  3% (2)
• D
  16% (9)

Explanation

Option B is correct because VMware Cloud on AWS (VMC) only applies rate-based pricing cards, not cost-based ones. Since the administrator attached a cost-based pricing card, it is simply ignored for VMC resources - resulting in a price of zero, not an error. VMC uses a host-based billing model that aligns with rate-based pricing, not the component-cost model that cost-based cards rely on.

Why the distractors are wrong:

• A is wrong because a zero value in Basic Charges would still affect traditional (non-VMC) workloads - the root issue here is card type incompatibility, not card configuration.
• C is wrong because there is no two-run requirement for VMC cost calculations; this option is fabricated.
• D is a near-miss but wrong - pricing cards are supported with VMC, just only the rate-based variety.

Memory tip: Think "VMC = Rate, not Cost" - VMware Cloud on AWS is a rented host service with fixed/variable rates, so it naturally maps to rate-based pricing cards, not cost-based ones that model owned infrastructure.

No community discussion yet for this question.