Rev-Con-201 Exam Questions & Answers
Salesforce Certified Revenue Management Consultant • Salesforce
100% money-back guarantee
Sample Rev-Con-201 Questions
Practice with real exam-style questions, each with the verified correct answer and explanation.
A customer currently owns subscription products with a term of 3 years. A ramped deal was configured to sell the products with a quantity of 20 in year one, 30 in year two, and 40 in year three. The list price of the product is US $1,000 per year.
The subscription started on June 24, 2025, and will end on June 23, 2028. Today's date is January 15, 2026.
What is the formula to calculate the current Monthly Recurring Revenue (MRR)?
Exact Extracts from Salesforce Billing and Subscription Management Guides:
''Monthly Recurring Revenue (MRR) represents the recurring portion of subscription revenue normalized to a monthly value.''
''For ramped deals, MRR should be calculated based on the currently active ramp period.''
''When a subscription includes quantity changes by period, MRR is (active period's quantity list price) 12.''
Step-by-Step Reasoning:
Current Date: January 15, 2026 within Year 1 of the ramp (June 24 2025 -- June 23 2026).
Active Quantity: 20 units.
List Price: $1,000 per year.
MRR Formula:
MRR=(201000)12=1,666.67
Why A is Correct:
Uses current active ramp period only, not the entire 3-year term.
Why Others Are Incorrect:
B: Divides by total months (36) --- incorrect for monthly normalization.
C: Aggregates all ramp years, not just the current active one.
Salesforce Billing Implementation Guide --- Recurring Revenue Metrics (MRR/ARR)
Salesforce Subscription Management Implementation Guide --- Ramp Deal Revenue Recognition and Active Period Logic
A pricing administrator aims to configure pricing for a smartphone so that the monthly installment price varies based on the selected memory options (128 GB, 256 GB, 512 GB) and contract term options (12 months, 24 months). The price should be equally divided for each month, considering the combinations of memory and contract term as price impacting attributes, with no interest charges applied.
How many records need to be present in the Attribute-Based Adjustments pricing schedule to satisfy this scenario?
Exact Extracts from Salesforce CPQ Implementation Guide:
''Attribute-Based Pricing allows administrators to define price adjustments based on one or more attribute combinations.''
''Each unique combination of attributes (e.g., Memory Size Contract Term) represents one record in the adjustment schedule.''
''If there are three memory options and two contract term options, there are six total combinations that require six entries in the Attribute-Based Adjustment matrix.''
Step-by-Step Reasoning:
Attributes:
Memory Options: 128 GB, 256 GB, 512 GB 3 values
Contract Term Options: 12 months, 24 months 2 values
Combinations: 3 2 = 6 unique attribute pairs.
Each combination requires one adjustment record.
Why A is Correct:
Six pricing adjustment records ensure accurate monthly installment calculation for each combination.
Why Others Are Incorrect:
B: Only accounts for one attribute (memory).
C: Arbitrary number; doesn't represent all possible pairs.
Salesforce CPQ Implementation Guide --- Attribute-Based Pricing and Adjustment Matrices
Salesforce Revenue Cloud Pricing Configuration Guide --- Combining Attribute-Driven Pricing Dimensions
A company using Revenue Cloud experiences frequent change requests after the customer accepts the quote and the order is activated. Order managers want the ability to change orders after activation but before fulfillment.
Which out-of-the-box permission set should be assigned to Order Managers to support in-flight order changes?
Comprehensive and Detailed From Exact Extract:
Salesforce Revenue Cloud introduces Change Orders as the standard mechanism for modifying activated orders.
From the Order Management section of Revenue Cloud documentation:
''Assign the Place Change Order permission set to users who manage in-flight order changes.''
''Change Orders allow quantity increases or decreases after an order is activated.''
Superseded orders and supplemental orders serve different purposes and do not support general in-flight changes.
Revenue Lifecycle Management / Order Management Guide --- Change Orders; Permission Set Definitions.
A Revenue Cloud Consultant confirmed that a user has the correct permissions and license access to view and amend assets. However, when the user navigates to the Account page, they do not see any assets available for amendment, even though active assets exist.
What is the reason the user cannot see the assets?
Comprehensive and Detailed From Exact Extract:
The Managed Asset Viewer is a Lightning component that must be added to the Account Lightning page to display and manage assets. In addition, the Asset related list can also be surfaced for basic asset visibility.
Revenue Cloud documentation notes that users may have full object access but still be unable to see assets if:
The Managed Asset Viewer component is not placed on the Account page.
The Asset related list is not included on the layout.
Amend/Renew/Cancel flows (C) drive process but do not control base visibility. Expired assets (B) may still be visible depending on filters; this does not explain ''no assets visible'' when active ones exist.
Revenue Lifecycle Management Implementation Guide -- Managed Asset Viewer Setup and Page Configuration
A high-tech company offers cloud storage services and wants to define different rates for API calls based on customers' usage patterns.
How should a consultant set up this requirement?
Comprehensive and Detailed From Exact Extract:
Salesforce Billing and Subscription Management support multiple usage-based pricing (UBP) models.
From the Subscription Management and Billing Implementation Guides:
''Attribute rate entries enable pricing based on characteristics of usage events, including call type, region, or customer usage behavior.''
''Use attribute rate entries when pricing varies based on usage attributes and patterns, not volume alone.''
This fits the requirement of applying different rates to API calls depending on how customers use the service.
Why other options are incorrect:
Base card entries: Apply a flat rate.
Tier rate entries: Apply rates based on volume tiers, not usage attributes.
Salesforce Billing Implementation Guide -- Usage-Based Pricing Models; Attribute Rate Pricing.
Get access to all 165 verified questions with detailed answers.
Unlock All Rev-Con-201 Questions