Salesforce Certified Revenue Cloud Consultant (Rev-Con-201)

"Any unreleased services or features referenced are not currently available and may not be delivered on time or at all."
"Customers should make their purchase decisions based upon features that are currently available." Why
B is correct (Step-by-step): Understand the core requirement: Salesforce's Safe Harbor requires that plans and designs do not depend on unreleased functionality. Key factors: Roadmap items are forward-looking, may change, slip, or never ship. Verbal confirmations do not change Safe Harbor constraints. Comprehensive solution: The team should design solely with GA capabilities and, if the roadmap feature becomes GA later, refactor or enhance the design at that time. To accommodate future possibilities, use extensible patterns (e.g., interface-driven design, feature toggles) that work with today' s GA features yet allow safe adoption later-without committing to non-GA behavior now.
Incorrect options:
A: Violates Safe Harbor by presuming delivery/timeline of unreleased features.
C: Verbal confirmation does not override Safe Harbor; relying on it is noncompliant.
References:
Salesforce CPQ Implementation Guide - Safe Harbor / Forward-Looking Statements Salesforce Billing
Implementation Guide - Safe Harbor / Forward-Looking Statements Salesforce Subscription Management
Implementation Guide - Safe Harbor / Forward-Looking Statements

Exact Extracts from Salesforce CPQ Implementation Guide: "Local Cardinality defines the minimum and maximum quantities allowed for an individual product option within a bundle."
"Group Cardinality defines the quantity range allowed across all options within a product option group. It restricts the total number of items a user can select within that group." "Use both local and group cardinalities together to control both per-option limits and total group quantity constraints."
Step-by-Step Reasoning: Requirement: Max 3 T-shirts Max 3 caps Total bundle limit = 5 items combined.
Solution:
Local Cardinality: For each item (T-shirts, caps) # min 1, max 3 ensures flexibility. Group Cardinality: Across both # min 1, max 5 ensures total combined limit of 5. Why B is Correct:It satisfies both individual and group quantity rules while maintaining configuration flexibility.
Why Others Are Incorrect: A: Allows total of 6 (violates the total maximum requirement).
C: Missing group cardinality - does not control total combined quantity.
References:
Salesforce CPQ Implementation Guide - Product Bundles, Local and Group Cardinality Salesforce
Revenue Cloud Product Configuration Best Practices - Bundle and Option Management

Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and CPQ Implementation Guides): "Bundle-Based Pricing allows you to define how the total price of a bundle is determined, whether from component prices, a fixed price, or dynamic price calculation." "Price Adjustment Matrices are used within pricing procedures to apply conditional or tiered discounts to bundle or product pricing."
"Attribute-Based Pricing is used for pricing individual products based on attribute values, not entire bundles."
Step-by-Step Reasoning: Requirement: Create bundle pricing logic (discounted total price).
Apply varying discounts under specific conditions.
Correct Components:
Bundle-Based Price: Controls how bundle total is derived.
Price Adjustment Matrix: Applies dynamic, condition-based discounts. Why B is Correct:Matches both aspects - bundle calculation and dynamic discounting.
Why Others Are Incorrect: A: Attribute-Based and Volume Discount apply to standalone or quantity-based pricing, not complex bundles.
C: Product Selling Model controls selling duration/frequency, not bundle pricing or discount logic.
References:
Salesforce CPQ Implementation Guide - Pricing Procedures and Bundle-Based Pricing Salesforce Billing Implementation Guide - Price Adjustment Matrices Salesforce Subscription Management Implementation Guide - Bundle Pricing Strategy

"Transaction Types define how Revenue Cloud interprets pricing, eligibility, and discount logic for a specific transaction (Sales, Amendment, Renewal, Cancellation, etc.)." "Volume-Based Pricing applies
tiered or bulk discounts based on quantities but can be conditioned by Transaction Type.""For initial sales, use the Sales Transaction Type. For renewals or amendments, different types apply."
Step-by-Step Reasoning: Requirement: Apply bulk discounts only for business-to-business (B2B) sales (initial purchases).
Solution:
Configure Volume-Based Pricing rules.
Condition them on Sales Transaction Type (so they apply only during initial sales).
Why B is Correct: Sales Transaction Type accurately represents new B2B purchases. Enables separation of pricing logic by channel or buyer type. Why Others Are Incorrect: A: Quote Transaction Type is metadata used in CPQ quoting but not for pricing control logic. C: Order Transaction Type applies post-sale; discounts must be
calculated pre-order in pricing.
References:
Salesforce CPQ Implementation Guide - Volume-Based Pricing and Transaction Type Logic Salesforce Subscription Management Implementation Guide - Sales and Renewal Transaction Configuration Salesforce Billing Implementation Guide - Pricing Control via Transaction Type

