Salesforce REV-CON-201 Online Practice Questions and Exam Preparation

Salesforce REV-CON-201 Online Questions & Answers

• Question 161:

  A business user wants to use advanced Revenue Cloud capabilities to gain a comprehensive view of the company's financial health, from initial quote to final cash collection. They need to track sales performance, forecast revenue, and monitor customer trends.

  Which Revenue Cloud reporting feature should the business user use?

  A. Pricing Operations Console
  B. Revenue Management Intelligence
  C. Revenue Lifecycle Management
  B. Revenue Management Intelligence

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Revenue Management Intelligence (RMI) is Salesforce's analytics and insights layer for Revenue Cloud.

  Documentation describes it as providing: End-to-end Quote-to-Cash analytics, including quoting, orders, billing, and payments. Dashboards for sales performance, revenue forecasts, and customer behavior. Pre-built and customizable KPIs across the revenue lifecycle. Pricing Operations Console (A) focuses on pricing operations, not full Q2C analytics. Revenue Lifecycle Management (C) is the product suite itself, not a reporting feature.

  References:

  Revenue Management Intelligence Guide - Overview and Use Cases Revenue Cloud Product Documentation - Analytics for Quote-to-Cash

• Question 162:

  During a transaction, which capability does the Transaction Line Editor provide?

  A. Drag to Sort
  B. Filtering
  C. Auto Save Changes
  B. Filtering

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: The Transaction Line Editor (TLE) supports: Column filtering and sorting.

  Inline editing and recalculation.

  Manual save actions.

  There is no "drag to sort" capability (A). Changes are not auto-saved (C); users must explicitly save.

  References:

  Revenue Lifecycle Management Implementation Guide - Transaction Line Editor Features

• Question 163:

  A consultant is preparing to enable multicurrency in an org that already has active pricing procedures linked to predefined Salesforce Pricing decision tables. The consultant notices that the Currency field is not available to select within the pricing procedure.

  What should the consultant do to resolve this?

  A. Clone the pricing procedure and create a new decision table with the Currency field. Link the new table to the cloned procedure and swap it into setup.
  B. Deactivate the pricing procedure and the associated decision table, then enable multicurrency and add the Currency field to the decision table before reactivating them.
  C. Enable multicurrency in the org, then wait a few minutes for the Currency field to become available for use in the pricing procedure and related decision tables.
  B. Deactivate the pricing procedure and the associated decision table, then enable multicurrency and add the Currency field to the decision table before reactivating them.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: For Revenue Cloud's

  Salesforce Pricing: The Currency field becomes available for use in decision tables and pricing procedures only after multicurrency is enabled.

  If a decision table and pricing procedure are already active, you must deactivate them, update the table to include Currency, and then reactivate. Simply waiting (C) will not retroactively expose Currency in existing decision tables. Cloning (A) is unnecessary and more complex than required.

  References:

  Salesforce Pricing / Revenue Lifecycle Management Implementation Guide - Multicurrency Enablement and Pricing Procedures Decision Table Configuration Steps for Currency-based Pricing

• Question 164:

  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?

  A. $9,900
  B. $9,500
  C. $1,800
  A. $9,900

  ---

  Explanation

  Comprehensive and Detailed Explanation 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.

  References:

  Revenue Lifecycle Management / Salesforce Pricing Guide - Pricing Element Order and Net Price Calculation

• Question 165:

  A Revenue Cloud Consultant needs to create a dynamic product bundle where the available options and default selections are determined by the customer's industry, a field stored on the parent Opportunity record.

  How should the consultant achieve this?

  A. By using a before-save flow on the Quote object to validate the product selections against the Opportunity's industry field to prevent an invalid configuration from being saved
  B. By creating a Product Configuration Rule that reads the Opportunity's industry field and applies the logic before the configurator UI loads, and ensures that all actions are executed
  C. By defining a context-aware rule using the Constraint Model that references the Opportunity's industry field to enforce product selection or set attribute values
  C. By defining a context-aware rule using the Constraint Model that references the Opportunity's industry field to enforce product selection or set attribute values

  ---

  Explanation

  Explanation (150-250 words) In Salesforce Revenue Cloud, when product bundle behavior must change dynamically based on contextual data (e.g., Opportunity or Account fields), the correct approach is to use context-aware Constraint Models. Constraint Models can reference context attributes, such as the Industry field from the parent Opportunity, to dynamically control which product options are available or preselected during bundle configuration. This approach ensures the configurator UI loads with the correct options and default selections without additional automation or UI components. The logic resides in the Constraint Model, which can define inclusion, exclusion, or recommendation rules that evaluate the context in real time. Flows or configuration rules (like option B) don't have direct access to Opportunity context within the configurator session; Constraint Models are specifically designed for contextual, attribute-driven logic.

  Exact Extract from Salesforce CPQ Implementation Guide: "Constraint Models can reference contextual data from related records such as Opportunity, Account, or Quote to drive dynamic product configuration behavior."

  References: Salesforce CPQ Implementation Guide - Constraint Models and Context Awareness Salesforce Revenue Cloud Developer Guide - Contextual Attributes in Product Configuration Salesforce CPQ Best Practices - Dynamic Bundling Based on Context Data

