Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. Rev-Con-201

Salesforce Rev-Con-201 Exam Questions
Salesforce Certified Revenue Cloud Consultant (Page 8 )

Updated On: 24-Feb-2026
Page 6 of 34
PDF with 165 Questions

A smartphone product is currently sold as a one-time upfront payment.

In order for it to be sold with equal monthly installment payments for 12 months, what should the consultant set up?

  1. Assign a product selling model option of Term Annual to the product.
  2. Assign a product selling model option of Term Monthly to the product.
  3. Assign a product selling model option of Evergreen Monthly to the product.

Answer(s): B

Explanation:

To support equal monthly installment payments over a defined period (in this case, 12 months), the product should be configured with a "Term Monthly" selling model. In Salesforce Subscription Management, selling models define the way a product is billed and consumed -- particularly whether it's sold as a one-time item, billed over a term, or on an ongoing (evergreen) basis.

The "Term Monthly" model means:

The product is sold with a defined term length (e.g., 12 months).

Billing occurs monthly, allowing installment-style payment plans.

The term and billing frequency are fixed, making it ideal for predictable revenue models like hardware installment plans.

The "Evergreen Monthly" model (option C) is used when the product does not have a fixed end date

-- common in SaaS or subscription services.

"Term Annual" (option A) implies an annual billing cycle, not suitable for monthly payments.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide ­ "Selling Models and Termed Products":

"Term Monthly allows a customer to commit to a product for a fixed period (e.g., 12 months) with recurring billing on a monthly basis. This model is commonly used for installment-based pricing."

CPQ Implementation Guide ­ "Selling Model Configurations":

"Assign the correct selling model to enable accurate pricing, billing frequency, and contract behavior based on the product type."


Reference:

Subscription Management Implementation Guide

Salesforce CPQ Implementation Guide



A Revenue Cloud Consultant needs to verify that the calculated prices on a quote match the pricing logic defined in the pricing procedure. The consultant has already reviewed the procedure steps and quote lines but suspects that a custom pricing script may be affecting the results.

What should the consultant do to trace the sequence of pricing actions and adjustments applied during quote calculation?

  1. Check the Pricing Operations Console.
  2. Check the Revenue Transaction Logs.
  3. Check the Pricing Debug Mode Output.

Answer(s): C

Explanation:

When validating the accuracy of quote pricing -- especially in the presence of custom pricing scripts or logic -- the recommended method is to enable and review the Pricing Debug Mode Output. This tool allows consultants and developers to trace all pricing operations step-by-step, including:

Price calculation sequence

Adjustments applied by pricing rules

Scripting logic execution (e.g., custom logic in Pricing Hooks)

Procedure steps execution order

According to the Salesforce CPQ Implementation Guide, Pricing Debug Mode is critical for diagnosing pricing anomalies, particularly in complex CPQ setups involving custom scripts or layered pricing rules.

The Pricing Operations Console (option A) is useful for managing pricing procedures and viewing applied logic but does not provide a line-by-line trace of what happened during the quote calculation.

Revenue Transaction Logs (option B) are primarily used in Billing and Invoicing scenarios, not for quote pricing diagnostics.

Exact Extracts from Salesforce Revenue Cloud Documents:

Salesforce CPQ Implementation Guide ­ "Debugging Pricing Procedures":

"Use Pricing Debug Mode to track the execution of pricing steps, logic hooks, and adjustments. This is the most detailed method to investigate discrepancies in pricing outcomes."

Developer Guide ­ "Pricing Engine Customization and Debugging Tools":

"Enable Pricing Debug Mode in the Quote Calculator Plugin to view the complete breakdown of calculations and custom logic applied."


Reference:

Salesforce CPQ Implementation Guide

Salesforce CPQ and Billing Developer Guide

Revenue Cloud Advanced Pricing Tools Documentation



A Billing Operations user at Universal Containers needs the system to automatically generate invoices every Monday at 6:00 AM for all completed billing schedules from the past week.

