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

Salesforce REV-CON-201 Online Questions & Answers

• Question 131:

  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?

  A. Attribute-Based Price and Volume Discount
  B. Bundle-Based Price and Price Adjustment Matrix
  C. Bundle-Based Price and Product Selling Model
  B. Bundle-Based Price and Price Adjustment Matrix

  ---

  Explanation

  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.

  References:

  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

• Question 132:

  A product administrator notices that the price of a warranty product is not being calculated correctly. It should be calculated as 10% of another equipment product's list price, but only when the products are purchased together in the same quote or order. This calculation works correctly for other products, but not for this specific warranty product.

  How should the product administrator resolve this issue?

  A. Find the Derived Price element and add the appropriate input/output variables in the pricing procedure.
  B. Find the Derived Price record where Product = Warranty and set the Derived Pricing Scope to Transactional.
  C. Find the price book entry of the equipment product and enable the Is Derived checkbox.
  B. Find the Derived Price record where Product = Warranty and set the Derived Pricing Scope to Transactional.

  ---

  Explanation

  Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and Derived Pricing Documentation): "Derived Pricing allows a product's price to be calculated based on another product's price, either within the same quote or across transactions." *"The Derived Pricing Scope determines when and how the derived price is evaluated:

  Transactional: The derived price is calculated dynamically when both products are in the same quote or order.

  Global: The derived price references a price from the catalog or price book, not quote-specific."* "If the Derived Pricing Scope is not set to Transactional, product interdependencies within the same quote will not evaluate."

  Step-by-Step Reasoning:

  Scenario: Warranty should price dynamically based on another product in the same transaction.

  Root Cause: The Derived Pricing Scope on the warranty product is likely not set to Transactional. Solution: Update the Derived Price record for the warranty product # set Derived Pricing Scope = Transactional.

  Why B is Correct: Ensures the price is recalculated dynamically when the related product exists in the same quote/order.

  Why A & C are Incorrect:

  A: Variables in the pricing procedure define logic but not scope of calculation.

  C: "Is Derived" on price book entries flags derivation capability but not the transaction context for dynamic evaluation.

  References:

  Salesforce CPQ Implementation Guide - Derived Pricing Concepts and Scopes Salesforce Subscription Management Implementation Guide - Pricing Dependencies and Derived Price Records

• Question 133:

  What should a consultant use to create Renewal Opportunities and Quotes/Orders out of the box?

  A. Revenue Cloud Subscription Settings
  B. Renewal Flow Templates
  C. Managed Apex classes
  B. Renewal Flow Templates

  ---

  Explanation

  Renewal Flow Templates are the out-of-the-box solution for creating Renewal Opportunities and Quotes /Orders in Revenue Cloud. Salesforce provides prebuilt flow templates specifically designed to automate the renewal process without requiring custom development.

  According to Salesforce Help documentation on Flow Templates for Renewal Automation, Revenue Cloud includes the "Create and Update Renewal Opportunities" flow template. This template automatically creates renewal opportunities for forecasting purposes when assets are created, and keeps them synchronized when customers amend or cancel subscriptions. The flow template is triggered by platform events and uses standard Revenue Cloud invocable actions. The renewal flow templates utilize the InitiateRenewal invocable action, which is a standard out-of-the-box Apex action provided by Salesforce. This action can create either renewal quotes or renewal orders based on specified parameters, and it properly links these transactions to renewal opportunities for accurate forecasting. The flow templates handle the complexity of tracking asset end dates, calculating renewal amounts, and maintaining synchronization between assets and renewal opportunities.

  Option A (Revenue Cloud Subscription Settings) is a configuration area but does not directly create renewal opportunities or quotes.

  Option C (Managed Apex classes) would require custom development and is not the out-of-the-box approach. The Renewal Flow Templates provide a declarative, point-and-click solution that administrators can activate and customize using Flow Builder, making them the correct out-of-the-box tool for automating renewal opportunity and quote creation in Revenue Cloud.

  References:

  Salesforce Help - Flow Templates to Automate Renewal Opportunity Creation and Asset Renewal, Summer '25

  Release Notes for Revenue Cloud

