A sales rep needs to renew multiple assets. Some assets will be renewed at the same prices, so negotiations are unnecessary and the rep can directly create a renewal order. Some assets need to be renewed at higher prices, so the rep needs to create a quote for negotiation. When the sales rep starts the renewal process, they are not able to choose whether to create a quote or an order.How should a Revenue Cloud Consultant address the sales rep's issue?
Answer(s): C
Salesforce Revenue Cloud provides a flexible renewal strategy configuration within Subscription Management that allows users to choose between renewing via quote or directly via order. If the sales rep is not seeing the option to choose between these two paths, the most likely cause is that the system settings are configured to default to only one renewal path (e.g., only via order).According to the Subscription Management Implementation Guide, admins can update Revenue Cloud Settings to enable both renewal quote and renewal order options in the Manage Asset interface. Once enabled, the sales rep can select which approach is most suitable depending on the business scenario--negotiation via quote or quick renewal via direct order.Option A (customizing the component) and Option B (overriding flows) introduce unnecessary complexity. The functionality is already supported natively through configuration.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Asset Renewal Configuration":"Admins can configure whether the renewal process creates a renewal quote, a renewal order, or gives the user the option to choose. This is controlled via settings in Revenue Cloud Setup."Revenue Cloud Admin Guide "Manage Asset Settings":"To support both negotiation and direct renewals, enable dual-path renewal logic in the subscription management configuration settings."
Salesforce Subscription Management Implementation GuideRevenue Cloud Admin GuideSalesforce Revenue Lifecycle Setup Documentation
A product designer created the necessary products and bundles using Product Catalog Management. However, users are not able to see the products while preparing quotes.Which action should the product designer take to resolve this?
When using Product Catalog Management in Salesforce Revenue Cloud, visibility of products during quote creation (especially through Product Discovery) is controlled by the Context Definition.Contexts allow administrators to define when and for whom products are visible during the product selection process, based on criteria like sales channels, quote type, or other business rules.If products are not appearing during quote preparation, it is often due to a missing or misconfigured context definition. Assigning the correct Context Definition in Product Discovery Settings ensures that products and bundles are available during quoting based on business logic.Option A (selecting a selling model) affects how the product is priced and billed, but not its visibility.Option B (pricing procedure) impacts price calculations, not product discovery or visibility.Exact Extracts from Salesforce Revenue Cloud Documents:CPQ Implementation Guide "Product Discovery Configuration":"Ensure that context definitions are properly set so that products appear under the right conditions during quoting. Missing contexts will result in products not being visible to end users."Revenue Cloud Product Catalog Guide "Using Context for Product Availability":"Context Definitions act as filters for product discovery. Without proper context mapping, products may not show up for selection."
Salesforce CPQ Implementation GuideProduct Catalog Management DocumentationRevenue Cloud Product Discovery Settings Guide
A law firm is using Revenue Cloud's Contract Lifecycle Management (CLM) capability. The law firm creates very large Merger & Acquisitions (M&A) contracts for its commercial customers. The contract designer sets a requirement to structure and organize the content more effectively. This will help the contract designer quickly navigate the document and include the appropriate clauses, tables, and contract text in the document.How should a template designer meet this requirement?
In Salesforce Revenue Cloud's Contract Lifecycle Management (CLM) module, Sections within a document template are the best tool for organizing complex content such as M&A contracts. Sections help break large documents into logical parts, allowing contract designers to:Insert reusable clausesManage conditional logicInclude dynamic tables or fieldsFacilitate easier navigation and updatesAs per the CLM Template Designer documentation, sections enable content modularity and simplify the process of customizing contracts for each client or scenario, particularly when dealing with large and complex documents.Option A is too general -- "creating a structure" is achieved by using sections.Option B refers to child templates, which are useful for reusability but are typically added within sections and do not provide layout or navigation benefits on their own.Exact Extracts from Salesforce Revenue Cloud Documents:CLM Implementation Guide "Creating Structured Templates with Sections":"Use sections in your document templates to organize clauses, fields, and conditional content. Sections are the primary way to structure large and complex documents like M&A contracts."Contract Designer Admin Guide "Best Practices for Document Layout":"Sections allow you to modularize the content and manage visibility, clause insertion, and layout more effectively."
Salesforce Revenue Cloud CLM Implementation GuideContract Lifecycle Management Admin GuideTemplate Designer Documentation
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?
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."
Product Catalog Management GuideSalesforce CPQ Implementation GuideRevenue Cloud Rules Configuration Reference
A Revenue Cloud Consultant is asked to provide a report on ordered internet service where upload/download speed is configurable and is required.Which objects should the consultant use in a custom report to retrieve this information?
Answer(s): A
In Salesforce Revenue Cloud, when configurable products are ordered (e.g., internet service with upload/download speeds), the configured values are stored at the Order Product Attribute level. These are linked to the corresponding Order Product, which represents the actual product ordered.To generate a report that includes both:The ordered item (Order Product)Its specific configurations (upload/download speeds)You need to use a custom report type that includes:Order ProductsOrder Product AttributesWhile Product Attribute Definition (mentioned in Option B and C) defines the possible attributes at the product catalog level, it does not store the selected values made during quoting or ordering. The actual values chosen are stored in the Order Product Attribute object.This approach ensures that your report includes actual selections made by customers, not just the available options.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Order Product Attribute Usage":"Order Product Attributes store the selected values from the product configuration process and are linked directly to the corresponding Order Product."CPQ Data Model Reference "Attributes and Orders":"Reporting on configurable products requires joining Order Product with Order Product Attribute to retrieve both the product and its configured values."
Subscription Management Implementation GuideSalesforce CPQ and Billing Data Model GuideRevenue Cloud Reporting and Analytics Guide
Post your Comments and Discuss Salesforce Rev-Con-201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Rev-Con-201 content, but please register or login to continue.