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

Free Salesforce Rev-Con-201 Exam Questions

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?

  1. Modify the contract extraction template to define the attribute mapping and context mapping for payment method.
  2. Modify the AI prompt template to define the attribute mapping and context mapping for payment method.
  3. Log a support case with Salesforce to enable payment method to be added to the extraction mapping used.

Answer(s): A

Explanation:

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.


Reference:

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's uniform order treatment leads to delays and errors in tailored delivery. UC needs to break down these complex orders, apply custom fulfillment plans for each distinct product, and ensure a tailored delivery experience.

Which Revenue Cloud capability should solve UC's problems with accurate order fulfillment?

  1. Dynamic Revenue Orchestrator (DRO)
  2. Salesforce Experience Cloud for customer portals
  3. Product Configurator

Answer(s): A

Explanation:

The Dynamic Revenue Orchestrator (DRO) in Salesforce Revenue Cloud enables organizations to create intelligent, rule-based orchestration flows that manage complex order-to-revenue processes. It allows consultants and admins to define custom fulfillment logic for different product types--such as hardware, software, or service components--ensuring that each item follows the correct process from order creation to fulfillment.

Exact Extract from Salesforce Revenue Cloud Documentation:

"Dynamic Revenue Orchestrator (DRO) provides a flexible orchestration framework that breaks down complex orders into fulfillment work items. Each work item can follow customized fulfillment, billing, and invoicing rules based on the product type, ensuring accurate and efficient processing."

-- Salesforce Billing Implementation Guide (Order Management and DRO section)

By leveraging DRO, UC can decompose composite orders into discrete, manageable workflows tailored to each product's delivery needs.

Option B (Experience Cloud) supports external interactions but not fulfillment logic, while Option C (Product Configurator) manages product setup at quoting--not fulfillment orchestration.


Reference:

Salesforce Billing Implementation Guide ­ Dynamic Revenue Orchestrator

Salesforce Revenue Cloud Implementation Guide ­ Order Fulfillment and DRO

Salesforce Revenue Cloud Consultant Exam Guide



A company creates large quotes with hundreds of line items. These line items must be generated in a specific format for internal processing and presentation to the customer.

What should the sales reps use to generate these line items in the required format?

  1. Document Builder
  2. Custom Report
  3. OmniStudio Document Generation

Answer(s): A

Explanation:

Salesforce CPQ provides a powerful built-in tool called Document Builder for generating documents from quotes, particularly when dealing with a large volume of quote line items. Document Builder allows sales reps to design templates that reflect branding and formatting requirements, while also ensuring data consistency pulled directly from the quote and quote line item records.

According to the Salesforce CPQ Implementation Guide, Document Builder supports features such as:

Pagination for large quote tables.

Grouping and sorting of line items.

Conditional logic to display specific sections.

Merging quote-level and line-level fields dynamically.

This makes Document Builder the optimal and scalable solution for companies managing large quotes with hundreds of line items, as it is natively integrated with Salesforce CPQ and tailored for high-volume quoting use cases.

While OmniStudio Document Generation can be used across various Salesforce industries, it is typically more applicable in Salesforce Industries (Vlocity) implementations and not the default or recommended approach for standard Revenue Cloud customers. A Custom Report would not provide the flexible formatting, pagination, and quote-specific templating capabilities needed for such structured document output.

Exact Extracts from Salesforce Revenue Cloud Documents:

Salesforce CPQ Implementation Guide ­ "Quote Document Templates" Section:

"Document templates allow for the display of quote and quote line item data using merge fields and conditional formatting. Templates can be customized to handle large volumes of quote lines with repeating sections, grouping, and multi-page support."

Salesforce CPQ and Billing Developer Guide ­ "Generate Document API" Section:

"The Quote Document generation process supports dynamic data merging and formatting for internal and customer-facing documents."


Reference:

Salesforce CPQ Implementation Guide

Salesforce Billing Implementation Guide

Salesforce Revenue Cloud Product Documentation (Fall 2023 Release Notes)

Salesforce CPQ and Billing Developer Guide



A medical device company manages its product information across multiple disconnected systems. Product specifications are stored in a dedicated Product Information Management (PIM) system, pricing is maintained in complex spreadsheets managed by the finance team, and sellable part numbers (SKUs) are mastered in the company's Enterprise Resource Planning (ERP) system.

How should a solution architect use Revenue Cloud to solve the company's data synchronization problems and streamline the process from quote to ERP fulfillment?

  1. By establishing the Salesforce Product Catalog as the single source of truth for all commercial products, pricing, and bundle configurations, and ensuring that downstream ERP systems consume this data for order fulfillment
  2. By creating custom objects in Salesforce to replicate the data structure of the PIM and ERP systems, and writing custom Apex triggers to keep the three systems aligned
  3. By using an integration platform to sync data from the PIM, the pricing spreadsheets, and the ERP into Salesforce nightly, overwriting the Salesforce catalog each time

Answer(s): A

Explanation:

Salesforce Revenue Cloud recommends centralizing product, pricing, and configuration data within the Salesforce Product Catalog to act as the commercial system of record. This approach ensures that sales teams are quoting from a single, consistent catalog that reflects accurate SKUs, pricing, and configurations. According to the Revenue Cloud Implementation Guides, this centralized model supports seamless quoting, bundling, discounting, and automated order and contract generation -- all critical for streamlining the quote-to-cash process.

The ideal architectural approach is to establish Salesforce CPQ as the source of truth for all sellable items, with upstream data (e.g., from PIM and ERP systems) being normalized and integrated into the Salesforce Product Catalog, rather than allowing disparate systems to overwrite Salesforce data. This enables Salesforce to drive clean, validated quote generation, which can then be integrated downstream to ERP for fulfillment and invoicing.

Creating custom objects (as in option B) increases technical debt and complexity, while overwriting Salesforce data nightly (option C) introduces risk, latency, and data integrity issues.

Exact Extracts from Salesforce Revenue Cloud Documents:

Salesforce CPQ Implementation Guide ­ "Product Catalog Best Practices":

"Establish Salesforce CPQ as the system of record for commercial products, including pricing, configuration rules, and availability. Use integration tools to populate product and pricing data from upstream systems such as ERP or PIM, ensuring consistency across quoting and order fulfillment processes."

Subscription Management Implementation Guide ­ "Data Model Alignment and Synchronization":

"Ensure a single source of truth for product data by leveraging Salesforce's product and pricing model. External systems should consume rather than overwrite Salesforce product catalog information."

Billing Implementation Guide ­ "Integration Patterns for Order to Cash":

"Salesforce should act as the authoritative quoting engine and drive orders into ERP for fulfillment. Product and pricing data should be managed in Salesforce to maintain quoting integrity."


Reference:

Salesforce CPQ Implementation Guide

Salesforce Billing Implementation Guide

Subscription Management Implementation Guide

Revenue Cloud Architecture Best Practices (Fall 2023 Release Notes)



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



Viewing page 10 of 22
Viewing questions 73 - 80 out of 165 questions



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

Rev-Con-201 Exam Discussions & Posts