• Question 166:

  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?

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

  ---

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

  References: Salesforce Billing Implementation Guide Salesforce Revenue Cloud Operations Guide Billing Setup & Automation Best Practices

• Question 167:

  A Revenue Cloud project requires that a contract agreement dynamically hide or show clauses based on Account-specific fields.

  Which token should the implementation consultant use on the document template to show the appropriate clauses at runtime?

  A. Variable tokens
  B. Conditional evaluation tokens
  C. Repeating content tokens
  B. Conditional evaluation tokens

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: In Revenue Cloud CLM /

  DocGen: Conditional evaluation tokens are used to conditionally include or exclude sections or clauses based on data (for example, Account fields, contract fields). They evaluate conditions at generation time and determine whether a clause block is rendered. Variable tokens (A) insert values but do not control visibility. Repeating content tokens (C) are used for lists or repeated items, not conditional visibility.

  References:

  Document Template & Clause Authoring Guide - Conditional Tokens for Dynamic Clauses

• Question 168:

  A consultant is setting up a new product in the product catalog. They already created a Product Classification and a set of Product Attributes, but the attributes are not appearing when viewing the product in the workspace.

  What is the cause of this error?

  A. The consultant did not activate the attribute group in the Product Workspace.
  B. The consultant forgot to publish the product in the product catalog.
  C. The consultant did not assign the attributes to the Product Classification.
  C. The consultant did not assign the attributes to the Product Classification.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract:

  In Product Catalog Management: Product Attributes are associated to Product Classifications (or attribute groups tied to them). When a product is linked to a classification, only attributes assigned to that classification appear in the workspace. If attributes are defined but not assigned to the Product Classification, they won't show up on products using that classification. Publishing (B) affects availability, not attribute visibility. Attribute group activation (A) is not the core requirement if the attribute-classification link is missing.

  References:

  Product Catalog Management Implementation Guide - Linking Attributes to Product Classifications

• Question 169:

  Universal Containers (UC) sells its products and services to other businesses, and provides an automatic discount to businesses that buy in bulk. UC is now expanding its selling channels and plans to sell directly to end users. A key requirement is to ensure that bulk discounts are only applicable to businesses and not individual buyers.

  How should the Revenue Cloud Consultant solve this requirement?

  A. By using Quote Transaction Type and Volume-Based Pricing
  B. By using Sales Transaction Type and Volume-Based Pricing
  C. By using Order Transaction Type and Volume-Based Pricing
  B. By using Sales Transaction Type and Volume-Based Pricing

  ---

  Explanation

  "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

• Question 170:

  In Salesforce Revenue Cloud, what is the primary role of Context Service in optimizing revenue operations?

  A. To automate the generation of official sales contracts and essential service agreements
  B. To provide and manage the relevant data inputs and variables required for transactional calculations
  C. To streamline the precise creation and management of product catalogs and bundles
  B. To provide and manage the relevant data inputs and variables required for transactional calculations

  ---

  Explanation

  Explanation (150-250 words)

  The Context Service in Salesforce Revenue Cloud serves as a foundational service layer that centralizes and manages the data inputs, parameters, and contextual variables used in transactional processes across CPQ, Billing, and Subscription Management. Its core role is to ensure that every transaction-such as pricing, billing, revenue recognition, and tax calculation-operates with accurate, synchronized data context. When a quote, order, or invoice is processed, the Context Service dynamically supplies key contextual data (like currency, account, tax jurisdiction, pricing date, and contractual terms) to ensure consistent calculations and business logic across different Revenue Cloud services. By doing so, it enables unified pricing and billing behavior and eliminates discrepancies that could occur from fragmented data sources. Exact Extract from Salesforce Revenue Cloud Platform Concepts: "Context Service provides the foundational context for transactional services in Revenue Cloud. It manages and distributes contextual data, such as customer, pricing, and tax parameters, enabling accurate calculations across CPQ, Billing, and Subscription Management."

  References: Salesforce Revenue Cloud Platform Concepts - Context Service Overview Salesforce CPQ and Billing Integration Guide - Context Service Data Flow Subscription Management Implementation Guide - Transaction Context Handling