Comprehensive and Detailed Explanation 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.
References:
Dynamic Revenue Orchestrator Guide - Jeopardy Management, Estimated Duration, and Thresholds

Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and Derived Pricing Documentation): "Derived Pricing allows a product's price to be calculated based on another product's price, either within the same quote or across transactions." *"The Derived Pricing Scope determines when and how the derived price is evaluated: Transactional: The derived price is calculated dynamically when both products are in the same quote or order. Global: The derived price references a price from the catalog or price book, not quote-specific."* "If the Derived Pricing Scope is not set to Transactional, product interdependencies within the same quote will not evaluate."
Step-by-Step Reasoning: Scenario: Warranty should price dynamically based on another product in the same transaction. Root Cause: The Derived Pricing Scope on the warranty product is likely not set to Transactional. Solution: Update the Derived Price record for the warranty product # set Derived Pricing Scope = Transactional.
Why B is Correct: Ensures the price is recalculated dynamically when the related product exists in the same quote/order.
Why A & C are Incorrect: A: Variables in the pricing procedure define logic but not scope of calculation.
C: "Is Derived" on price book entries flags derivation capability but not the transaction context for dynamic evaluation.
References:
Salesforce CPQ Implementation Guide - Derived Pricing Concepts and Scopes Salesforce Subscription Management Implementation Guide - Pricing Dependencies and Derived Price Records

To enable search functionality, the custom field must be added to Index and Search Configuration and the index must be rebuilt.

Page layouts do not affect search indexing.

References:
Product Discovery Setup Guide ?Search Configuration

Exact Extracts from Salesforce CPQ & Subscription Management Implementation Guides: "Product Discovery Context Definitions provide the framework for dynamic filtering and qualification rules during catalog browsing and product configuration." "Context definitions can include nodes that map Account, Contact, and related attributes (such as customer tier, geography, or historical data) for rule evaluation." "This enables dynamic, real-time product visibility and eligibility control during Browse Catalog." Step-by-Step Reasoning: Requirement: Dynamic catalog filtering during quoting based on Account Tier, Location, and Purchase History.
Correct Mechanism:
Product Discovery Context Definition - defines what contextual data (Account, Tier, Location, etc.) is available for evaluation in qualification rules.
Why A is Correct: It uses declarative context definition mapping (no code) to feed rule logic during catalog browsing. Why B and C are Incorrect: B: Sales Transaction Context applies to pricing and calculation logic, not catalog discovery visibility.
C: Product2 custom fields and layouts don't control dynamic filtering or interact with context definitions;
they're static metadata.
References:
Salesforce CPQ Implementation Guide - Product Discovery Context Definitions and Qualification Rules Salesforce Subscription Management Implementation Guide - Dynamic Product Eligibility using Context Definitions

To automatically generate invoices at a specific time and on a recurring schedule, Salesforce Billing provides the Recurring Invoice Run functionality. This feature allows users to define how often invoice runs should occur (e.g., daily, weekly, monthly) and at what time of day. In this scenario, the correct approach is to schedule a Recurring Invoice Run with a Weekly frequency, specifically set to run every Monday at 6:00
AM.
As described in the Salesforce Billing Implementation Guide, Recurring Invoice Runs allow Billing users to: Select the frequency (e.g., weekly)
Define the day(s) and time of execution Automatically generate invoices for completed billing schedules during the configured time window This method ensures consistency, reduces manual workload, and aligns with operational requirements. Option
A refers to Billing Treatments, which are used to manage how invoices are formatted or communicated, not when they are generated.
Option C, using a custom flow with Invoice Preview, is a non-standard and unnecessarily complex approach for a routine task that is already handled natively by Salesforce Billing.
Exact Extracts from Salesforce Revenue Cloud Documents: Salesforce Billing Implementation Guide - "Recurring Invoice Runs":"Use Recurring Invoice Runs to configure automated invoice generation. You can set the recurrence frequency (daily, weekly, etc.), and specify the time of execution to match business needs."
Billing Operations Guide - "Automation for Scheduled Invoicing":"Recurring invoice runs simplify billing operations by executing invoice logic for completed billing schedules on a regular cadence." References: Salesforce Billing Implementation Guide Salesforce Revenue Cloud Operations Guide Billing Setup & Automation Best Practices

The standard way to identify whether an Asset is managed by Salesforce Revenue Cloud's Lifecycle

Management engine is by using the HasLifecycleManagement field. This out-of-the-box field is a Boolean value on the Asset object that indicates whether the asset is tied to Revenue Lifecycle-managed records (e.g., originating from CPQ+ or Subscription Management flows). This field enables reporting, filtering, and business logic to segment Revenue Cloud-managed assets from assets generated through custom or legacy systems like CK's app. It is the most appropriate solution in this scenario as it requires no customization and is supported natively by Salesforce. Option B suggests creating a custom field, which is unnecessary since the platform already provides a system field for this purpose.
Option C (Asset Action Source) refers to tracing asset actions to originating events, but it is not suitable for broad classification of asset origin or management type.
Exact Extracts from Salesforce Revenue Cloud Documents: Subscription Management Implementation Guide - "Asset Data Model":"The HasLifecycleManagement field flags whether an asset is lifecycle-managed by Revenue Cloud. This is useful in environments where assets come from multiple systems."
Revenue Cloud Data Dictionary - "Asset Object":"Use HasLifecycleManagement to distinguish system-managed assets from externally generated or legacy assets." References: Salesforce Subscription Management Implementation Guide Salesforce Revenue Cloud Data Dictionary Asset Lifecycle Management Documentation