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

Salesforce REV-CON-201 Online Questions & Answers

• Question 171:

  A Revenue Cloud Consultant wants to customize the Transaction Line Editor to display an existing custom field, Estimated Delivery Date, for sales reps when they are working on Quote record pages.

  What is the correct method to achieve this customization?

  A. Add Estimated Delivery Date as a selected field to the Transaction Line Editor component in the Quote Lightning Record page.
  B. Enable 'Instant Pricing' under Revenue Settings to automatically display all custom fields on the Transaction Line Editor.
  C. Add the Estimated Delivery Date field to the relevant Quote Line Item page layout to display the field in the Transaction Line Editor.
  A. Add Estimated Delivery Date as a selected field to the Transaction Line Editor component in the Quote Lightning Record page.

  ---

  Explanation

  Explanation (150-250 words)

  The Transaction Line Editor (TLE) in Salesforce Revenue Cloud provides a configurable grid interface for users to interact with Quote Line Items (QLIs). To display custom fields such as Estimated Delivery Date, administrators must explicitly add those fields to the Selected Fields list of the TLE component within the Quote Lightning Record Page.

  This configuration determines which fields appear in the line editor and in what order. Adding fields to the Quote Line Item page layout (option C) does not affect TLE visibility because the TLE configuration operates independently of page layouts.

  Option B (enabling.

  Instant Pricing) controls pricing recalculation frequency and is unrelated to UI field visibility.

  Exact Extract from Salesforce CPQ Implementation Guide: "To display a custom field in the Transaction Line Editor, add it as a selected field in the TLE component configuration on the record page where it appears."

  References: Salesforce CPQ Implementation Guide - Transaction Line Editor Customization Salesforce Revenue Cloud Configuration Guide - TLE Field Selection and Layout Management Salesforce Solution Architect Handbook - Optimizing Line Editor User Experience

• Question 172:

  A consultant is tasked to create an advanced decision table that will provide a discount % as output based on the following scenario. The discount is eligible for Partner accounts where they have products ordered in quantities greater than 100, or if customers order an accessory in quantities greater than 100.

  Conditions:

  Account Source = Partner

  Ordered Quantity > 100

  Product Category = Accessory

  While defining the conditions during the creation of a decision table, how should the consultant configure the table to satisfy the conditions above?

  A. Condition Type = Custom Logic & Custom Logic = (1 OR 2) AND (2 AND 3)
  B. Condition Type = Custom Logic & Custom Logic = (1 AND 2) OR (2 AND 3)
  C. Condition Type = All conditions are met (AND) & Custom Logic = 1 AND 2 AND 3
  B. Condition Type = Custom Logic & Custom Logic = (1 AND 2) OR (2 AND 3)

  ---

  Explanation

  Explanation (150-250 words)

  The scenario describes two possible discount triggers: Condition 1: Partner accounts with orders above 100 units # (1 AND 2) Condition 2: Customers ordering accessories above 100 units # (2 AND 3) To model this in a decision table, the consultant should choose Condition Type = Custom

  Logic and define the logical expression as (1 AND 2) OR (2 AND 3). This expression ensures the decision table returns a discount whenever either condition group is met.

  Option A incorrectly mixes unrelated logical paths and would not isolate the two valid scenarios.

  Option C would require all three conditions to be true simultaneously, which contradicts the "or" requirement.

  Exact Extract from Salesforce Pricing and Decision Framework Guide: "When multiple conditional paths can trigger an output, use Custom Logic and define a Boolean expression such as (1 AND 2) OR (2 AND 3). The decision table evaluates true if any path meets the condition."

  References: Salesforce Revenue Cloud Pricing Implementation Guide - Decision Table Conditions and Custom Logic Salesforce CPQ Advanced Rules Framework - Custom Logic Syntax Salesforce Pricing Engine Developer Guide - Conditional Evaluation Behavior

