Revenue Cloud Consultant Rev-Con-201 Book

“A Term Selling Model defines a fixed duration for a product or service, such as 12 months, and specifies how the customer is billed—monthly, quarterly, or annually.”

“Evergreen Selling Models are used for ongoing, indefinite subscriptions without a predefined end date.”

“To convert a one-time purchase into an installment plan over a fixed period, use a Term-based Selling Model with the appropriate billing frequency.”

Step-by-Step Reasoning:

Current State: Product is a one-time purchase.

Required Outcome: Convert to 12 equal monthly payments — this is a fixed duration (12 months) with monthly billing frequency.

Correct Setup: Assign Term Monthly selling model, defining the duration as 12 months with monthly charge intervals.

Why Others Are Incorrect:

B (Term Annual): Uses annual billing, not monthly.

C (Evergreen Monthly): Represents an open-ended subscription, not a fixed 12-month term.

“Product Classifications allow you to define and manage attributes that are reusable across multiple products, ensuring catalog consistency and reducing maintenance.”

“Selling Models define how a product is sold—one-time, term-based, or evergreen—and can be applied to a product without duplicating the record.”

“A flexible catalog design leverages reusable metadata like Product Classifications, Selling Models, and Attribute Sets rather than creating separate product records for each variation.”

“Dynamic or configurable bundles support product combinations across business units without static dependencies or hard-coded configurations.”

Step-by-Step Reasoning:

Core Requirement: Minimize catalog duplication while supporting various selling models and reusable attributes.

Key Design Factor: Use Product Classifications to standardize and reuse product attributes across offerings.

Implementation Approach: Assign Selling Models at the product level (One-Time, Term, Evergreen) for flexible pricing and lifecycle management.

Outcome: This setup enables consistent catalog governance, lower maintenance, and support for configurable bundles across multiple business units.

Incorrect Options:

A: Creates redundant records and increases maintenance.

C: Static bundles eliminate flexibility and reusability, conflicting with requirements.

Exact Extracts from Salesforce Subscription Management Implementation Guide:

“When multiple assets exist for the same product at different price points, Salesforce applies the FIFO (First In, First Out) strategy to determine which asset(s) to cancel and what price to use for refund calculation.”

“The earliest purchased asset is considered first during partial cancellations or quantity reductions.”

“This ensures financial accuracy based on original transaction pricing rather than averaging or last purchase pricing.”

Step-by-Step Reasoning:

Scenario: Multiple purchases at different prices → cancel a portion.

System Behavior: Cancellation refund is tied to the earliest purchased (first-in) asset.

Why A is Correct: Reflects Revenue Cloud’s default FIFO cancellation pricing logic.

Why Others Are Incorrect:

B: Average pricing is not used by default; FIFO is the standard.

C: LIFO would use the latest purchase, which is not the default method.

References :

Salesforce Subscription Management Implementation Guide — Cancellation and Refund Logic (FIFO Pricing)

Salesforce Billing Implementation Guide — Asset-Level Cancellation Pricing Strategy

Exact Extracts from Salesforce CPQ and Subscription Management Implementation Guides:

“When a ramped asset is renewed through the InitiateRenew action or API, Revenue Cloud replicates the ramp structure from the original quote to the renewal quote.”

“Each ramp segment and its pricing terms are preserved on the renewal quote lines.”

“This ensures consistency in pricing logic, duration, and segment breakdowns for renewals of ramped subscriptions.”

Step-by-Step Reasoning:

Scenario: Ramped subscription (e.g., quantity or price changing per period).

Renewal via API: The InitiateRenew API copies asset and ramp data into the new quote.

Result: All ramp segments are recreated — preserving ramp structure for renewal.

Why B is Correct:

Renewal quote retains the same ramp lines as the original asset.

Why Others Are Incorrect:

A: Segments are recreated as ramped (not flattened).

C: Would eliminate ramp structure, which contradicts the API’s renewal logic.

References :

Salesforce CPQ Implementation Guide — Ramp Renewals and InitiateRenew API Behavior

Salesforce Subscription Management Implementation Guide — Renewal Processing for Ramped Assets