Rev-Con-201 Exam Questions 2026 – Practice Test with Answers

Explanation:
(150C250 words)
In Salesforce CPQ and Subscription Management, subscription cancellations cannot be backdated to a date earlier than the current date when the amendment or cancellation action is performed. This rule ensures data integrity between contracts, billing schedules, and revenue recognition.
In this case, the customer requested cancellation effective June 29, 2025, but the cancellation request was received on July 5, 2025. Salesforce enforces that the earliest possible effective date is the date the amendment or cancellation is executed―July 5, 2025―not any past date.
The only scenario where a contract can be canceled from the start date (June 20, 2025) is if the entire subscription term is voided before any billing or revenue recognition has occurred. Since the service was already active, that option isn’t valid.
Exact Extract from Salesforce Subscription Management Guide:
“Cancellations are effective on or after the date they are performed. Backdating cancellations before the current amendment date is not supported.”
Reference: Salesforce Subscription Management Implementation Guide ― Subscription Amendments and Cancellations
Salesforce CPQ Implementation Guide ― Amendment Rules and Effective Dates
Salesforce Revenue Cloud Contract Lifecycle Management ― Subscription Termination Behavior

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. Reference:
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

Explanation:
Exact Extracts from Salesforce Subscription Management Implementation Guide:
“Lot-based or As-is Renewals allow renewal quotes or orders to use the customer’s last negotiated pricing and quantities from existing assets.”
“This feature ensures that renewals reflect the same commercial terms from the current assets, even if list prices have changed.”
“Enabling As-is Renewal simplifies renewal creation and ensures pricing consistency for multi-term or upsold subscriptions.”

Explanation:
When using Product Catalog Management in Salesforce Revenue Cloud, visibility of products during quote creation (especially through Product Discovery) is controlled by the Context Definition. Contexts allow administrators to define when and for whom products are visible during the product selection process, based on criteria like sales channels, quote type, or other business rules.
If products are not appearing during quote preparation, it is often due to a missing or misconfigured context definition. Assigning the correct Context Definition in Product Discovery Settings ensures that products and bundles are available during quoting based on business logic.
Option A (selecting a selling model) affects how the product is priced and billed, but not its visibility.
Option B (pricing procedure) impacts price calculations, not product discovery or visibility.
Exact Extracts from Salesforce Revenue Cloud Documents:
CPQ Implementation Guide C “Product Discovery Configuration”:
“Ensure that context definitions are properly set so that products appear under the right conditions during quoting. Missing contexts will result in products not being visible to end users.”
Revenue Cloud Product Catalog Guide C “Using Context for Product Availability”:
“Context Definitions act as filters for product discovery. Without proper context mapping, products may not show up for selection.”
Reference: Salesforce CPQ Implementation Guide
Product Catalog Management Documentation
Revenue Cloud Product Discovery Settings Guide

Explanation:
In Salesforce Revenue Cloud’s Contract Lifecycle Management (CLM) module, Sections within a document template are the best tool for organizing complex content such as M&A contracts.
Sections help break large documents into logical parts, allowing contract designers to:
Insert reusable clauses
Manage conditional logic
Include dynamic tables or fields
Facilitate easier navigation and updates
As per the CLM Template Designer documentation, sections enable content modularity and simplify the process of customizing contracts for each client or scenario, particularly when dealing with large and complex documents.
Option A is too general ― “creating a structure” is achieved by using sections.
Option B refers to child templates, which are useful for reusability but are typically added within sections and do not provide layout or navigation benefits on their own.
Exact Extracts from Salesforce Revenue Cloud Documents:
CLM Implementation Guide C “Creating Structured Templates with Sections”:
“Use sections in your document templates to organize clauses, fields, and conditional content. Sections are the primary way to structure large and complex documents like M&A contracts.”
Contract Designer Admin Guide C “Best Practices for Document Layout”:
“Sections allow you to modularize the content and manage visibility, clause insertion, and layout more effectively.”
Reference: Salesforce Revenue Cloud CLM Implementation Guide
Contract Lifecycle Management Admin Guide
Template Designer Documentation