• Question 173:

  A customer is delinquent on their payments.

  How should a Revenue Cloud Consultant stop invoicing the customer's account?

  A. Assign themselves the Billing Administrator permission set, navigate to Scheduled Jobs, and delete the invoice scheduler's scheduled jobs.
  B. Assign themselves the Billing Operations User permission set, go to the customer's account, and delete their related pending invoices.
  C. Assign themselves the Billing Administrator permission set, go to the customer's account, and use the Suspend Billing button.
  C. Assign themselves the Billing Administrator permission set, go to the customer's account, and use the Suspend Billing button.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Salesforce Billing includes a Suspend Billing feature that stops invoice generation for an account.

  From Salesforce Billing Implementation Guide: "Use Suspend Billing on the Account to pause invoicing for customers who are delinquent or temporarily blocked." "This prevents future invoices without modifying global schedulers or deleting invoice records." Option A would halt invoicing for all customers.

  Option B removes existing invoices but does not stop future ones.

  References:

  Salesforce Billing Implementation Guide - Suspend Billing

  Account Billing Controls.

• Question 174:

  On the final day of User Acceptance Testing (UAT), a critical issue is discovered. The tester believes the critical issue is a bug, while the developer asserts it is working as designed. The business representative suspects a training issue, and the project manager views the critical issue as scope creep.

  What is the next course of action to mitigate this critical issue?

  A. All involved parties should review the issue, cross-referencing against the approved business requirements, and collaboratively determine if it is a legitimate defect, a training gap, or a new requirement.
  B. Escalate the issue to the steering committee and request an exception to deploy the solution as is; given that it is the final day of UAT, there is no time remaining for further review.
  C. The consultant should review the critical issue, perform root cause analysis, reproduce the issue in the development sandbox, fix it to maintain the go-live date, and deploy it to UAT.
  A. All involved parties should review the issue, cross-referencing against the approved business requirements, and collaboratively determine if it is a legitimate defect, a training gap, or a new requirement.

  ---

  Explanation

  In Salesforce Revenue Cloud implementations, especially during User Acceptance Testing (UAT), it is common to encounter discrepancies in expectations versus system behavior. When stakeholders disagree on the nature of a critical issue

  - whether it is a defect, scope change, or training gap - the correct course of action is to collaboratively review the issue against the signed-off business requirements. Per the Salesforce Implementation Best Practices, a triage meeting or working session involving the tester, developer, business stakeholder, and project manager should be conducted to:

  Review the documented business requirements and use cases Evaluate whether the issue represents a missed requirement, a misunderstanding, or a training need Reach consensus on how to classify and resolve the issue

  Option A reflects this structured and collaborative approach.

  Option B is premature escalation without due diligence and can lead to bypassing quality assurance.

  Option C assumes the issue is a bug and skips the critical validation and stakeholder agreement process, risking scope deviation or misalignment.

  Exact Extracts from Salesforce Revenue Cloud Documents: Salesforce Partner Implementation Guide - "Managing UAT and Defect Triage":"Conduct issue triage sessions with key stakeholders to determine if findings are bugs, enhancements, or training gaps. Always align resolution path with documented requirements." Revenue Cloud Delivery Framework - "Final UAT and Go-Live Readiness":"Do not assume issue type. Instead, validate all critical issues with documentation and team consensus."

  References: Salesforce Partner Implementation Guide Revenue Cloud Delivery Framework Salesforce Project Governance and UAT Checklist

• Question 175:

  A Billing Operations user needs to capture customer credits during negative amends and cancellations to represent a negative invoice balance. This information will be reused later for settling invoices before processing payments.

  Which Revenue Cloud capability should the Billing Operations user use to do this?

  A. Debit Memo
  B. Cash Memo
  C. Credit Memo
  C. Credit Memo

  ---

  Explanation

  Explanation (150-250 words)

  In Salesforce Billing, a Credit Memo is used to record and manage customer credits resulting from negative transactions-such as cancellations, returns, or amendments that reduce invoiced amounts. When a negative amend or cancellation occurs, Salesforce Billing automatically generates Credit Memo Lines to represent the negative value associated with the customer's account balance. Credit Memos serve multiple purposes: they reflect negative invoice balances, adjust billing records, and can later be applied to open invoices to offset charges or prepare the account for payment settlement. This ensures financial accuracy while maintaining a clear audit trail for adjustments. By contrast, Debit Memos represent additional charges to customers, while Cash Memos are related to direct cash entries and do not manage negative invoice balances.

  Exact Extract from Salesforce Billing Implementation Guide: "A Credit Memo is used to record and manage customer credits resulting from negative transactions such as cancellations, refunds, or adjustments. These credits can be applied to open invoices or retained for future settlements."

  References: Salesforce Billing Implementation Guide - Credit and Debit Memo Management Salesforce Revenue Cloud Billing Data Model - Credit Memo and Invoice Relationships Salesforce Billing Operations Guide - Refunds and Credits Workflow

