Which pricing scenario allows the pricing quantity and pricing unit to be consumed in different amounts?

Which pricing scenario allows the pricing quantity and pricing unit to be consumed in different amounts?

• A. Simple per-unit pricing
• B. Block & Fractional block pricing
• C. Commitment based discounts
• D. Different Units

Answer: (D)

The idea being tested is that pricing can be defined in one unit while actual usage is measured in another. This separation lets you price a quantity in one dimension (the pricing quantity) but tally and bill the actual consumption in a different dimension (the pricing unit). That flexibility is what “Different Units” captures. Why this fits best: If a service allows you to buy a certain amount of something (pricing quantity) but the way you actually consume it is tracked in another unit (pricing unit), you can handle scenarios where the measurement for usage doesn’t line up with the thing you’re purchasing. For example, you might price access by seats (pricing quantity) but track usage in hours of feature utilization (pricing unit), or price data transfer per GB while the system reports consumption in TB. In these cases, the amount you buy and the unit you measure usage in are different, which is exactly what this option enables. In contrast, simple per-unit pricing ties price to the same unit as consumption, block pricing still uses the same unit in both price and usage, and commitment-based discounts modify total price or need but don’t inherently permit a mismatch between pricing quantity and usage unit.

The idea being tested is that pricing can be defined in one unit while actual usage is measured in another. This separation lets you price a quantity in one dimension (the pricing quantity) but tally and bill the actual consumption in a different dimension (the pricing unit). That flexibility is what “Different Units” captures.

Why this fits best: If a service allows you to buy a certain amount of something (pricing quantity) but the way you actually consume it is tracked in another unit (pricing unit), you can handle scenarios where the measurement for usage doesn’t line up with the thing you’re purchasing. For example, you might price access by seats (pricing quantity) but track usage in hours of feature utilization (pricing unit), or price data transfer per GB while the system reports consumption in TB. In these cases, the amount you buy and the unit you measure usage in are different, which is exactly what this option enables.

In contrast, simple per-unit pricing ties price to the same unit as consumption, block pricing still uses the same unit in both price and usage, and commitment-based discounts modify total price or need but don’t inherently permit a mismatch between pricing quantity and usage unit.