• Question 134:

  A large enterprise customer, Universal Containers (UC), has negotiated a special, long-term agreement with a software vendor for its enterprise-wide licensing. This agreement includes custom pricing tiers, specific discounts that apply only to UC across various product families, and unique billing frequencies tied to UC's fiscal year. The sales team needs to ensure that all future quotes and orders for UC automatically reflect these pre-negotiated terms.

  How should the sales team consistently apply these specific pricing and billing conditions for UC?

  A. Use Discount Schedules on relevant products, with a Price Rule that applies these custom schedules only when UC is the designated account.
  B. Establish a dedicated price book for UC that is populated with UC's negotiated prices, and includes all custom rates and specific billing rules for its products.
  C. Create a Contracted Pricing record on the contract associated with the UC Account that details product-specific prices, tiered discounts, and special billing arrangements.
  C. Create a Contracted Pricing record on the contract associated with the UC Account that details product-specific prices, tiered discounts, and special billing arrangements.

  ---

  Explanation

  Contract Pricing in Revenue Cloud is the correct mechanism for managing long-term, negotiated customer-specific terms like those in UC's enterprise agreement. According to Salesforce Help documentation on "Contract Pricing in Revenue Cloud," Contract Pricing allows sales teams to negotiate and manage custom pricing agreements by creating Contract Item Prices and Price Adjustment Schedules tied to a specific contract. When UC signs their enterprise agreement, a Contract record is created and associated with the UC Account. The sales team then creates Contracted Pricing records within this contract, detailing all product-specific prices, tiered volume discounts, and special billing arrangements unique to UC. These contract-based pricing terms become "the negotiated contract prices for the customer" that Revenue Cloud applies to future transactions. When sales reps create future quotes or orders for UC, they can initiate them from the existing active contract using the "Start a New Quote or Order From a Contract" functionality. Revenue Cloud automatically applies the contract's negotiated prices and billing frequencies to all line items. Additionally, when amending or renewing UC's assets, the system maintains these contract-based pricing terms, ensuring consistency across the entire customer lifecycle. This approach supports UC's unique requirements: custom pricing tiers are defined in tiered volume adjustments on Contract Item Prices; specific discounts are captured in Price Adjustment Schedules; and billing frequencies tied to UC's fiscal year are configured at the contract level. All future transactions for UC automatically inherit these terms.

  Option A (Discount Schedules with Price Rules) applies broadly to any account and doesn't support customer-specific governance.

  Option B (Dedicated Price Book) lacks the flexibility for tiered billing and special terms. Contract Pricing is specifically designed for long-term, negotiated, customer-specific commercial agreements.

  References:

  Salesforce Help - Contract Pricing in Revenue Cloud, Manage Contract Pricing, Apply Contract Pricing.

  When You Amend or Renew Assets

• Question 135:

  A customer wants to change specific line items of the order after it has been submitted but before it has been fulfilled. The system administrator has granted permissions to allow the order management team to make this change, but they are unable to do so.

  What is the reason for this issue?

  A. The entire order is asseized.
  B. The entire order is activated.
  C. The entire order is decomposed.
  B. The entire order is activated.

  ---

  Explanation

  Salesforce Billing Implementation Guide - "Order Activation" section:"Once an order is activated, it is considered finalized and cannot be modified directly. Activated orders are used to generate invoices, fulfillments, and billing schedules. Any required changes must be made through amendments or new orders."

  Salesforce CPQ Implementation Guide - "Orders and Contracts" section:"After an order is activated, the order lines become read-only. Users can no longer edit the order or its line items. To change product quantities, pricing, or terms, use the amendment or change order process." Subscription Management Implementation Guide - "Order Lifecycle Management" section:"Activation transitions an order from a draft or submitted state into a locked state for processing. No direct modifications to order lines are permitted once activated."

  Step-by-Step Reasoning Understand the scenario:The order has been submitted and permissions were granted, but the team still cannot edit line items.

  Key factor:If an order is activated, its records (header and line items) become locked for billing and fulfillment synchronization. Why option B is correct:Activation locks the order, preventing direct edits. The only way to make changes post-activation is via amendments or change orders, not direct editing.

  Why A and C are incorrect:

  A (Asseized): Not a Salesforce term related to order lifecycle.

  C (Decomposed): Decomposition refers to fulfillment item breakdown, not a locking mechanism preventing edits.

  References:

  Salesforce Billing Implementation Guide - Order Activation and Amendment Management Salesforce CPQ Implementation Guide - Orders and Contracts Salesforce Subscription Management Implementation Guide - Order Lifecycle and Change Management

