2026 Latest Rev-Con-201 dumps Exam Material with 165 Questions
Salesforce Rev-Con-201 Questions and Answers Guarantee you Oass the Test Easily
Salesforce Rev-Con-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
NEW QUESTION # 52
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 # 53
A Revenue Cloud Consultant needs to deploy a custom decision table into a staging sandbox.
What is the correct sequence of activities required for this deployment?
- A. Deploy the custom object and decision table into the staging sandbox.Map the decision table in the default pricing recipe.Refresh the decision table or sync Pricing.
- B. Deploy the decision table into the staging sandbox.Map the decision table in the default pricing recipe.
Import the data for the decision table, then refresh the decision table. - C. Deploy the custom object and decision table into the staging sandbox.Map the decision table in the default pricing recipe.Import the data for the custom object, then sync Pricing.
Answer: A
Explanation:
Explanation (150-250 words)
A Decision Table in Salesforce CPQ and Revenue Cloud Pricing is used to evaluate business rules and return outputs such as discounts, rates, or pricing logic. When deploying to a sandbox, both the Decision Table definition and any related custom objects that store rule inputs/outputs must first exist in the target environment.
The correct deployment sequence is:
* Deploy the custom object and decision table metadata to the staging sandbox (ensuring structural consistency).
* Map the decision table into the default pricing recipe, allowing it to integrate with the pricing engine for evaluations.
* Refresh or sync Pricing, which updates the pricing engine and ensures all decision table logic and data are active and aligned with the current recipe configuration.
Importing data is optional if the data already exists in the source metadata; however, syncing pricing ensures that the engine recognizes the new logic.
Exact Extract from Salesforce Pricing and Decision Framework Guide:
"After deploying a Decision Table and its supporting custom objects, map it to the pricing recipe and refresh or sync pricing to activate the latest logic within the pricing engine." References:
Salesforce Revenue Cloud Pricing Implementation Guide - Decision Table Deployment Steps Salesforce CPQ Advanced Rules Framework - Decision Table and Recipe Mapping Salesforce Revenue Cloud Deployment Best Practices - Pricing Engine Synchronization
NEW QUESTION # 54
A solution is being designed for migrating a customer's install base to Revenue Cloud. The customer states that it is extremely critical for the installed base to work fine in Revenue Cloud so that there is no business disruption, as a large part of their business is Amendments and Renewals. Apart from the Product, Product Selling Model, and Pricebook, which other key objects should be included in the discovery to help design this migration?
- A. Quote, Quote Line, Order, Order Product
- B. Asset, Subscription, Subscribed Asset, Order
- C. Asset, Asset Action, Asset State Period, Asset Action Source
Answer: C
Explanation:
For migrating an install base to Revenue Cloud with focus on Amendments and Renewals, the correct objects are Asset, Asset Action, Asset State Period, and Asset Action Source. These objects form the foundation of Revenue Cloud's Asset Lifecycle Management, which is essential for tracking customer subscriptions and enabling amendment and renewal processes.
The Asset object represents products or services that customers have purchased and own. It contains critical information about what the customer has, including quantity, pricing, and contract relationships. The Asset Action object tracks all changes made to assets throughout their lifecycle, including new purchases, amendments, renewals, and cancellations. Each asset action creates a historical record of modifications.
Asset State Period is crucial as it represents time spans when an asset has the same quantity, amount, and monthly recurring revenue (MRR). According to the Revenue Cloud Developer Guide, "An asset has as many asset state periods as there are changes to it (asset actions) during its lifecycle." This object is essential for accurate revenue recognition and reporting.
Asset Action Source links back to the originating transaction (Quote or Order) that created or modified the asset, maintaining data lineage. This traceability is vital for amendments and renewals, as Revenue Cloud needs to understand the complete history of each asset.
Option B includes legacy CPQ objects (Subscription, Subscribed Asset) that are not part of Revenue Cloud's asset management model. Option C focuses on transactional objects rather than asset tracking. The Asset Lifecycle Management objects in Option A are specifically designed to support the amendment and renewal workflows that are critical to the customer's business requirements.
References: Revenue Cloud Developer Guide - Asset Lifecycle Standard Objects, AssetStatePeriod object documentation, Asset Lifecycle Management
NEW QUESTION # 55
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. Inactivate the Amend, Renew, and Cancel Assets screen flow for users who should not have access to the cancel button.
- B. Modify the Managed Asset Viewer page layout for users who should not have access to the cancel button.
- C. Unassign InitiateCancellation API permission for users who should not have access to the cancel button.
Answer: C
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 # 56
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 flow Renew Assets screen component for renewal term and remove the option for early renewal.
- B. Modify the flow Amend, Renew, and Cancel Assets screen component for renewal term and remove the option for early renewal.
- C. Modify the Lightning web component corresponding to the renew assets page and remove the option for early renewal.
Answer: A
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 # 57
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. There are two conditions on the stage, but only one condition in the step.
- B. The condition in the stage is not same as the condition on 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 # 58
A sales rep creates a quote with a subscription product called 'Training' with a quantity of 50 and term of 1 year, followed by Order creation, activation, and assetization. The 'Training' asset is then amended on the same day to add eight more seats, followed by Order creation, activation, and assetization.
How many records will be present for Training for each Asset Action and Asset State Period?
- A. Two Asset Actions and one Asset State Periods
- B. Two Asset Actions and two Asset State Periods
- C. One Asset Actions and two Asset State Periods
Answer: B
Explanation:
Explanation (150-250 words)
In Salesforce Subscription Management and CPQ, Asset Actions and Asset State Periods track changes in asset quantity, pricing, and lifecycle states over time.
When the initial order for "Training" is activated, Salesforce creates:
* One Asset Action for the creation (initial assetization).
* One Asset State Period representing the active subscription for 50 seats.
When the same asset is amended later that day to add eight more seats (quantity change), Salesforce generates:
* A second Asset Action to record the amendment event (quantity increased by 8).
* A second Asset State Period to represent the new asset state (58 seats active).
Each amendment creates a new Asset Action and corresponding State Period because Salesforce tracks historical lifecycle events for traceability, revenue recognition, and audit integrity.
The original state remains closed as of the amendment date, and a new one begins immediately.
Exact Extract from Salesforce Subscription Management Guide:
"Each amendment or change event generates a new Asset Action and corresponding Asset State Period to represent the new effective asset configuration." References:
Salesforce Subscription Management Implementation Guide - Asset Actions and State Periods Salesforce CPQ-Billing Integration Guide - Assetization Process Salesforce Revenue Cloud Data Model - Asset Lifecycle Tracking
NEW QUESTION # 59
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 Template
- B. Document Clause
- C. Document Authored Content
Answer: B
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 # 60
A sales rep is beginning the process of renewing a customer's expired assets in Revenue Cloud.
What is the first step the sales rep should take?
- A. Create a new Quote/Order record and manually add the expired assets in the Transaction Line Editor.
- B. Update the Assets Lifecycle End Date on the Current Asset State Period and Asset Action records.
- C. Override Renewal Term using the Managed Assets Component on the Account/Contract record.
Answer: C
Explanation:
Explanation (150-250 words)
When renewing expired assets in Salesforce Subscription Management, the recommended starting point is the Managed Assets Component on the Account or Contract record. From this interface, sales users can override the Renewal Term and initiate the renewal flow for expired or expiring assets.
This ensures that the system automatically references existing asset data, applies renewal pricing logic, and creates the appropriate Renewal Quote and subsequent order.
Manually updating Asset State Periods or Asset Actions (option B) violates lifecycle integrity and is not supported. Similarly, manually adding assets to a quote (option C) disconnects them from the asset management lifecycle, resulting in data inconsistency.
Exact Extract from Salesforce Subscription Management Guide:
"To renew expired assets, initiate the renewal from the Managed Assets Component. Override the renewal term if necessary to regenerate a renewal quote." References:
Salesforce Subscription Management Implementation Guide - Managing and Renewing Expired Assets Salesforce Revenue Cloud UI Guide - Managed Assets Component Salesforce CPQ Subscription Lifecycle - Renewal Term Handling
NEW QUESTION # 61
A Revenue Cloud Consultant is setting up the amendment process for assets in Revenue Cloud. The goal is to ensure that when a customer wants to change their subscription, the process is streamlined from initiation to the final update of the asset.
In this automated lifecycle, what is true about the Opportunity?
- A. It directly updates the Asset record as soon as the opportunity stage is changed to Closed Won, bypassing the need for a quote.
- B. It is only required for amendments that involve a price increase; for other amendments, a quote can be created directly from the account.
- C. It is an optional record used for forecasting purposes and does not directly participate in the asset update automation.
Answer: C
Explanation:
In Salesforce Revenue Cloud, during the amendment process, the Opportunity record is optional and primarily serves for forecasting and reporting. It does not play a direct role in the automation of asset or subscription updates. The automation of amendments is handled by the Quote, Order, and Contract records.
The amendment quote captures the requested changes, and once finalized, it creates an order that updates the contract and related assets automatically.
Exact Extract from Salesforce Revenue Cloud Documentation:
"In an automated amendment lifecycle, an Opportunity is optional and primarily used for forecasting or pipeline tracking. The amendment Quote is the driver of subscription changes. Once the Quote is finalized and converted into an Order, the system automatically updates the Contract and Asset records accordingly."
- Salesforce Subscription Management Implementation Guide
This confirms that the Opportunity is not mandatory in the amendment process and does not directly perform updates. Instead, the Quote-to-Order flow governs asset and subscription modifications. The Opportunity may be linked for visibility but is not a dependency for automation.
Option B is incorrect because asset updates are never triggered directly from an Opportunity stage change.
Option C is also incorrect because Opportunity requirements are not determined by pricing scenarios.
References:
Salesforce Subscription Management Implementation Guide
Salesforce Billing Implementation Guide - Amendment Lifecycle
Salesforce CPQ Implementation Guide - Contracts and Amendments
Salesforce Revenue Cloud Consultant Exam Guide
NEW QUESTION # 62
In the context of a quote or order, the administrator needs to include a Product2 custom field for search.
What should the administrator do to accomplish this?
- A. Use the Index and Search Configuration page to set the Product2 custom field as searchable and run Rebuild Index job.
- B. Add Product2 custom field as a new filter option in the Browse Catalog list view.
- C. Modify the Discover Products screen flow to add the Product2 custom field on the product list page container component.
Answer: A
Explanation:
To make a custom field on the Product2 object available for searching and filtering in the Product Discovery or Browse Products experience, the administrator must configure it using the Index and Search Configuration feature in Salesforce Revenue Cloud.
The correct process includes:
* Navigating to the Index and Search Configuration page.
* Selecting the Product2 object.
* Adding the custom field to the list of searchable fields.
* Running the Rebuild Index job to apply the changes.
This process ensures the custom field is indexed and usable in the search API and UI filters during quote or order product selection.
* Option A (list view filter) impacts UI sorting/filtering but not full-text search capability.
* Option C involves altering the Discover Products flow, which is not required if the goal is simply to enable search based on a field - and would introduce unnecessary complexity.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Product Discovery Setup Guide - "Index and Search Configuration":"To make custom fields on Product2 searchable in product discovery, configure the field in the Index and Search Configuration UI and then rebuild the search index."
* Salesforce CPQ Product Catalog Guide - "Custom Fields and Discovery Search":"After adding a field to searchable fields, it is required to run the Rebuild Index job to enable the change." References:
Salesforce Revenue Cloud Product Discovery Guide
CPQ Implementation Guide - Product Catalog Configuration
Salesforce Index and Search Configuration Admin Tool
NEW QUESTION # 63
An issue is reported during User Acceptance Testing (UAT). Which initial steps should the implementation team take to ensure efficient resolution and proper resource allocation?
- A. Conduct root cause analysis for the issue to determine if it's a legitimate defect, a user training gap, or a new feature request, then route it to the appropriate team.
- B. Prioritize the issue based solely on its impact on project timelines, fixing any issue that is easy to fix and deferring any deep investigation into its root cause.
- C. Assume it is a legitimate defect and assign any identified issue directly to the development team so they can fix and deploy the solution.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Salesforce project methodology and Revenue Cloud implementation guidance state:
* "All UAT issues must undergo root cause analysis to determine whether the issue is (1) a defect, (2) a user training need, or (3) a new requirement or enhancement."
* "Only after classification should the issue be assigned to development or another appropriate team." This ensures that actual defects are addressed while avoiding unnecessary development work and preventing incorrect assumptions.
Why other options are incorrect:
* Option A skips the mandatory triage step.
* Option B discourages root cause analysis and is not aligned with Salesforce UAT processes.
References:Salesforce Implementation Guide - UAT Best Practices; Issue Classification and Triage Procedures.
NEW QUESTION # 64
A solution architect notices that a complex product bundle uses multiple nested Constraint Modeling Language (CML) rules to enforce constraints during product configuration. Users report long load times when adding options to the bundle.
What should the architect do to improve configuration performance and ensure quotes remain technically and commercially viable?
- A. Replace CML entirely with Apex triggers to enforce constraints at quote submission.
- B. Disable constraint rules during configuration and validate selections after deployment.
- C. Refactor and simplify CML constraints to reduce runtime complexity.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Revenue Cloud documentation recommends optimizing and simplifying constraint rules when performance issues arise. Key guidance includes:
* Reducing the number of nested and overlapping CML rules.
* Consolidating rules when possible.
* Avoiding unnecessary complexity that increases runtime evaluation time.
Disabling rules (B) breaks guardrails during configuration and goes against best practices; users would be able to configure invalid combinations.
Replacing CML with Apex triggers (C) removes real-time configurator guidance and is not recommended; constraints should be enforced in the configurator, not only at submission.
References:
Product Configurator and CML Documentation - Performance and Best Practices Revenue Lifecycle Management Implementation Guide - Constraint Rules Optimization
NEW QUESTION # 65
A new order is created with these details:
* The account has a default Billing Profile with a billing address in San Francisco.
* An order is created associated with this account with a billing address in New York.
* The order has a billing account attached with a billing address in Chicago.When billing processes the order, which city will be used?
- A. San Francisco
- B. New York
- C. Chicago
Answer: C
Explanation:
Exact Extracts from Salesforce Billing Implementation Guide:
* "When generating invoices, Salesforce Billing uses the billing account attached to the order as the billing entity."
* "If a billing account is specified on the order, its details (including Billing Address) take precedence over the order or account-level billing information."
* "If no billing account is provided, the system falls back to the order's billing fields, and then to the account's default billing profile." Step-by-Step Reasoning:
* Hierarchy for billing address resolution:Billing Account (highest) # Order Billing Address # Account Billing Profile (lowest).
* In this case:
* Billing Account (Chicago) exists and overrides all others.
* Why B is Correct:The billing process will use Chicago, because the billing account attached to the order dictates the billing details.
References :
* Salesforce Billing Implementation Guide - Billing Account Hierarchy and Invoice Address Resolution
* Salesforce Subscription Management Implementation Guide - Order Billing Account Logic
NEW QUESTION # 66
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 = 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)
- C. Condition Type = Custom Logic & Custom Logic = (1 OR 2) AND (2 AND 3)
Answer: B
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
NEW QUESTION # 67
In Salesforce Revenue Cloud, a consultant is setting up a new user who will primarily be responsible for managing customer assets.
What is a fundamental requirement to ensure this user can effectively view and manage customer assets?
- A. The products must be configured as assetizable, and the createOrUpdateAssetFromOrder flow action should be triggered.
- B. The Asset viewer must have a Salesforce CPQ Plus license assigned to access the Asset-related objects.
- C. The user must have the Customize Application permission enabled on their profile to view the Assets on Accounts.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
To manage assets in Revenue Cloud, two key requirements must be satisfied:
* The product must be marked as assetizable so that the system generates asset records after order activation.
* The createOrUpdateAssetFromOrder flow action (or the automated assetization engine) must run to actually create the asset records.
From Revenue Lifecycle Management documentation:
* "Only products configured as assetizable generate assets."
* "Asset management depends on successful assetization, which is performed via the createOrUpdateAssetFromOrder flow action or automated lifecycle processing." If assets are not generated, even a properly-permissioned user cannot view or manage them.
Why other options are incorrect:
* Customize Application is not required for asset visibility.
* Asset management does not require a CPQ Plus license; asset objects are part of standard RLM
/Revenue Cloud licensing, not CPQ Plus specifically.
References:Salesforce Revenue Lifecycle Management Implementation Guide - Assetizable Products; Assetization Process; createOrUpdateAssetFromOrder Action.
NEW QUESTION # 68
A product manager is creating a bundle in Product Catalog Management and would like to limit the component quantity to three on specific components. How should the product manager achieve this outcome?
- A. Set the maximum quantity to three on the Product Record of each of the desired components.
- B. Set the maximum quantity field on the Local Cardinality of the desired component product to three.
- C. Set the maximum number of components on the Group Cardinality to three.
Answer: B
Explanation:
Local Cardinality is the correct Revenue Cloud feature for limiting component quantities within a bundle.
According to Salesforce Help documentation on "Manage Local Cardinality," local cardinality defines the default, minimum, and maximum quantity of a product component that is permissible in a product bundle.
When a product manager edits the local cardinality of a component within a bundled product, they can set the Max Quantity field to three. This setting restricts customers to ordering a maximum of three units of that specific component when configuring the bundle. The local cardinality settings are configured at the Structure tab of the bundled product, accessible from the Product Catalog Management app.
The local cardinality feature includes several configurable fields: Require this component, Include component by default, Allow quantity changes, Min Quantity, Max Quantity, Quantity Scaling Method, and Price Includes Component. The Max Quantity field specifically controls the upper limit for that component's quantity. This applies to individual product components, enabling granular control over bundled product configurations.
Option A refers to Group Cardinality, which sets limits on a group of products rather than individual components. Option B about modifying the Product Record is incorrect; quantity limits cannot be set at the product level directly for bundle purposes. Local Cardinality is the dedicated feature in Revenue Cloud Product Catalog Management for setting component-specific quantity constraints within bundles.
References: Salesforce Help - Manage Local Cardinality, Define Quantity Limits for Bundled Products, Product Catalog Management documentation
NEW QUESTION # 69
Universal Containers (UC) created a custom formula field called Annual Contract Value on the Asset object.
UC wants this field visible during asset selection for amendment/renewal.
How should a consultant enable this behavior?
- A. Modify the screen flows in the amend, renew, and cancel flow
- B. Modify the Asset related list on Page Layout
- C. Modify the Managed Asset Viewer component on the Lightning page
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Revenue Cloud's asset-based amendment and renewal flows use the Managed Asset Viewer Lightning Web Component to display the list of assets available for selection. This component determines which fields are displayed.
From the RLM Implementation Guide:
* "The Managed Asset Viewer component controls the list and fields shown when selecting assets during amend, renew, or cancel processes."
* "To display custom or additional asset fields, configure the field set used by the Managed Asset Viewer." Updating the page layout or modifying the screen flow does not alter the fields shown in the Managed Asset Viewer.
Why other options are incorrect:
* Page Layout changes do not influence the Managed Asset Viewer UI.
* The guided flows reference the component, not individual flow screens.
References:Salesforce Revenue Lifecycle Management Implementation Guide - Managed Asset Viewer Configuration; Asset Selection Experience.
NEW QUESTION # 70
When a sales user is amending assets, the amendment quote does not have a contract populated.
What is the reason?
- A. The amendment operation has been started after Renewal.
- B. The amendment operation has been started from the Account.
- C. The amendment operation has been started from the Contract.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When beginning an amendment:
From the Revenue Cloud Amendment Guide:
* "If an amendment is initiated from the Account, Salesforce cannot automatically determine which Contract to use, so the Amendment Quote is created without a Contract reference."
* "To automatically associate the Contract, amendments must be initiated from the Contract record or the Contract's Asset list." Option A is not related to contract population rules.
Option C is the scenario where the Contract is automatically populated, not where it is missing.
References:Revenue Lifecycle Management Implementation Guide - Starting Amendments; Contract Context Requirements.
NEW QUESTION # 71
A Revenue Cloud Consultant recently implemented Revenue Cloud for a customer and wants to ensure successful adoption and maintenance.
Which steps should the consultant take with the customer after go-live?
- A. Have the customer get certified in Revenue Cloud and write their own documentation.
- B. Take customer inquiries and keep in touch with them through Slack post-project.
- C. Have knowledge transfer sessions on the implementation and provide help documentation/recordings.
Answer: C
Explanation:
Post-go-live success in Revenue Cloud implementations hinges on knowledge transfer, user enablement, and documentation. According to Salesforce's Implementation Best Practices, consultants should conduct structured knowledge transfer sessions to walk through configuration decisions, key processes, and any customizations. This should be complemented with help documentation, training materials, and recorded walkthroughs to enable self-sufficiency.
The goal is to ensure the client's internal admins and users understand:
* Product catalog structure
* Pricing logic
* Renewal and amendment flows
* Invoice and billing configurations
Option A reflects this industry standard and aligns with Salesforce's prescribed approach for post-go-live readiness.
Option B (Slack support) is informal and not scalable or secure for enterprise implementations.
Option C is unrealistic as a short-term expectation and doesn't guarantee the user's understanding of the specific implementation.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Salesforce Implementation Guide - "Post-Go-Live Support and Enablement":"Conduct knowledge transfer sessions with client stakeholders, and provide recorded demos, configuration documentation, and a runbook for maintenance."
* Revenue Cloud Delivery Framework - "Transition to Support":"A successful go-live includes detailed documentation, admin training, and clear handoff materials to ensure smooth transition to client ownership." References:
Salesforce Revenue Cloud Implementation Guide
Revenue Cloud Partner Delivery Framework
Salesforce Success Guide: Post-Go-Live Strategy
NEW QUESTION # 72
A software company wants to offer a Premium Suite bundle that includes multiple applications and support services at a discounted price compared to purchasing each component individually. The company also needs to apply different discounts to this bundle based on custom conditions.
Which pricing element must the company use to define the bundle pricing logic and then to calculate its price within a pricing procedure?
- A. Bundle-Based Price and Product Selling Model
- B. Bundle-Based Price and Price Adjustment Matrix
- C. Attribute-Based Price and Volume Discount
Answer: B
Explanation:
Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and CPQ Implementation Guides):
* "Bundle-Based Pricing allows you to define how the total price of a bundle is determined, whether from component prices, a fixed price, or dynamic price calculation."
* "Price Adjustment Matrices are used within pricing procedures to apply conditional or tiered discounts to bundle or product pricing."
* "Attribute-Based Pricing is used for pricing individual products based on attribute values, not entire bundles." Step-by-Step Reasoning:
* Requirement:
* Create bundle pricing logic (discounted total price).
* Apply varying discounts under specific conditions.
* Correct Components:
* Bundle-Based Price: Controls how bundle total is derived.
* Price Adjustment Matrix: Applies dynamic, condition-based discounts.
* Why B is Correct:Matches both aspects - bundle calculation and dynamic discounting.
* Why Others Are Incorrect:
* A: Attribute-Based and Volume Discount apply to standalone or quantity-based pricing, not complex bundles.
* C: Product Selling Model controls selling duration/frequency, not bundle pricing or discount logic.
References :
* Salesforce CPQ Implementation Guide - Pricing Procedures and Bundle-Based Pricing
* Salesforce Billing Implementation Guide - Price Adjustment Matrices
* Salesforce Subscription Management Implementation Guide - Bundle Pricing Strategy
NEW QUESTION # 73
......
Share Latest Rev-Con-201 DUMP Questions and Answers: https://www.actualtestsit.com/Salesforce/Rev-Con-201-exam-prep-dumps.html