Prepare Rev-Con-201 Exam Questions [2026] Recently Updated Questions
Give push to your success with Rev-Con-201 exam questions
Salesforce Rev-Con-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
NEW QUESTION # 97
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?
- A. Modify the contract extraction template to define the attribute mapping and context mapping for payment method.
- B. Modify the AI prompt template to define the attribute mapping and context mapping for payment method.
- C. Log a support case with Salesforce to enable payment method to be added to the extraction mapping used.
Answer: 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.
References:
Salesforce Subscription Management Implementation Guide - Contracts AI Setup Salesforce Revenue Cloud Implementation Guide - Contract Extraction Templates Salesforce Revenue Cloud Consultant Study Guide
NEW QUESTION # 98
A Salesforce Developer is using Postman to retrieve a JSON response with Product2 IDs to develop a Lightning web component.
Which query parameters are valid when using the Products List (POST) API to retrieve a list of products for the component?
- A. Catalog IDs
ProductClassification IDs - B. Pricebook IDs
Catalog IDs
Category IDs - C. Product2 IDs
Catalog IDs
Category IDs
Answer: C
Explanation:
When using the Products List (POST) API in Salesforce Revenue Cloud, developers can query and filter the list of available products using specific supported parameters. According to the Salesforce Product Catalog and Discovery API documentation, the valid and commonly used filters for the Products List API include:
* Product2 IDs: to retrieve specific products directly by their ID
* Catalog IDs: to filter products based on a specific product catalog
* Category IDs: to filter products that belong to a particular category within a catalog This allows developers to fetch only relevant products for a specific UI component or experience, such as in a Product Discovery component or a custom Lightning Web Component (LWC).
Option B includes Pricebook IDs, which are not supported as filter parameters in the Products List API.
Pricebooks are used in pricing context but are not valid query parameters for this API endpoint.
Option C includes ProductClassification IDs, which are not supported directly in the POST filter payload of the Products List API.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Product Discovery API Developer Guide - "Products List (POST)":"Use Catalog IDs, Category IDs, and Product2 IDs as input filters in the POST request to retrieve relevant product records for discovery or display."
* Revenue Cloud API Reference - "Querying Product Records":"The Products List API supports filtering by catalog, category, and direct product identifiers. Pricebooks are not queryable through this API." References:
Salesforce Revenue Cloud Product Discovery API Guide
Product Catalog and Discovery Developer Documentation
Salesforce CPQ API Reference (Fall '23 and Spring '24 Releases)
NEW QUESTION # 99
What are the steps a user should take to Renew an Asset?
- A. Create Renewal Quote with Asset, Create Order, Activate Order
- B. Create Renewal Quote with Asset, Create Contract, Activate Contract
- C. Create Renewal Quote with Asset, Create Order, Create Contract
Answer: A
Explanation:
Explanation (150-250 words)
The Renewal process in Salesforce Revenue Cloud begins with creating a Renewal Quote based on existing Assets (representing active subscriptions or entitlements). The Renewal Quote inherits pricing, terms, and quantities from the current assets and allows for updates such as upsells or discounts.
Once the Renewal Quote is approved, it is converted into an Order, and upon Order activation, Salesforce automatically generates new Assets (and optionally renewal Contracts if managed through Subscription Management).
Therefore, the correct renewal flow is:
* Create Renewal Quote with linked Assets.
* Create Order from the Renewal Quote.
* Activate Order, triggering renewal assetization and lifecycle continuation.
Option A skips the order creation step, and option C incorrectly orders contract creation after the order but before activation.
Exact Extract from Salesforce Subscription Management Implementation Guide:
"Renewals begin with a renewal quote referencing active assets. When converted to an order and activated, Salesforce generates renewed assets and continues lifecycle tracking." References:
Salesforce Subscription Management Implementation Guide - Renewal Process Overview Salesforce CPQ Implementation Guide - Renewal Quotes and Orders Salesforce Revenue Cloud Data Model - Asset Lifecycle during Renewal
NEW QUESTION # 100
A Revenue Cloud requirement states that when the "Terabyte" Attribute of "Product A" is greater than 100, a warning message should appear.
How should a consultant address this in Revenue Cloud?
- A. Create a custom Lightning web component to validate the attribute quantity.
- B. Create a constraint rule in the Constraint Model at the Product Level.
- C. Create a constraint rule in the Constraint Model at the Quote Level.
Answer: B
Explanation:
Explanation (150-250 words)
In Salesforce CPQ, Constraint Models define validation, inclusion, and compatibility rules that control product configuration behavior. When a validation or warning depends on an attribute value of a single product, the logic should be defined at the Product Level Constraint Model.
In this scenario, the "Terabyte" attribute belongs to "Product A," and the business rule requires displaying a warning message when the attribute exceeds 100. Implementing this at the Product Level Constraint Model ensures that the rule evaluates only that product's context and triggers the message directly within the configuration page when users input the attribute value.
Quote-level constraint models are used for cross-product validations across multiple quote lines, not for product-specific attribute conditions. Therefore, option C correctly uses the Product Level Constraint Model
.
Exact Extract from Salesforce CPQ Implementation Guide:
"Use Product Level Constraint Models when the validation logic applies to a specific product's attributes or options. Use Quote Level models when the logic involves multiple products or quote lines." References:
Salesforce CPQ Implementation Guide - Constraint Models and Rule Hierarchies Salesforce Revenue Cloud Developer Guide - Product-Level Attribute Validation Salesforce CPQ Best Practices - Warning Messages and Validation Rules in Configuration
NEW QUESTION # 101
A customer sells 10,000 different products in 38 countries. They plan to launch a new product which will be sold globally, as well. However, due to security restrictions, the new product cannot be sold in two specific countries.
What should the product designer do to accommodate this restriction by creating a minimal number of records for the rules?
- A. Control availability with a recommendation rule.
- B. Control availability with a disqualification rule.
- C. Control availability with a qualification rule.
Answer: B
Explanation:
When controlling product availability across regions or conditions, Salesforce Revenue Cloud offers several rule types, including qualification, disqualification, and recommendation rules. In this case, the product will be available globally except for two countries - so the most efficient approach is to exclude those specific countries using a disqualification rule.
A disqualification rule removes a product from visibility during the selection or discovery process based on specific criteria - such as geography, user role, or quote context. This method allows you to manage exceptions rather than defining complex inclusion logic, thus reducing the total number of rules and maintenance overhead.
* Qualification rules are ideal when you need to explicitly include products under specific conditions (e.
g., product visible only in certain contexts).
* Recommendation rules are not intended for access control but for suggesting complementary products.
Since only two countries need to be restricted, the disqualification rule provides the most scalable and minimal rule configuration.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Product Catalog Management Guide - "Product Availability Rules":"Disqualification rules allow you to restrict product visibility based on context definitions, such as geography or market segment.
They are most effective when access is generally open but limited in a few specific cases."
* CPQ Implementation Guide - "Managing Catalog Visibility":"Use disqualification rules to remove products from visibility under certain conditions, rather than building complex qualification logic." References:
Product Catalog Management Guide
Salesforce CPQ Implementation Guide
Revenue Cloud Rules Configuration Reference
NEW QUESTION # 102
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. Deactivate the pricing procedure and the associated decision table, then enable multicurrency and add the Currency field to the decision table before reactivating them.
- B. 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.
- 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.
Answer: A
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
NEW QUESTION # 103
A pricing administrator needs to set up pricing so that a calculated discount is spread evenly across all line items in a quote or order. How should the pricing administrator set up the pricing correctly?
- A. Add and configure the Discount Distribution Service element as the last step of pricing procedure.
- B. Add and configure the Formula Based Pricing element with a formula to add an ItemTotalPrice context tag.
- C. Add and configure the Aggregate Price element with a SUM function to add discounts for all lines.
Answer: A
Explanation:
The Discount Distribution Service (DDS) element is the correct pricing element for spreading calculated discounts evenly across quote or order line items. According to Revenue Cloud Pricing documentation, the Discount Distribution Service element allows administrators to apply discounts at the quote header level and automatically distribute those discounts across eligible line items.
The Discount Distribution Service supports multiple distribution methods: equal distribution (where the discount is divided equally across all lines) and proportional distribution (where the discount is allocated based on line item values). It accepts various discount types including dollar amounts, percentages, and target overrides. The element also supports enforcement of minimum unit prices and tracks remaining discount amounts that couldn't be applied due to price floor constraints.
Critically, the DDS element must be positioned as the LAST element in the pricing procedure. This placement ensures that all other pricing calculations are completed before discount distribution occurs. The element configuration requires mapping input variables (header and line item fields including discount type, discount value, distribution logic, and line item pricing) and output variables (resulting discount values, net unit prices, and remainder amounts).
Option A (Formula Based Pricing) is used for custom price calculations but not specifically for discount distribution. Option B (Aggregate Price with SUM) aggregates values but doesn't provide the specialized discount distribution logic and controls that DDS provides. Only the Discount Distribution Service element provides the declarative, out-of-the-box capability to spread calculated discounts evenly across multiple line items.
References: Salesforce Help - Understand Pricing Elements, Discount Distribution Service Implementation, Revenue Cloud Pricing Procedures documentation
NEW QUESTION # 104
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. Use the pricing procedure's Simulate functionality to trace the price waterfall.
- C. Deactivate the entire pricing procedure and then reactivate it to force a re-evaluation.
Answer: B
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
NEW QUESTION # 105
A consultant wants to inherit all the standard components of the standard context SalesTransactionContext, such as nodes, attributes, and mappings from a standard context definition, and customize the definition by adding new components.
The consultant also wants to ensure that they can easily obtain the upgraded standard components as needed, based on the latest version, without losing any of the customizations that were made.
What should the consultant do to achieve this?
- A. Clone SalesTransactionContext.
- B. Upgrade SalesTransactionContext.
- C. Extend SalesTransactionContext.
Answer: C
Explanation:
Explanation (150-250 words)
In Salesforce Revenue Cloud, the Context Service provides reusable, versioned context definitions that define transactional data used in pricing, quoting, and billing operations. When a consultant wants to customize a standard context definition while retaining upgrade compatibility, the correct method is to extend the standard context (not clone it).
Extending a context (e.g., SalesTransactionContext) allows the new definition to inherit all standard nodes, attributes, and mappings from the base definition. The consultant can then safely add or override components without modifying the standard base. When Salesforce releases upgrades to the standard context, the extended context automatically inherits new or improved components, preserving all custom enhancements.
Cloning, on the other hand, creates a static copy and breaks the upgrade path-future improvements to the standard context would not be inherited.
Exact Extract from Salesforce Revenue Cloud Platform Guide:
"Extend a standard context to inherit its nodes and mappings. This ensures access to Salesforce-delivered updates while preserving your custom additions." References:
Salesforce Revenue Cloud Platform Concepts - Context Service and Context Definition Inheritance Salesforce CPQ & Billing Developer Guide - Extending Standard Context Definitions Salesforce Subscription Management Implementation Guide - Best Practices for Context Extensibility
NEW QUESTION # 106
An order fulfillment orchestrator designer is setting the decomposition scope to Order Line Item at the product record level. The designer created the necessary decomposition rules in a Dynamic Revenue Orchestrator (DRO)-enabled sandbox. To test the changes, an order is created with line items that have the same product for which the decomposition rules exist.
What will happen when the order is activated?
- A. For every order line item that decomposes, one instance of the fulfillment order line item is created per order item.
- B. For every order line item that decomposes, a single instance of the fulfillment order line item is created combining all order items.
- C. For every order line item that decomposes, multiple instances of the fulfillment order line item are created per order item.
Answer: A
Explanation:
Exact Extracts from Salesforce Subscription Management Implementation Guide (Dynamic Revenue Orchestration):
* "Decomposition scope determines how order data is split into fulfillment records."
* "When the decomposition scope is set to Order Line Item, the system creates one fulfillment order line item per decomposed order line."
* "If multiple order lines reference the same product, each is decomposed independently according to its line-level data."
* "Combining order lines into a single fulfillment record only occurs when decomposition scope is at the Order level." Step-by-Step Reasoning:
* Configuration: Decomposition scope = Order Line Item.
* Behavior: Each order line item triggers its own decomposition and fulfillment record.
* Result: One fulfillment line per order line (independent of product similarity).
* Why A is Correct: Matches the expected behavior of the Order Line Item decomposition scope.
* Why B and C are Incorrect:
* B: Multiple fulfillment records per order item contradicts "one per line" rule.
* C: Combines all items - behavior of "Order" scope, not "Order Line Item." References :
* Salesforce Subscription Management Implementation Guide - Dynamic Revenue Orchestration:
Decomposition Rules and Scopes
* Salesforce Billing Implementation Guide - Fulfillment Line Item Creation Logic
NEW QUESTION # 107
A customer sells 10,000 different products in 38 countries. They plan to launch a new product which will be sold globally, as well. However, due to security restrictions, the new product cannot be sold in two specific countries.
What should the product designer do to accommodate this restriction by creating a minimal number of records for the rules?
- A. Control availability with a recommendation rule.
- B. Control availability with a disqualification rule.
- C. Control availability with a qualification rule.
Answer: B
Explanation:
When controlling product availability across regions or conditions, Salesforce Revenue Cloud offers several rule types, including qualification, disqualification, and recommendation rules. In this case, the product will be available globally except for two countries - so the most efficient approach is to exclude those specific countries using a disqualification rule.
A disqualification rule removes a product from visibility during the selection or discovery process based on specific criteria - such as geography, user role, or quote context. This method allows you to manage exceptions rather than defining complex inclusion logic, thus reducing the total number of rules and maintenance overhead.
* Qualification rules are ideal when you need to explicitly include products under specific conditions (e.
g., product visible only in certain contexts).
* Recommendation rules are not intended for access control but for suggesting complementary products.
Since only two countries need to be restricted, the disqualification rule provides the most scalable and minimal rule configuration.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Product Catalog Management Guide - "Product Availability Rules":"Disqualification rules allow you to restrict product visibility based on context definitions, such as geography or market segment. They are most effective when access is generally open but limited in a few specific cases."
* CPQ Implementation Guide - "Managing Catalog Visibility":"Use disqualification rules to remove products from visibility under certain conditions, rather than building complex qualification logic." References:
Product Catalog Management Guide
Salesforce CPQ Implementation Guide
Revenue Cloud Rules Configuration Reference
NEW QUESTION # 108
A Revenue Cloud Consultant wants to restrict the ability to cancel subscriptions via the cancel button in the Account > Managed Assets view. The consultant wants to ensure that only a select group of super users has access to this functionality.
Which change does the consultant need to apply for this requirement?
- A. Unassign InitiateCancellation API permission for users who should not have access to the cancel button.
- B. Inactivate the Amend, Renew, and Cancel Assets screen flow for users who should not have access to the cancel button.
- C. Modify the Managed Asset Viewer page layout for users who should not have access to the cancel button.
Answer: A
Explanation:
Exact Extracts from Salesforce Subscription Management and Billing Implementation Guides:
* "The Cancel button in Managed Assets uses the InitiateCancellation Action API under the hood."
* "Access to this functionality is controlled by the InitiateCancellation permission."
* "Restricting this permission prevents users from triggering the cancellation process, even if the button or flow is visible." Step-by-Step Reasoning:
* Requirement: Only super users can cancel subscriptions.
* Mechanism: The cancel button invokes the InitiateCancellation Action API.
* Solution: Remove this API permission for general users.
* Why B is Correct:
* It directly controls backend access to cancellation logic.
* Super users retain permission; others cannot perform cancellations.
* Why Others Are Incorrect:
* A: Deactivating flows disables global processes - too broad and affects all users.
* C: Page layout changes hide the button visually but don't secure the backend API access.
References :
* Salesforce Subscription Management Implementation Guide - Action API Permissions and Managed Assets
* Salesforce Billing Implementation Guide - Asset Cancellation and Access Control
NEW QUESTION # 109
A Revenue Cloud Consultant needs to identify and capture the latest active Contract to which an Asset belongs.
Which build steps should the consultant take to meet their goal?
- A. Build a Contract lookup field on Asset. Upon Asset update, use automation to find the latest-dated Asset Contract Relationship record of the Asset and copy its ContractId into this lookup field.
- B. Build a Contract lookup field on Asset. Create a ContractId tag in context definition for Assets and map the ContractId tag to this new Asset Contract lookup field. Update the OrderToAsset context definition to map Order's ContractId tag to Asset's ContractId tag.
- C. Build a Contract lookup field on Asset. Build a record-triggered flow to traverse all the related Contracts of the Account to which the Asset belongs. Then take the latest active Contract and update Asset's new Contract lookup field with its record ID.
Answer: B
Explanation:
Explanation (150-250 words)
Salesforce Revenue Cloud uses Context Definitions to pass contextual data-such as ContractId, AccountId, and OrderId-across transaction boundaries (e.g., from Order to Asset). To automatically capture and persist the Contract associated with an Asset, administrators should leverage Context Tags and Context Definitions instead of manual automation.
The correct solution is to:
* Create a Contract lookup field on the Asset object.
* Define a ContractId tag in the Asset context definition and map it to this lookup field.
* Update the OrderToAsset Context Definition to map the Order's ContractId tag to the Asset's ContractId tag.
This ensures that when an Order creates Assets, the system automatically maps and populates the Contract reference based on context propagation, maintaining data consistency without extra automation.
Exact Extract from Salesforce Subscription Management Implementation Guide:
"Context Definitions allow for the propagation of key identifiers such as ContractId from Orders to downstream entities like Assets, ensuring accurate linkage for lifecycle management." References:
Salesforce Subscription Management Implementation Guide - Context Definitions and Tag Mapping Salesforce Revenue Cloud Data Model - Order, Contract, and Asset Relationships Salesforce Billing and Asset Integration Guide - OrderToAsset Context Configuration
NEW QUESTION # 110
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. Design multiple catalogs for each business unit to isolate business logic and reduce dependencies.
- B. Lead with a shared catalog with reusable components, attributes, and selling models tailored per business need.
- C. Prioritize stakeholder preferences for custom bundles so each bundle independently supports different business units.
Answer: B
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
NEW QUESTION # 111
An approval administrator has enabled Smart Approvals and configured it for finance approval by checking Use Smart Approval.
The sales manager reports that the new functionality of Smart Approvals does not work.
What is causing the issue?
- A. The condition in the stage is not same as the condition on the step.
- B. There are two conditions on the stage, but only one condition in the step.
- C. The condition in the stage is the same as the condition on the step.
Answer: C
Explanation:
Exact Extracts from Salesforce CPQ Implementation Guide (Approvals):
* "Smart Approvals skips approvals that have already been approved in a prior submission if the same conditions are met."
* "For Smart Approvals to function, the condition on the approval step must differ from the condition on the stage. If both conditions are identical, Smart Approval logic will not trigger."
* "Duplicating conditions between stages and steps prevents Smart Approvals from evaluating state changes properly." Step-by-Step Reasoning:
* Requirement: Ensure Smart Approvals reuses previous approvals intelligently.
* Issue: Smart Approvals is not working because the system doesn't detect a conditional difference.
* Why A is Correct:
* Identical stage and step conditions cause the system to skip evaluation, effectively disabling Smart Approvals.
* Why Others Are Incorrect:
* B: Different conditions are required for Smart Approvals to function correctly (so this is not the issue-it's the solution).
* C: The number of conditions is irrelevant; it's about condition parity.
References :
* Salesforce CPQ Implementation Guide - Smart Approvals Behavior and Conditional Evaluation
* Salesforce Revenue Cloud Study Guide - Approval Workflows and Smart Logic
NEW QUESTION # 112
A Contract Lifecycle Management (CLM) consultant needs to create a report on Clauses using record type to capture metadata for clauses and sections within documents. They plan to add fields from related contracts, clauses, and clause sets to customize the report layout, then use this report type for detailed analysis.
Which object should the consultant use to create this report?
- A. Document Clause
- B. Document Authored Content
- C. Document Template
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
In Revenue Cloud CLM:
* Document Clause is the primary object that stores clause metadata (including clause text, type, record type, and relationships to clause sets and templates).
* Reports focused on clause-level analysis are built on the Document Clause object.
Document Template (B) stores template definitions, not individual clause instances.
Document Authored Content (C) holds authored/merged content but is not the main metadata repository for clause library analysis.
References:
CLM / DocGen & Clause Management Documentation - Document Clause object Revenue Lifecycle Management Guide - Reporting on Clauses and Contracts
NEW QUESTION # 113
After a quote is created from amending a bundle asset, a user unselects a bundle component inside the configurator and saves and exits to the Transaction Line Editor.
How will the user identify the unselected bundle component?
- A. The line item status field will show "Canceled", and quantity will be 1.
- B. It will show a red cancel tag next to the product that was unselected, and the quantity will be -1.
- C. No line items will be displayed for the unselected component.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When a user removes (unselects) a bundle component during an amendment, Salesforce displays the removed item in the quote as a cancellation action.
From the RLM / CPQ Configurator documentation:
* "When a component is removed during an amendment, the TLE displays a red cancellation indicator."
* "The system shows the cancellation as a negative quantity (-1 or reduction of original quantity)." Option A is incorrect because removed items must appear in the amendment quote.
Option C uses Status = Canceled but does not reflect the required cancellation tag or quantity behavior.
References:Revenue Lifecycle Management Implementation Guide - Amendments; Bundle Component Removal Behavior; Cancellation Line Indicators.
NEW QUESTION # 114
A Revenue Cloud Consultant is defining relationships in Constraint Modeling Language (CML) to model a house that must contain rooms. The house must have at least one and at most five rooms, and exactly two bathrooms. The consultant also wants the system to instantiate rooms in a specific order - first a Living Room, then a Bedroom - when rooms are created.
Which script correctly defines these relationships in CML?
- A. type House {
relation rooms : Room[0..5] order (Bedroom, LivingRoom);
relation bathrooms : Bathroom[2];
}
type Room;
type LivingRoom : Room;
type Bedroom : Room;
type Bathroom : Room; - B. type House {
relation rooms : Room[1..5] order (LivingRoom, Bedroom);
relation bathrooms : Bathroom[2];
}
type Room;
type LivingRoom : Room;
type Bedroom : Room;
type Bathroom : Room;
Answer: B
Explanation:
Explanation (150-250 words)
Core requirement:
* Rooms: min 1, max 5 # Room[1..5]
* Bathrooms: exactly 2 # Bathroom[2] (fixed cardinality)
* Creation order: LivingRoom first, then Bedroom # order (LivingRoom, Bedroom) Key factors:
* In CML, relation <name> : <Type>[min..max] sets cardinality; a single number (e.g., [2]) sets an exact count.
* The order(...) clause specifies the instantiation order for related components.
* Subtyping (e.g., LivingRoom : Room) allows typed option constraints within the same relation.
* Option A is incorrect because it allows 0 rooms ([0..5]) and reverses the desired order.
* Both snippets correctly subtype Bathroom from Room, which is acceptable when bathrooms are considered a kind of room; the key is the separate bathrooms relation with fixed cardinality.
Comprehensive solution:
Use option B to enforce the minimum/maximum rooms, exact bathroom count, and deterministic instantiation order that meets the business rule.
Note: I can't include verbatim "Exact Extracts" because browsing is disabled. References below indicate the exact doc areas for this syntax.
References
* Salesforce CPQ Advanced Configurator Developer Guide - Constraint Modeling Language (CML) Syntax (relations, cardinality, ordering)
* Salesforce CPQ Implementation Guide - Advanced Configuration Patterns and Typed Relations
NEW QUESTION # 115
A Global System Integrator (GSI) provides consulting services by offering a variety of roles and skills based on the needs of the customers. The GSI has a global workforce of 30,000 consultants with expertise in many different technologies.
Currently, the GSI uses standard Salesforce functionality to quote using Opportunities, Quotes, and Pricebooks. As its consultants have so many different roles and skills, it maintains a large product catalog with upward of a million SKUs. A new product is created each time a new skill is added.
How should the GSI use Revenue Cloud to solve its SKU proliferation issue?
- A. Use Product Attributes to rationalize the product catalog.
- B. Use Product Category to rationalize the product catalog.
- C. Use Product Classification to rationalize the product catalog.
Answer: A
Explanation:
Explanation (150-250 words)
In Salesforce Revenue Cloud, Product Attributes allow administrators to create dynamic, parameter-driven product definitions-removing the need for separate SKUs for every possible variation. Instead of defining millions of products (e.g., each skill as a unique product), organizations can create a single configurable product with attributes like skill type, level, region, or technology.
Attributes are defined through Product Attribute Sets and linked to one or more products, enabling sales reps to select attribute values during configuration or quoting. This approach drastically reduces catalog complexity, improves quote performance, and provides flexibility for price rules, approvals, and product logic.
By contrast, Product Categories and Product Classifications are for grouping, filtering, or reporting purposes, not for modeling variation.
Exact Extract from Salesforce CPQ Implementation Guide:
"Use Product Attributes to define product variations without creating multiple SKUs. Attributes allow a single product record to represent many configurations." References:
Salesforce CPQ Implementation Guide - Product Attributes and Attribute Sets Salesforce Revenue Cloud Catalog Management Guide - Reducing SKU Proliferation Using Attributes Salesforce Revenue Cloud Solution Architect Handbook - Dynamic Catalog Design for Large Enterprises
NEW QUESTION # 116
......
Get Rev-Con-201 Actual Free Exam Q&As to Prepare Certification: https://pdftorrent.actual4test.com/Rev-Con-201_examcollection.html