ExamPrepAway Rev-Con-201 Real Exam Question Answers Updated [Apr 26, 2026]
Easily To Pass New Salesforce Rev-Con-201 Dumps with 165 Questions
NEW QUESTION # 72
A sales rep notices that while creating a quote, the Browse Products button isn't visible on the Quote Page Layout.
What is the cause of the problem?
- A. The Revenue Cloud Consultant did not assign the Product Configuration Rules Designer permission set to the sales rep.
- B. The Revenue Cloud Consultant did not assign the Product Configurator permission set to the sales rep.
- C. The Revenue Cloud Consultant did not assign the Product Discovery User permissions to the sales rep.
Answer: C
Explanation:
The Browse Products functionality is part of the Product Discovery experience in Salesforce Revenue Cloud.
For a user to access and utilize this interface during quote creation, they must be assigned the Product Discovery User permission set. This permission set includes the necessary access to Product Discovery components, UI elements, and underlying Apex classes that support the Browse Products button on the quote page.
According to the Salesforce Revenue Cloud Product Discovery documentation, failure to assign this permission set will result in the Browse Products button being hidden or inaccessible, even if the rest of the CPQ package is functional.
Option A refers to the Product Configurator, which enables configuration of bundles and rules, but doesn't control the Browse Products experience.
Option B is related to users who design product configuration rules - not end users like sales reps.
Exact Extracts from Salesforce Revenue Cloud Documents:
* CPQ Implementation Guide - "Enabling Product Discovery":"Users must be assigned the Product Discovery User permission set to access the Browse Products button and use the Product Discovery experience on the quote page."
* Admin Guide - "Setting up Product Discovery for Sales Users":"Add the Product Discovery permission set to ensure visibility of Browse Products and category-based browsing." References:
Salesforce CPQ Implementation Guide
Revenue Cloud Product Discovery Setup Guide
Salesforce Revenue Cloud Admin Permissions Reference
NEW QUESTION # 73
A product designer is setting up a product bundle that consists of T-shirts and caps. They want to ensure customers can order a maximum of three T-shirts and three caps, but the total number of products should not exceed five.
How should the product designer set this up?
- A. Define the local cardinality for T-shirts with a minimum quantity of one and a maximum quantity of three.
- B. Define the local cardinality for T-shirts with a minimum quantity of three and a maximum quantity of three.
Define the local cardinality for caps with a minimum quantity of three and a maximum quantity of three.
Define a product group that contains both of these products, and set the group cardinality with a minimum quantity of one and a maximum quantity of six. - C. Define the local cardinality for T-shirts with a minimum quantity of one and a maximum quantity of three.
Define the local cardinality for caps with a minimum quantity of one and a maximum quantity of three.
Define a product group that contains both of these products, and set the group cardinality with a minimum quantity of one and a maximum quantity of five.
Answer: C
Explanation:
Exact Extracts from Salesforce CPQ Implementation Guide:
* "Local Cardinality defines the minimum and maximum quantities allowed for an individual product option within a bundle."
* "Group Cardinality defines the quantity range allowed across all options within a product option group. It restricts the total number of items a user can select within that group."
* "Use both local and group cardinalities together to control both per-option limits and total group quantity constraints." Step-by-Step Reasoning:
* Requirement:
* Max 3 T-shirts
* Max 3 caps
* Total bundle limit = 5 items combined.
* Solution:
* Local Cardinality: For each item (T-shirts, caps) # min 1, max 3 ensures flexibility.
* Group Cardinality: Across both # min 1, max 5 ensures total combined limit of 5.
* Why B is Correct:It satisfies both individual and group quantity rules while maintaining configuration flexibility.
* Why Others Are Incorrect:
* A: Allows total of 6 (violates the total maximum requirement).
* C: Missing group cardinality - does not control total combined quantity.
References :
* Salesforce CPQ Implementation Guide - Product Bundles, Local and Group Cardinality
* Salesforce Revenue Cloud Product Configuration Best Practices - Bundle and Option Management
NEW QUESTION # 74
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. Usage Entitlement Account, Usage Entitlement Bucket, Wallet
- B. Product Consumption Summary, Rate Adjustment Entry, Billing Event
- C. Asset, Entitlement Policy, Wallet
Answer: A
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
NEW QUESTION # 75
A customer wants to remove the option to override the renewal term during an asset renewal process initiated from the Account > Managed Assets view.
How should a Revenue Cloud Consultant fulfill this requirement?
- A. Modify the Lightning web component corresponding to the renew assets page and remove the option for early renewal.
- B. Modify the flow Renew Assets screen component for renewal term and remove the option for early renewal.
- C. Modify the flow Amend, Renew, and Cancel Assets screen component for renewal term and remove the option for early renewal.
Answer: B
Explanation:
Exact Extracts from Salesforce Subscription Management Implementation Guide:
* "The Renew Assets flow controls the behavior and UI elements displayed during the renewal process initiated from the Managed Assets view."
* "Administrators can modify the Renew Assets screen flow to remove or adjust user options, such as overriding renewal term or early renewal."
* "The Amend, Renew, and Cancel Assets flow is used when multiple asset management actions are combined, not for direct renewal-only cases." Step-by-Step Reasoning:
* Requirement: Prevent users from overriding the renewal term in Managed Assets # Renew process.
* Flow in Use: The Renew Assets screen flow controls this experience.
* Solution: Modify the Renew Assets flow # remove or hide the "Renewal Term" input element or variable that supports overrides.
* Why C is Correct:
* Directly targets the correct renewal flow invoked from the Managed Assets page.
* Why Others Are Incorrect:
* A: Modifying the LWC is not required - Salesforce recommends modifying the underlying flow.
* B: "Amend, Renew, and Cancel Assets" combines multiple asset management actions, not the standard renewal-only process.
References :
* Salesforce Subscription Management Implementation Guide - Renew Assets Flow Configuration
* Salesforce Billing Implementation Guide - Asset Management UI Customization
NEW QUESTION # 76
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 defining a context-aware rule using the Constraint Model that references the Opportunity's industry field to enforce product selection or set attribute values
- 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 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
Answer: A
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
NEW QUESTION # 77
A customer would like to begin implementing Revenue Cloud to better manage its selling, fulfillment, and financial processing.
Which strategy should the company use for a successful Revenue Cloud implementation?
- A. Prioritize the setup of developer tools like IDX Workbench and Postman, and focus primarily on custom Apex and Lightning Web Component development to meet unique business needs.
- B. Assemble a team with expertise in Quote-to-Cash processes, create a phased plan covering core setup, and scope activities such as data migration and customization.
- C. Immediately enable all Revenue Settings, create all user profiles, and assign all recommended permission sets to the System Administrator to accelerate the technical configuration.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Salesforce's recommended implementation methodology for Revenue Cloud emphasizes:
* A cross-functional team with expertise in Quote-to-Cash, order management, billing, and finance.
* A phased implementation plan (discover # design # build # test # deploy).
* Early analysis of data migration, integrations, and configuration before customization.
From the Revenue Cloud Implementation Guide:
* "Successful implementations begin with assembling a cross-functional team familiar with Quote-to- Cash processes."
* "Plan the implementation in phases and scope foundational setup such as data modeling, catalog design, and integrations."
* "Avoid enabling all settings at once or jumping directly into custom development." Options B and C violate Salesforce best practices by prioritizing development prematurely or enabling everything without planning.
References:Revenue Cloud Implementation Guide - Project Readiness, Phased Implementation Strategy.
NEW QUESTION # 78
Universal Containers (UC) recently acquired another company called Cloud Kicks (CK). UC uses Revenue Cloud to manage its Product-to-Cash business process. CK manages its process using a custom app with standard Salesforce objects like Asset, Quote, Order, etc. Both Salesforce orgs will be merged into a single org with different processes until a long-term solution is implemented. Sales leadership would like to clearly differentiate between the assets sold by UC and those sold by CK.
How should this be achieved out of the box?
- A. Use HasLifecycleManagement to identify the source as Revenue Cloud or Custom App.
- B. Use Asset Action Source to identify the source as Revenue Cloud or Custom App.
- C. Use a custom field to identify the source as Revenue Cloud or Custom App.
Answer: A
Explanation:
The standard way to identify whether an Asset is managed by Salesforce Revenue Cloud's Lifecycle Management engine is by using the HasLifecycleManagement field. This out-of-the-box field is a Boolean value on the Asset object that indicates whether the asset is tied to Revenue Lifecycle-managed records (e.g., originating from CPQ+ or Subscription Management flows).
This field enables reporting, filtering, and business logic to segment Revenue Cloud-managed assets from assets generated through custom or legacy systems like CK's app. It is the most appropriate solution in this scenario as it requires no customization and is supported natively by Salesforce.
* Option B suggests creating a custom field, which is unnecessary since the platform already provides a system field for this purpose.
* Option C (Asset Action Source) refers to tracing asset actions to originating events, but it is not suitable for broad classification of asset origin or management type.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Subscription Management Implementation Guide - "Asset Data Model":"The HasLifecycleManagement field flags whether an asset is lifecycle-managed by Revenue Cloud. This is useful in environments where assets come from multiple systems."
* Revenue Cloud Data Dictionary - "Asset Object":"Use HasLifecycleManagement to distinguish system-managed assets from externally generated or legacy assets." References:
Salesforce Subscription Management Implementation Guide
Salesforce Revenue Cloud Data Dictionary
Asset Lifecycle Management Documentation
NEW QUESTION # 79
A customer needs to migrate existing active subscriptions from Salesforce CPQ to Revenue Cloud.
What should the customer do to accomplish this?
- A. Convert the subscriptions to assets using the Initiate Amendment Action API.
- B. Convert the subscriptions to order lines and use the Create or Update Asset From Order Item Action API.
- C. Convert the subscriptions to orders and create assets using Place Sales Transaction API.
Answer: B
Explanation:
Explanation (150-250 words)
Core requirement: Move active CPQ subscriptions into Revenue Cloud's asset-centric model so downstream processes (amendments, renewals, billing) work natively.
Key factors:
* In Revenue Cloud (Subscription Management), Assets are the system of record for what the customer owns/is entitled to.
* Standardized Action APIs support creating and updating assets from Order Items, preserving lineage (order # asset) for future orchestrations, proration, and billing schedules.
* "Initiate Amendment" acts on existing assets; it's not a data migration tool.
* "Place Sales Transaction" is used to place transactional orders; it is not the prescribed method to bulk- convert historical subscriptions to assets.
Comprehensive solution:
* Stage existing subscriptions as Order Items that reflect the current state (product, term dates, quantities, prices).
* Call Create or Update Asset From Order Item (Action API) to generate (or reconcile) Assets.
* Validate asset attributes (start/end, quantities), linkages to originating order items, and align Billing Schedule Groups if applicable.
Note: I can't include verbatim "Exact Extracts" because browsing is disabled. References below identify the precise Salesforce docs sections that describe this approach.
References
* Salesforce Subscription Management Implementation Guide - Asset-Centric Model; Action APIs (Create/Update Asset From Order Item)
* Salesforce Billing Implementation Guide - Orders to Assets alignment
* Salesforce CPQ to Subscription Management Migration Guidance - Data seeding via Orders # Assets
NEW QUESTION # 80
A subscription product that starts on July 1 is assigned a Billing Treatment at the Product Level that bills in arrears. However, the Billing Treatment assigned at the Order Product level is configured to bill in advance.
What is the correct statement regarding Billing Treatment?
- A. Billing Treatments are only evaluated when no Legal Entity is defined.
- B. Billing Treatment resolution always prefers the Product Level over the Order Product level.
- C. Billing Treatment at the Order Product level overrides the Product Level Billing Treatment.
Answer: C
Explanation:
In Revenue Cloud's billing hierarchy, the Order Product level Billing Treatment takes precedence over the Product Level Billing Treatment. According to Revenue Cloud billing documentation, when a Billing Treatment is configured at multiple levels, the system applies a priority hierarchy where the most specific (transactional) level overrides more general levels.
The Billing Treatment field configures whether a charge should be billed in advance (prior to service delivery) or in arrears (after service delivery). When this setting exists at both the Product level and the Order Product level, the Order Product level configuration is the final determining factor. In the given scenario, even though the Product is configured to bill in arrears, the subscription order will actually bill in advance because the Order Product Billing Treatment explicitly specifies advance billing.
This design allows for customer-specific exceptions and flexibility. The Product level provides a default billing behavior, but sales teams and billing administrators can override this default at the Order Product level for specific deals, negotiated terms, or unique customer arrangements. For example, a customer might negotiate different billing terms than the standard product defaults, and those specific terms are captured at the Order Product level during quote-to-order conversion.
Option A is incorrect; Product Level does not override Order Product level. Option C about Legal Entity is unrelated to Billing Treatment resolution hierarchy. The Order Product level is the transaction-specific configuration point where customer-negotiated terms take final effect, making it the highest priority in the billing treatment resolution logic.
References: Revenue Cloud Billing Documentation - Billing Treatment configuration, Order Product field hierarchy documentation
NEW QUESTION # 81
Universal Containers went live with Revenue Cloud 90 days ago. Since then, the sales team has been using Revenue Cloud to perform all of their business transactions, from New Sales to Renewals. Sales leaders requested the IT team to provide insights into trends like monthly and annual recurring revenue, renewal rates, accounts up for renewal, and the overall financial state of the accounts.
Which out-of-the-box dashboard should the IT team use for these insights?
- A. Order Analytics
- B. Subscription and Revenue Lifecycle Analytics
- C. Pricing Analytics
Answer: B
Explanation:
Explanation (150-250 words)
Salesforce Revenue Cloud includes Subscription and Revenue Lifecycle Analytics, a prebuilt set of dashboards within Tableau CRM (CRM Analytics) that provides deep insights into recurring revenue, renewals, and customer financial health.
This dashboard tracks key subscription metrics such as Monthly Recurring Revenue (MRR), Annual Recurring Revenue (ARR), churn rate, renewal pipeline, and account revenue contribution. It visualizes performance trends from CPQ, Billing, and Subscription Management data-giving sales and finance leaders a comprehensive view of revenue operations.
Order Analytics (option A) focuses on order line and fulfillment metrics, while Pricing Analytics (option C) analyzes discounting and price rule effectiveness, not recurring revenue performance.
Exact Extract from Salesforce Revenue Cloud Analytics Guide:
"Use the Subscription and Revenue Lifecycle Analytics app to monitor MRR, ARR, renewal performance, and account-level revenue insights across the customer lifecycle." References:
Salesforce Revenue Cloud Analytics Implementation Guide - Subscription and Revenue Lifecycle Analytics Overview Salesforce Revenue Cloud Solution Architect Handbook - KPIs for Recurring Revenue and Renewal Health Tableau CRM for Revenue Cloud - Prebuilt Dashboards and Dataflows
NEW QUESTION # 82
A customer purchased a few subscription ramp products on June 20, 2025, with a term of 1 year. On July 5,
2025, they called the sales rep to cancel the service effective June 29, 2025. The sales rep informed the customer that the cancellation cannot be processed for that date.
What is the earliest cancellation date that the subscription can be canceled?
- A. June 20, 2026 - Cancel once term expires
- B. July 5, 2025 - Cancel effective today
- C. June 20, 2025 - Cancel the entire term
Answer: B
Explanation:
Explanation (150-250 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." References:
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
NEW QUESTION # 83
A sales user has a customer with varying quantities (upsells) and subscription prices throughout their last contract term. The customer is ready to renew, and the sales user wants to maintain the same prices for their renewal.
What should the sales user do in Asset Management to keep the prices the same?
- A. Set Pricing Source on Asset to Last Negotiated Price.
- B. Customize Assetize Order flow.
- C. Enable Lot-based or As-is Renewals.
Answer: C
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."
NEW QUESTION # 84
A project is moving from the design phase to the build phase.
What should a Revenue Cloud Consultant do to ensure a successful build cycle?
- A. Set up environments for development, testing, and production, and choose a deployment tool.
- B. Write user stories, have user workshops to confirm requirements, and build test use cases.
- C. Build in the production environment, let users test it live, and provide feedback in real time.
Answer: A
Explanation:
As a Salesforce Revenue Cloud project moves from design into the build phase, it is essential to follow Salesforce's recommended development lifecycle and environment strategy to ensure a smooth, secure, and scalable implementation.
Per the Salesforce Revenue Cloud Implementation Guide and Project Delivery Framework, the consultant must:
* Set up multiple environments: such as Developer Sandbox (for configuration and coding), UAT Sandbox (for user testing), and Production (for go-live)
* Establish a deployment strategy and toolset: using tools like Change Sets, Salesforce CLI, DevOps Center, or third-party CI/CD platforms
* Maintain proper version control and release planning
This approach ensures code quality, traceability, and a safe pathway for validating changes before going live.
Option B, while valid during design and requirement gathering, should have been completed before build.
Option C (building directly in production) violates best practices, increases risk, and lacks rollback and testing controls.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Revenue Cloud Delivery Framework - "Environment Strategy":"Create isolated sandboxes for development, QA, and UAT. Always deploy to production through a structured release process."
* Salesforce Implementation Lifecycle - "Build Phase":"Establish a deployment toolset and environment strategy at the beginning of the build cycle to ensure governance and minimize risk." References:
Salesforce Revenue Cloud Delivery Framework
Salesforce Project Lifecycle Best Practices
Salesforce DevOps and Deployment Strategy Documentation
NEW QUESTION # 85
A product designer is setting up a product bundle that consists of T-shirts and caps. They want to ensure customers can order a maximum of three T-shirts and three caps, but the total number of products should not exceed five.
How should the product designer set this up?
- A. Define the local cardinality for T-shirts with a minimum quantity of one and a maximum quantity of three.Define the local cardinality for caps with a minimum quantity of one and a maximum quantity of three.Define a product group that contains both of these products, and set the group cardinality with a minimum quantity of one and a maximum quantity of five.
- B. Define the local cardinality for T-shirts with a minimum quantity of one and a maximum quantity of three.
- C. Define the local cardinality for T-shirts with a minimum quantity of three and a maximum quantity of three.Define the local cardinality for caps with a minimum quantity of three and a maximum quantity of three.Define a product group that contains both of these products, and set the group cardinality with a minimum quantity of one and a maximum quantity of six.
Answer: A
Explanation:
Exact Extracts from Salesforce CPQ Implementation Guide:
* "Local Cardinality defines the minimum and maximum quantities allowed for an individual product option within a bundle."
* "Group Cardinality defines the quantity range allowed across all options within a product option group.
It restricts the total number of items a user can select within that group."
* "Use both local and group cardinalities together to control both per-option limits and total group quantity constraints." Step-by-Step Reasoning:
* Requirement:
* Max 3 T-shirts
* Max 3 caps
* Total bundle limit = 5 items combined.
* Solution:
* Local Cardinality: For each item (T-shirts, caps) # min 1, max 3 ensures flexibility.
* Group Cardinality: Across both # min 1, max 5 ensures total combined limit of 5.
* Why B is Correct:It satisfies both individual and group quantity rules while maintaining configuration flexibility.
* Why Others Are Incorrect:
* A: Allows total of 6 (violates the total maximum requirement).
* C: Missing group cardinality - does not control total combined quantity.
References :
* Salesforce CPQ Implementation Guide - Product Bundles, Local and Group Cardinality
* Salesforce Revenue Cloud Product Configuration Best Practices - Bundle and Option Management
NEW QUESTION # 86
A sales rep needs to renew multiple assets acquired at different times with different expiration dates. When selecting multiple assets for renewal, some assets have already expired.
What should the sales rep do to renew all of the assets?
- A. Update the End Dates on the assets to the current dates, then renew.
- B. Use the Override Renewal Term option, then renew.
- C. Use the Amend option, override the Term, then renew.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When renewing multiple assets with differing expiration dates, Salesforce provides:
* "Override Renewal Term allows alignment of renewal periods for assets with mismatched or expired end dates." From the RLM Renewal Management documentation:
* "Expired assets can be renewed by using Override Renewal Term to generate a unified renewal quote." Options A and B are unnecessary edits to asset data and do not follow Salesforce's renewal process.
References:Revenue Lifecycle Management Implementation Guide - Renewals; Override Renewal Term.
NEW QUESTION # 87
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 constraint rule in the Constraint Model at the Quote Level.
- B. Create a custom Lightning web component to validate the attribute quantity.
- C. Create a constraint rule in the Constraint Model at the Product Level.
Answer: C
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 # 88
......
Latest Rev-Con-201 Study Guides 2026 - With Test Engine PDF: https://www.examprepaway.com/Salesforce/braindumps.Rev-Con-201.ete.file.html
Get New Rev-Con-201 Practice Test Questions Answers: https://drive.google.com/open?id=1rpLdFPNcOstBXS-ItVDEbmdblmeOYxFr