How should the user configure this automation in Billing?

  1. Define a Billing Treatment that references an Invoice Generation Time field at the product level.
  2. Schedule a Recurring Invoice Run with a Weekly frequency and 6:00 AM start time.
  3. Create a custom flow that runs nightly and generates invoices using the Invoice Preview feature.

Answer(s): B

Explanation:

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."


Reference:

Salesforce Billing Implementation Guide

Salesforce Revenue Cloud Operations Guide

Billing Setup & Automation Best Practices



A hardware company sells bundles that consist of commercial products. All products are required to be shipped, and they have a corresponding technical product called 'Shipping Service'. For some of the company's customers, multiple instances of fulfillment products are generated. The fulfillment designer does not want to ship each of those commercial products separately.

What should the Decomposition Scope be for all these products to allow all products to ship together?

  1. Account
  2. Order
  3. Bundle

Answer(s): B

Explanation:

In Salesforce Revenue Cloud's Subscription Management and Order Fulfillment framework, Decomposition Scope determines how fulfillment requests are grouped during the decomposition process. If the goal is to group multiple commercial products (and their technical/fulfillment counterparts) from different bundles within the same order into a single shipment, the appropriate scope is "Order".

Using Order-level Decomposition Scope ensures that all applicable products within the same order are processed as a single unit for fulfillment, which is ideal when shipping coordination is needed across bundles or product lines. This avoids generating multiple shipments for each product or bundle, thereby streamlining logistics and enhancing customer experience.

Option C (Bundle) would result in decomposition happening separately per bundle, leading to multiple fulfillment requests -- contrary to the requirement.

Option A (Account) is too broad and may introduce unrelated products into the same fulfillment group, which is not desirable.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide ­ "Decomposition Scope Settings":

"The decomposition scope determines the grouping of products for fulfillment. Setting the scope to 'Order' allows all decomposable products in an order to be grouped into a single fulfillment request."

Order Management Configuration Guide ­ "Controlling Decomposition and Fulfillment":

"Use `Order' as the decomposition scope to consolidate fulfillment for all products in the same order, even if they are from different bundles."


Reference:

Subscription Management Implementation Guide

Salesforce Order Management Configuration Guide

Revenue Cloud Fulfillment Architecture Notes



A new product administrator has been tasked with managing the product catalog for their company. They can view product records in the catalog but can't make any edits.

What should a consultant do to fix this issue?

  1. Add the administrator to the Product Management Queue.
  2. Grant the Modify All Data permission on the Product object for the administrator.
  3. Assign the Product Catalog Management Designer permission set license to the administrator.

Answer(s): C

Explanation:

In Salesforce Revenue Cloud, the ability to manage product records within the product catalog is governed by specific permission sets and licenses. If a user can view but not edit product records,

they likely lack the proper Permission Set License (PSL) required to perform product catalog modifications.

The correct solution is to assign the Product Catalog Management Designer permission set license, which enables users to:

Create and update product records

Manage attributes, configurations, and pricing

Work with product relationships and dependencies

According to the Salesforce CPQ Implementation Guide, this permission set is essential for users responsible for catalog operations.

Option A (Product Management Queue) is unrelated to user permissions.

Option B (Modify All Data) is overly permissive and not best practice for security and data integrity; it grants unrestricted access to all objects, which is not necessary.

Exact Extracts from Salesforce Revenue Cloud Documents:

CPQ Implementation Guide ­ "User Permissions for Product Management":

"Assign the Product Catalog Management Designer permission set license to users responsible for managing product and pricing records. This license includes edit access for key product catalog components."

Revenue Cloud Admin Guide ­ "Setting Up Product Catalog Roles":

"Use the appropriate PSL to ensure least privilege while granting catalog modification capabilities."


Reference:

Salesforce CPQ Implementation Guide

Salesforce Revenue Cloud Admin Guide

Salesforce Permission Set License Reference Documentation






Post your Comments and Discuss Salesforce Rev-Con-201 exam dumps with other Community members:

Join the Rev-Con-201 Discussion