• Question 136:

  A cloud storage company offers a subscription service where customers pay a base platform fee plus usage-based charges. For an Enterprise tier, pricing varies by storage, data transfer, and API calls, with tiered pricing where rates decrease at higher volumes. The company needs an automated way to manage the entire lifecycle of consumption-based products.

  How should a solution architect use Revenue Cloud to meet this requirement?

  A. Build a custom solution with Apex and custom objects to store usage data and batch calculate charges.
  B. Use Digital Wallet Management Consumption to sell usage products and track drawdowns.
  C. Use Usage Management to automatically ingest, aggregate, and rate consumption data against the products and pricing schedules defined in the Salesforce Product Catalog.
  C. Use Usage Management to automatically ingest, aggregate, and rate consumption data against the products and pricing schedules defined in the Salesforce Product Catalog.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Revenue Cloud provides Usage Management, which fully supports usage-based pricing, rating, and invoicing.

  From the Subscription Management and Billing Implementation Guides: "Usage Management allows ingestion of raw usage records."

  "Usage data is aggregated, rated, and billed based on the product's rate plan." "Tiered pricing is supported natively through usage rate tiers." Option B refers to Digital Wallet, which is for prepaid drawdowns-not rating usage or supporting tiered charges.

  Option A is unnecessary because Salesforce provides end-to-end usage aggregation, rating, and billing out of the box.

  References:

  Salesforce Billing Implementation Guide - Usage Management

  Tiered Usage Pricing

  Rating Engine.

• Question 137:

  A sales rep creates a quote with a subscription product called 'Training' with a quantity of 50 and term of 1 year, followed by Order creation, activation, and assetization. The 'Training' asset is then amended on the same day to add eight more seats, followed by Order creation, activation, and assetization.

  How many records will be present for Training for each Asset Action and Asset State Period?

  A. Two Asset Actions and one Asset State Periods
  B. One Asset Actions and two Asset State Periods
  C. Two Asset Actions and two Asset State Periods
  C. Two Asset Actions and two Asset State Periods

  ---

  Explanation

  Explanation (150-250 words)

  In Salesforce Subscription Management and CPQ, Asset Actions and Asset State Periods track changes in asset quantity, pricing, and lifecycle states over time.

  When the initial order for "Training" is activated, Salesforce creates: One Asset Action for the creation (initial assetization).

  One Asset State Period representing the active subscription for 50 seats. When the same asset is amended later that day to add eight more seats (quantity change), Salesforce generates: A second Asset Action to record the amendment event (quantity increased by 8). A second Asset State Period to represent the new asset state (58 seats active). Each amendment creates a new Asset Action and corresponding State Period because Salesforce tracks historical lifecycle events for traceability, revenue recognition, and audit integrity. The original state remains closed as of the amendment date, and a new one begins immediately. Exact Extract from Salesforce Subscription Management Guide: "Each amendment or change event generates a new Asset Action and corresponding Asset State Period to represent the new effective asset configuration." References:

  Salesforce Subscription Management Implementation Guide - Asset Actions and State Periods Salesforce CPQ-Billing Integration Guide - Assetization Process Salesforce Revenue Cloud Data Model - Asset Lifecycle Tracking

