Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
After a quote is created from amending a bundle asset, a user unselects a bundle component inside the configurator and saves and exits to the Transaction Line Editor.
How will the user identify the unselected bundle component?
Comprehensive and Detailed From Exact Extract:
When a user removes (unselects) a bundle component during an amendment, Salesforce displays the removed item in the quote as a cancellation action.
From the RLM / CPQ Configurator documentation:
''When a component is removed during an amendment, the TLE displays a red cancellation indicator.''
''The system shows the cancellation as a negative quantity (-1 or reduction of original quantity).''
Option A is incorrect because removed items must appear in the amendment quote.
Option C uses Status = Canceled but does not reflect the required cancellation tag or quantity behavior.
Revenue Lifecycle Management Implementation Guide --- Amendments; Bundle Component Removal Behavior; Cancellation Line Indicators.
A product administrator has been asked to set up product visibility in the Browse Catalog phase based on a customer's region. Which Revenue Cloud specific capabilities should the product administrator use to satisfy this requirement?
Comprehensive and Detailed From Exact Extract:
In Revenue Cloud Product Catalog Management, Browse Catalog product visibility is controlled using Qualification Rules and Product Qualification decision tables. The standard (''out-of-the-box'') decision table and related qualification rule procedures are designed exactly for use cases like:
Hiding or showing products based on contextual criteria such as region, industry, customer segment, etc.
Evaluating product visibility during Product Discovery / Browse Catalog.
The documented approach is to configure ProductQualification and Qualification Rule Procedures so that they reference customer region (for example, via Account or Quote fields) and drive visibility accordingly. This leverages standard Revenue Cloud capabilities instead of creating custom frameworks.
Option A (custom decision table) is possible but not the recommended Revenue Cloud--specific capability when there is already an out-of-the-box decision table built for product qualification.
Option B (separate price books per region) controls pricing, not visibility, and quickly becomes hard to maintain.
Salesforce Revenue Lifecycle Management Implementation Guide -- Product Qualification, Qualification Rule Procedures, and catalog visibility
Product Catalog Management Documentation -- Using Qualification Rules with Browse Catalog
A Revenue Cloud Consultant manages a product catalog serving multiple regions and customer segments. The team wants to dynamically control product visibility based on criteria such as region, industry, or customer type.
What is the recommended approach?
Comprehensive and Detailed From Exact Extract:
Revenue Cloud recommends using Qualification Rules for:
Contextual product visibility in Browse Catalog and Product Discovery.
Evaluating criteria like region, industry, and account attributes using decision tables and qualification procedures.
Multiple price books (A) address pricing, not visibility. Separate catalogs (B) can be used in some cases, but quickly become complex; qualification-based visibility is the scalable, recommended method.
Product Catalog Management Guide -- Qualification Rules for Product Visibility
Revenue Lifecycle Management Implementation Guide -- ProductQualification Decision Tables
A Cloud Consultant is using Contracts AI to retrieve clauses and contract fields from a PDF. After the initial run, the consultant realizes that a payment method custom field needs to be retrieved that was not initially included.
What should the consultant do to retrieve this custom field?
In Salesforce Revenue Cloud's Contracts AI functionality, the process of retrieving data such as clauses or contract fields from uploaded documents (e.g., PDFs) relies on Contract Extraction Templates. These templates define which attributes and contextual mappings are used during document extraction. When a new field---such as Payment Method (a custom field)---needs to be retrieved, it must be explicitly added to the extraction template through configuration.
Exact Extract from Salesforce Revenue Cloud Documentation:
''To extract additional custom fields or clauses, users must update the contract extraction template to include attribute and context mappings for each new field. The template defines which contract data points Contracts AI retrieves from the uploaded document.''
--- Salesforce Subscription Management Implementation Guide (Contracts AI section)
The AI prompt template (Option B) controls the tone and structure of the generated summaries, not data extraction parameters. Logging a support case (Option C) is unnecessary, as this configuration is fully managed by the consultant or administrator through template updates.
Salesforce Subscription Management Implementation Guide -- Contracts AI Setup
Salesforce Revenue Cloud Implementation Guide -- Contract Extraction Templates
Salesforce Revenue Cloud Consultant Study Guide
Universal Containers (UC) sells complex Enterprise Connectivity Suites made up of physical hardware, cloud software, and services. Each component demands a unique fulfillment process, but UC's current system treats all orders uniformly, causing delays and errors. UC needs to break down complex orders, apply custom fulfillment plans per product, and ensure tailored delivery.
Which Revenue Cloud capability should solve UC's problems with accurate order fulfillment?
Comprehensive and Detailed From Exact Extract:
Dynamic Revenue Orchestrator (DRO) is Revenue Cloud's orchestration engine for post-order processes. Documentation describes DRO capabilities such as:
Decomposing orders into multiple fulfillment tasks or sub-orders based on product configuration.
Applying different orchestration/fulfillment plans for hardware, software, and services.
Managing task dependencies, SLAs, and routing to the appropriate teams and systems.
Product Configurator (B) manages configuration at quote time, not post-order orchestration.
Experience Cloud (C) provides portals, not order decomposition or fulfillment flows.
Revenue Lifecycle Management / Dynamic Revenue Orchestrator Guide -- Order Decomposition and Fulfillment Plans
Revenue Cloud Implementation Guide -- Orchestration of complex orders
A product has a list price of US$15,000. An attribute-based price override of $12,000 is applied first, followed by a $1,000 bundle-based adjustment discount and a 10% manual discount at the end of the product sale.
What will be the final price of the product shown in the Net Price column of the Transaction Line Editor?
Comprehensive and Detailed From Exact Extract:
Calculation sequence:
Original List Price = $15,000
Attribute-based price override Price becomes $12,000
Bundle-based adjustment discount: $12,000 $1,000 = $11,000
10% manual discount on $11,000:
10% of 11,000 = 1,100
11,000 1,100 = $9,900
Therefore, the Net Price = $9,900.
Revenue Lifecycle Management / Salesforce Pricing Guide -- Pricing Element Order and Net Price Calculation
A software company wants to offer a Premium Suite bundle that includes multiple applications and support services at a discounted price compared to purchasing each component individually. The company also needs to apply different discounts to this bundle based on custom conditions.
Which pricing element must the company use to define the bundle pricing logic and then to calculate its price within a pricing procedure?
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.
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
Exam domains verified against: Official Salesforce Rev-Con-201 exam guide, last checked October 2026.
Explain how to configure foundational Salesforce features for Agentforce Revenue Management, including flows, Lightning page components, permission set licenses, and permission sets.; Identify and describe Agentforce Revenue Management features, such as Context Service, Omnistudio, Business Rules Engine (BRE), and application programming interfaces (APIs).; Design context-aware dashboards and key performance indicators (KPIs) using native Salesforce reporting tools.; Describe core Agentforce Revenue Management fields, objects, and relationships between objects.
Plan implementation readiness by identifying required licenses, permission sets, and prerequisite feature toggles. Assign stakeholder roles and responsibilities for cross-cloud projects and develop a scope of work and project plan that drives implementation through build, test, deployment, and adoption.
Explain core concepts and capabilities of Catalog Management within Revenue Cloud. Apply out-of-the-box functionality to implement solutions that meet scenario-based business requirements for product catalogs and hierarchies.
Use the Product Configurator tool to customize product components and attributes and validate configurations. Configure pricing procedures for customer-specific business cases and generate accurate pricing quotes using CPQ features and Agentforce capabilities.
Configure Salesforce Contracts to meet business requirements in scenario-based situations. Configure Order Management functionality to support order-to-cash processes and meet specific business scenarios.
Explain core concepts and capabilities of Asset Management within Revenue Cloud. Implement solutions using appropriate out-of-the-box Asset Management functionality to handle scenario-based asset tracking and lifecycle requirements.
Explain core concepts and capabilities of Invoice Management within Revenue Cloud. Apply out-of-the-box Invoice Management functionality to generate, handle, and manage invoices within revenue operations scenarios.
Common questions about the exam itself
