A cloud storage company offers a subscription service where customers pay a base platform fee...

Usage Managementis the Revenue Management capability designed to operationalize consumption-based products. The scenario requires processing several metered resources—storage, data transfer, and API calls—and applying tiered pricing as customer usage increases.

Usage Management provides the standard architecture for receiving usage data, aggregating it according to configured resources and periods, applying entitlements where applicable, and rating consumption against pricing structures associated with the commercial products. This enables the resulting consumption charges to flow into downstream billing processes.

Option B recreates capabilities already provided by Revenue Management through custom objects, Apex, and batch processing. That would significantly increase technical debt and operational risk. Option C incorrectly makes Digital Wallet Management the primary end-to-end consumption lifecycle solution. Wallet-related structures can participate in entitlement and drawdown scenarios, but the supplied source identifies Usage Management as the overarching capability for ingesting, aggregating, and rating consumption.

The preferred architecture is therefore to model the products and pricing in the Salesforce catalog and use standard Usage Management processing.

Study Guide Reference:Invoice Management — Usage Management; usage ingestion, aggregation, rating, tiered consumption pricing.

===============