Salesforce Updated Rev-Con-201 Exam Questions and Answers by lake

Product Selling Models and Product Selling Model Options separatewhat the product isfromhow the product is commercially sold. Instead of creating duplicate Product2 records for purchase, lease, subscription, or other commercial models, Revenue Management allows one product to be associated with multiple selling options. This substantially reduces SKU proliferation and improves catalog governance.

For example, the same physical product can have a one-time selling option for outright purchase and a term-defined selling option for leasing. Pricing can then be associated with the relevant selling model instead of maintaining separate product records for each commercial variation. Salesforce defines Product Selling Models as the mechanism that controls how products are sold and billed, while Product Selling Model Options associate those models with individual products.

Commercial versus Technical products addresses order decomposition and fulfillment rather than commercial-model rationalization. Multiple price books might support different prices, but they do not solve unnecessary duplication caused by different ways of selling the same product.

Study Guide Reference:Catalog Management — Product Selling Models; Product Selling Model Options; catalog rationalization.

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

The discount must depend on thetype of sales transaction/customer channelwhile still calculating according to purchased volume. The supplied source therefore identifiesSales Transaction Type combined with Volume-Based Pricing.

Volume-Based Pricing supplies the quantity-sensitive pricing behavior: when eligible buyers purchase larger quantities, progressively different pricing or discounts can be applied. Sales Transaction Type supplies contextual differentiation so the pricing logic can distinguish the B2B transaction path from the direct-to-consumer path.

This is superior to applying the volume schedule indiscriminately because the requirement states that individual end users must not receive the business bulk discount even if they purchase quantities that might otherwise reach the threshold.

Options A and C narrowly associate the logic with Quote or Order transaction types rather than using the Revenue Management Sales Transaction Type construct identified in the question. The broader Sales Transaction Type enables the pricing procedure to evaluate the intended commercial transaction context consistently.

The architectural pattern iscontext-sensitive pricing: quantity determines the discount level, while transaction classification determines whether that pricing mechanism is eligible to run.

Study Guide Reference:Configure, Price, Quote — Volume-Based Pricing; Sales Transaction Type; contextual pricing eligibility.

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

The appropriate approach is toamend the existing asset, retain its quantity, and reprice the amendment quote. The commercial requirement is a price refresh, not a cancellation, quantity change, or replacement of the customer ' s service.

Keeping the original quantity preserves the customer ' s existing entitlement and minimizes service disruption. Repricing causes the transaction to evaluate the applicable current pricing configuration rather than retaining the previously negotiated heavily discounted price. The resulting amendment can then proceed through the normal Quote-to-Order lifecycle so the new commercial state is properly recorded.

Option A unnecessarily creates a negative quantity and re-adds the same product. That models a removal and addition rather than a pure repricing requirement and can complicate lifecycle and billing calculations. Option C manually alters the Asset end date and creates another product line, which similarly disrupts asset continuity.

The correct design preserves the product ' s lifecycle identity while changing only the commercial value that actually requires revision.

Study Guide Reference:Asset Management — Asset Amendments; repricing existing assets; Quote-to-Order lifecycle; service continuity.

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

The correct Product Catalog Management business API isProducts List (POST). The requirement is to retrieve a collection of products for the browse phase while applying a specific catalog context. The POST-based Products List operation supports the structured request parameters needed to identify and filter the relevant product set.

This API aligns with Product Discovery use cases where an external interface, guided-selling experience, or custom component must retrieve products dynamically according to catalog and related discovery criteria.

Option A identifies a GET variant that is not the API specified by the supplied Revenue Management source for this catalog-scoped retrieval use case. Option B, Product Related Records List, serves a different purpose: retrieving related information associated with a product rather than returning the primary list of products belonging to the desired catalog.

The architectural distinction is betweendiscovering the products themselvesand retrieving secondary records related to an already identified product. For the browse phase, the consultant needs the former.

Study Guide Reference:Catalog Management — Product Catalog Management Business APIs; Products List (POST); Product Discovery and guided selling.