• Question 138:

  A solution architect is leading a discovery session for a complex B2B company. The architect needs to align the product catalog structure to meet stakeholder needs. Each line of business has its own bundling logic, selling models, and approval requirements, but the executive team wants a unified catalog to support reuse, governance, and cross-selling.

  What should the solution architect do during the session to make sure the product catalog structure aligns with business needs?

  A. Lead with a shared catalog with reusable components, attributes, and selling models tailored per business need.
  B. Prioritize stakeholder preferences for custom bundles so each bundle independently supports different business units.
  C. Design multiple catalogs for each business unit to isolate business logic and reduce dependencies.
  A. Lead with a shared catalog with reusable components, attributes, and selling models tailored per business need.

  ---

  Explanation

  Explanation (150-250 words)

  In Salesforce Revenue Cloud, a unified catalog strategy promotes scalability, governance, and efficient cross-sell and upsell opportunities across business units. For large B2B enterprises with diverse product models, the best approach is to lead discovery with a shared catalog architecture using reusable components, shared attributes, and modular selling models that can be adapted per business line. This method ensures data consistency and allows governance teams to maintain a single source of truth for pricing, attributes, and approval logic-while still allowing flexibility for each line of business to define unique bundles or rules. Creating separate catalogs (option C) or fully independent custom bundles (option B) leads to duplication, inconsistent logic, and high maintenance.

  Exact Extract from Salesforce Revenue Cloud Catalog Management Guide: "A unified catalog with shared components and attributes enables governance, reuse, and consistent cross-selling while still allowing flexibility for business-specific selling models."

  References: Salesforce Revenue Cloud Catalog Management Guide - Unified Catalog Design Best Practices Salesforce CPQ Implementation Guide - Modular Product Architecture and Shared Attributes Salesforce Revenue Cloud Solution Architect Handbook - Catalog Governance and Scalability

• Question 139:

  A customer owned an asset for 2 years, from January 1, 2024, through December 31, 2025. The customer missed the January 1, 2026, renewal but now wants to renew starting February 1, 2026.

  What is the recommended approach?

  A. Use Override Renewal Term and provide the start date of February 1, 2026.
  B. Add the same asset as a new line on the renewal quote with a start date of February 1, 2026.
  C. Start a new initial sale with the same asset with a start date of February 1, 2026.
  A. Use Override Renewal Term and provide the start date of February 1, 2026.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Revenue Cloud renewal logic supports:

  Override Renewal Term to adjust renewal dates, even if the renewal date has been missed. Maintaining continuity of the subscription history while shifting the renewal period. Using Override Renewal Term with a new start date of February 1, 2026, is the recommended way to handle late renewals. Options B and C break the standard renewal link and treat it as a new sale, which is not ideal for lifecycle tracking.

  References:

  Revenue Lifecycle Management Implementation Guide - Renewal Management and Override Renewal Term

• Question 140:

  A critical manual review step in the order fulfillment process is designed to take up to 60 minutes. The company configures the system to trigger an alert if the task is not completed 15 minutes before its scheduled end.

  Based on this scenario, which key parameters were configured in the Dynamic Revenue Orchestrator (DRO) system to manage this SLA?

  A. Completion Deadline and Warning Interval
  B. Task Priority and Escalation Rule
  C. Estimated Duration and Jeopardy Threshold
  C. Estimated Duration and Jeopardy Threshold

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: In DRO, SLA and jeopardy management are typically driven by: Estimated Duration - how long a task is expected to take (e.g., 60 minutes). Jeopardy Threshold - when a task is considered at risk (e.g., 15 minutes before due time). These parameters enable jeopardy alerts and proactive management before SLA breaches. Completion Deadline / Warning Interval (A) and Task Priority / Escalation Rule (B) are more generic concepts and not the named DRO configuration parameters for this specific SLA pattern.

  References:

  Dynamic Revenue Orchestrator Guide - Jeopardy Management, Estimated Duration, and Thresholds