Salesforce Rev-Con-201 Exam Questions

Salesforce Revenue Cloud introduces the Product Selling Model and Product Selling Model Option framework to help companies offer multiple purchase or subscription options for the same base product, reducing catalog sprawl. This approach is ideal for businesses that previously created multiple product records (e.g., separate SKUs for lease vs. buy) just to accommodate different pricing or selling logic.

With selling models, you define whether a product is sold as a one-time purchase, subscription (e.g., monthly, annual), lease, or usage-based. You can then attach multiple Selling Model Options to a single product, each reflecting a specific commercial approach (e.g., Lease Monthly, Term Annual, One-Time).

This allows the business to maintain a streamlined catalog while supporting diverse sales motions.

Option B refers to the decomposition process and is more relevant for fulfillment than pricing.

Option C (Multiple Price Books) enables regional or segmented pricing but doesn't solve the core problem of catalog sprawl due to multiple sales models.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide -- ''Product Selling Models'':

''Selling Models reduce catalog complexity by allowing a single product to support multiple commercial options such as one-time, lease, or subscription.''

CPQ Implementation Guide -- ''Product Configuration Best Practices'':

''Use selling model options to attach different billing or pricing terms to a single product record rather than duplicating products.''

Subscription Management Implementation Guide

Salesforce CPQ Implementation Guide

Revenue Cloud Product Catalog Strategy Notes

===========

Comprehensive and Detailed From Exact Extract:

Salesforce Billing includes a Suspend Billing feature that stops invoice generation for an account.

From Salesforce Billing Implementation Guide:

''Use Suspend Billing on the Account to pause invoicing for customers who are delinquent or temporarily blocked.''

''This prevents future invoices without modifying global schedulers or deleting invoice records.''

Option A would halt invoicing for all customers.

Option B removes existing invoices but does not stop future ones.

Salesforce Billing Implementation Guide --- Suspend Billing; Account Billing Controls.

When using Product Catalog Management in Salesforce Revenue Cloud, visibility of products during quote creation (especially through Product Discovery) is controlled by the Context Definition. Contexts allow administrators to define when and for whom products are visible during the product selection process, based on criteria like sales channels, quote type, or other business rules.

If products are not appearing during quote preparation, it is often due to a missing or misconfigured context definition. Assigning the correct Context Definition in Product Discovery Settings ensures that products and bundles are available during quoting based on business logic.

Option A (selecting a selling model) affects how the product is priced and billed, but not its visibility.

Option B (pricing procedure) impacts price calculations, not product discovery or visibility.

Exact Extracts from Salesforce Revenue Cloud Documents:

CPQ Implementation Guide -- ''Product Discovery Configuration'':

''Ensure that context definitions are properly set so that products appear under the right conditions during quoting. Missing contexts will result in products not being visible to end users.''

Revenue Cloud Product Catalog Guide -- ''Using Context for Product Availability'':

''Context Definitions act as filters for product discovery. Without proper context mapping, products may not show up for selection.''

Salesforce CPQ Implementation Guide

Product Catalog Management Documentation

Revenue Cloud Product Discovery Settings Guide

===========

Comprehensive and Detailed From Exact Extract:

In DRO, SLA and jeopardy management are typically driven by:

Estimated Duration -- how long a task is expected to take (e.g., 60 minutes).

Jeopardy Threshold -- when a task is considered at risk (e.g., 15 minutes before due time).

These parameters enable jeopardy alerts and proactive management before SLA breaches.

Completion Deadline / Warning Interval (A) and Task Priority / Escalation Rule (B) are more generic concepts and not the named DRO configuration parameters for this specific SLA pattern.

Dynamic Revenue Orchestrator Guide -- Jeopardy Management, Estimated Duration, and Thresholds

===========

Comprehensive and Detailed From Exact Extract:

In Salesforce Revenue Lifecycle Management, eligibility and availability rules are built using Decision Tables. The predefined templates for product eligibility and product availability rely on Qualification objects.

From the Revenue Lifecycle Management Implementation Guide:

''Eligibility and availability rules are driven by Product Qualifications and Product Category Qualifications, which determine whether a product can be selected for a specific customer or scenario.''

''Decision table templates for eligibility and availability use Qualification objects as the evaluation criteria.''

These objects are designed specifically for determining whether a product should be selectable based on business rules, customer attributes, and catalog categorizations.

Why other options are incorrect:

Product Price Book and Product Schedule are used for pricing, not eligibility.

Product Relationship and Product Attribute are used in configuration rules, not eligibility templates.

Salesforce Revenue Lifecycle Management Implementation Guide -- Eligibility and Availability Decision Tables; Product Qualification Framework.

===========