• Question 176:

  After activating an order for a usage-based analytics subscription, a billing specialist wants to confirm that the system has generated the necessary components to support usage tracking, entitlement enforcement, and billing readiness.

  Which set of records is created automatically as part of the usage management process?

  A. Asset, Entitlement Policy, Wallet
  B. Product Consumption Summary, Rate Adjustment Entry, Billing Event
  C. Usage Entitlement Account, Usage Entitlement Bucket, Wallet
  C. Usage Entitlement Account, Usage Entitlement Bucket, Wallet

  ---

  Explanation

  Explanation (150-250 words)

  When a usage-based subscription is activated in Salesforce Billing or Subscription Management, the system automatically generates a hierarchy of records that support usage tracking, entitlement enforcement, and billing readiness.

  These include:

  Usage Entitlement Account (UEA): Identifies the customer's entitlement context for usage collection.

  Usage Entitlement Bucket (UEB): Stores individual usage events or quantities accumulated for a given period and product.

  Wallet: Tracks prepaid balances or usage credits and integrates with rating and billing to manage consumption and renewals.

  This structure ensures all usage data is captured, rated, and invoiced accurately according to entitlements.

  Option A represents general asset and entitlement records but not specific usage entities.

  Option B lists derived financial records, not the foundational usage structures. Exact Extract from Salesforce Billing Implementation Guide: "Upon activation of a usage-based order product, Salesforce Billing creates a Usage Entitlement Account, Usage Entitlement Bucket, and Wallet to support usage capture, entitlement enforcement, and billing integration."

  References: Salesforce Billing Implementation Guide - Usage Management Overview Salesforce Revenue Cloud Data Model - Usage Entitlement Entities Salesforce Subscription Management Implementation Guide - Wallet and Usage Tracking

• Question 177:

  A business is undergoing a digital transformation. As part of the process, sales leadership wants the contracting process fully digitized, including clause generation, redlining, e-signature, and related activities.

  Which capability should the implementation consultant use?

  A. Salesforce Contracts Connector for Word
  B. OmniStudio Document Generation
  C. Document Builder
  A. Salesforce Contracts Connector for Word

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Salesforce Revenue Lifecycle Management provides a modern contract lifecycle management experience using Salesforce Contracts Connector for Word, which enables: Contract document generation Clause insertion and management Redlining within Microsoft Word Integration with e-signature providers Tracking and syncing changes back to Salesforce From the RLM Implementation Guide: "Salesforce Contracts Connector for Word allows users to generate agreements, manage clauses, and perform redlining directly within Microsoft Word." "Supports digital negotiation workflows and integrates with DocGen and e-signature."

  Why other options are incorrect: OmniStudio Document Generation is a legacy document output tool and does not support clause redlining or contracting workflows. Document Builder (older CPQ add-on) does not provide full CLM capabilities such as clause libraries, redlining, or negotiations.

  References:

  Salesforce Revenue Lifecycle Management Implementation Guide - Contract Lifecycle Management Contracts Connector for Word.

• Question 178:

  A sales rep at an SaaS company observes that a recent renewal quote for a premium software subscription, which includes several add-on modules and usage-based tiers, is displaying an unexpected total price. The customer is disputing the amount, stating it is higher than anticipated based on their contracted terms. The pricing consultant suspects an issue with how the pricing rules are being applied.

  What is the first diagnostic step the consultant should take to investigate the pricing calculation?

  A. Manually adjust the disputed total price on the quote to the customer's anticipated amount.
  B. Deactivate the entire pricing procedure and then reactivate it to force a re-evaluation.
  C. Use the pricing procedure's Simulate functionality to trace the price waterfall.
  C. Use the pricing procedure's Simulate functionality to trace the price waterfall.

  ---

  Explanation

  Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and CPQ Implementation Guides): "The Simulate feature in the pricing procedure enables administrators to execute and trace the pricing calculation logic to identify where pricing rules, conditions, or adjustments are applied." "Using simulation, consultants can visualize the price waterfall and confirm whether attribute-based, tier-based, or contract-based adjustments are contributing to the final price." "This is the recommended first diagnostic step when pricing discrepancies are reported."

  Step-by-Step Reasoning:

  Issue: Discrepancy between expected and calculated renewal quote prices.

  Correct Action: Use Simulate to run the pricing engine in diagnostic mode and examine the price waterfall. Why C is Correct: Allows tracing rule application order and effective discounts. Identifies where unexpected conditions or overrides occurred.

  Why Others Are Incorrect:

  A: Manual edits mask the issue rather than diagnose it.

  B: Deactivating/re-enabling does not reveal rule logic; it risks production disruption.

  References:

  Salesforce CPQ Implementation Guide - Pricing Procedures and Price Simulation Salesforce Subscription Management Implementation Guide - Pricing Debugging Tools and Price Waterfall Analysis

• Question 179:

  A customer uses a price book to populate list prices. They need to override the list price by 10% if the product is being sold in an emerging market. The emerging market is identified on the quote via a custom field.

  What should a pricing designer do to solve this?

  A. Use a formula-based pricing element to apply an override to the list price and use that to populate the list price for further calculations like total, discount, net prices, etc.
  B. Use a formula-based pricing element to apply the override to the unit price and use that to populate the list price for further calculations like total, discount, net prices, etc.
  C. Use a formula-based pricing element to apply an override to the list price value and populate a line item custom field for further calculations like total, discount, net prices, etc.
  A. Use a formula-based pricing element to apply an override to the list price and use that to populate the list price for further calculations like total, discount, net prices, etc.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract:

  In Salesforce Pricing (Revenue Cloud): List Price is typically derived from the price book entry. A formula-based pricing element can override the list price based on conditions (such as a custom "Emerging Market" flag on the quote).

  Downstream pricing steps (discounts, totals, net prices) use this adjusted list price as the base. Option A matches the documented pattern: override the list price using a formula element.

  Option B confuses unit price vs list price as the base.

  Option C puts the override into a custom field, which then would require additional custom logic for subsequent pricing steps.

  References:

  Salesforce Pricing / Revenue Lifecycle Management Guide - Formula-Based Pricing Elements

  List Price Overrides

• Question 180:

  A furniture company is selling unassembled furniture with user manuals. The company does not want to show user manuals as a quote line when selling to customers, but it needs to make sure user manuals are included when shipping the unassembled furniture.

  What is the recommended approach?

  A. Add the user manuals as quote line, but hide them in the Transaction Line Table and proposal document.
  B. Add the user manuals as an attribute with a value of Included or Excluded under the unassembled furniture product record.
  C. Add the user manuals as a technical product and create associated decomposition rule(s).
  C. Add the user manuals as a technical product and create associated decomposition rule(s).

  ---

  Explanation

  The recommended approach uses technical products with decomposition rules. According to Revenue Cloud fulfillment documentation, technical products are purpose-built for fulfillment and operational processes rather than commercial sale. User manuals in this scenario should be configured as technical products that accompany the commercial unassembled furniture product but are not visible as separate quote lines to customers. Decomposition rules govern how commercial products (the unassembled furniture) break down into fulfillment components when an order is activated. By creating a technical product called "User Manual Inclusion" and establishing decomposition rules that link it to the furniture product, the system ensures that when an unassembled furniture order is created and activated, the decomposition process automatically includes the user manual technical product in the fulfillment decomposition. This approach provides several advantages: customers see only the furniture product in their quote (not the manual as a separate line item), but during order fulfillment, the decomposition rules ensure that user manuals are included in the shipping package.

  Technical products do not appear in quoting interfaces, so they remain hidden from customer-facing documentation and proposals while still participating in fulfillment operations.

  Option A (hiding quote lines) is not recommended because it adds unnecessary complexity to quotes and can cause confusion.

  Option B (attributes) doesn't support the fulfillment requirement; attributes describe product features, not orchestrate separate fulfillment items. Technical products with decomposition rules is the purpose-built Revenue Cloud mechanism for handling fulfillment-only items that shouldn't appear as commercial line items.

  References:

  Revenue Cloud Fulfillment Documentation - Technical Products and Decomposition Rules, Dynamic Revenue Orchestrator decomposition configuration