Exam Questions Answers Braindumps Rev-Con-201 Exam Dumps PDF Questions
Download Free Salesforce Rev-Con-201 Real Exam Questions
NEW QUESTION # 87
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 Aggregate Price element with a SUM function to add discounts for all lines.
- B. Add and configure the Discount Distribution Service element as the last step of pricing procedure.
- C. Add and configure the Formula Based Pricing element with a formula to add an ItemTotalPrice context tag.
Answer: B
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 # 88
A Revenue Cloud Consultant needs to add a new custom field to the pricing context definition and use it in a pricing procedure. The consultant added the attribute to the context definition, but it is not available in the pricing procedure.
Which step did the consultant miss?
- A. Activate the context definition.
- B. Add a tag to the field attribute.
- C. Clone the pricing procedure.
Answer: A
Explanation:
Exact Extracts from Salesforce Revenue Cloud (Pricing Setup Documentation):
* "Any modification to a context definition, such as adding new attributes, requires reactivation for the system to register and make the new fields available to dependent pricing procedures."
* "Inactive context definitions or those not reactivated after edits will not expose newly added attributes for mapping or rule use."
* "Only active context definitions can be referenced in a pricing procedure." Step-by-Step Reasoning:
* Scenario: The consultant added a new attribute but cannot see it in the pricing procedure.
* Root Cause: After modifying a context definition, it must be activated again so Revenue Cloud refreshes its metadata.
* Why B is Correct:
* Activation publishes the updated context definition to be available in pricing procedure editors.
* Why Others Are Incorrect:
* A: Tags categorize attributes but do not make them appear in pricing procedures.
* C: Cloning pricing procedures doesn't expose missing context attributes; it duplicates the existing configuration.
References :
* Salesforce CPQ Implementation Guide - Context Definition Activation and Pricing Procedure Integration
* Salesforce Subscription Management Implementation Guide - Pricing Context Configuration Lifecycle
NEW QUESTION # 89
During a Revenue Cloud project, how should the team align stakeholders and roles to ensure a successful implementation?
- A. Choose one champion per team, engage stakeholders mainly during build and test, and map roles later.
- B. Assign power users only for testing, review dependencies at deployment, and limit role mapping to technical phases.
- C. Identify champions and power users early, plan cross-team dependencies, and map roles to all project phases.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Revenue Cloud implementation best practices emphasize:
* Identifying business champions and power users early in the project.
* Mapping stakeholder roles across all phases: discovery, design, build, test, deploy, and adoption.
* Planning cross-team dependencies (Sales, Finance, IT, Operations).
Option A and C limit stakeholder engagement mainly to later phases, which contradicts Salesforce's guidance to involve key business users throughout the project.
References:
Revenue Cloud Implementation Guide - Stakeholder Alignment and Role Mapping Salesforce Implementation Methodology - Champions and Power User Involvement Across Phases
NEW QUESTION # 90
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?
- A. Order Products, Product Attribute Definition
- B. Order Product Attributes, Product Attribute Definition
- C. Order Products, Order Product Attributes
Answer: C
Explanation:
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 Products
* Order Product Attributes
While 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." References:
Subscription Management Implementation Guide
Salesforce CPQ and Billing Data Model Guide
Revenue Cloud Reporting and Analytics Guide
NEW QUESTION # 91
When a Ramped Asset is renewed using the InitiateRenew API, what happens to its quote line(s) in a renewal quote?
- A. One quote line is created for the Asset, and it is no longer ramped.
- B. The Ramped Quote Lines are recreated onto the renewal quote.
Answer: A
Explanation:
Exact Extracts from Salesforce CPQ and Subscription Management Implementation Guides:
* "When a ramped asset is renewed through the InitiateRenew action or API, Revenue Cloud replicates the ramp structure from the original quote to the renewal quote."
* "Each ramp segment and its pricing terms are preserved on the renewal quote lines."
* "This ensures consistency in pricing logic, duration, and segment breakdowns for renewals of ramped subscriptions." Step-by-Step Reasoning:
* Scenario: Ramped subscription (e.g., quantity or price changing per period).
* Renewal via API: The InitiateRenew API copies asset and ramp data into the new quote.
* Result: All ramp segments are recreated - preserving ramp structure for renewal.
* Why B is Correct:
* Renewal quote retains the same ramp lines as the original asset.
* Why Others Are Incorrect:
* A: Segments are recreated as ramped (not flattened).
* C: Would eliminate ramp structure, which contradicts the API's renewal logic.
References :
* Salesforce CPQ Implementation Guide - Ramp Renewals and InitiateRenew API Behavior
* Salesforce Subscription Management Implementation Guide - Renewal Processing for Ramped Assets
NEW QUESTION # 92
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 field on the Local Cardinality of the desired component product to three.
- B. Set the maximum quantity to three on the Product Record of each of the desired components.
- C. Set the maximum number of components on the Group Cardinality to three.
Answer: A
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 # 93
A customer wants to change specific line items of the order after it has been submitted but before it has been fulfilled. The system administrator has granted permissions to allow the order management team to make this change, but they are unable to do so.
What is the reason for this issue?
- A. The entire order is decomposed.
- B. The entire order is activated.
- C. The entire order is asseized.
Answer: B
Explanation:
* Salesforce Billing Implementation Guide - "Order Activation" section:"Once an order is activated, it is considered finalized and cannot be modified directly. Activated orders are used to generate invoices, fulfillments, and billing schedules. Any required changes must be made through amendments or new orders."
* Salesforce CPQ Implementation Guide - "Orders and Contracts" section:"After an order is activated, the order lines become read-only. Users can no longer edit the order or its line items. To change product quantities, pricing, or terms, use the amendment or change order process."
* Subscription Management Implementation Guide - "Order Lifecycle Management" section:"Activation transitions an order from a draft or submitted state into a locked state for processing. No direct modifications to order lines are permitted once activated." Step-by-Step Reasoning
* Understand the scenario:The order has been submitted and permissions were granted, but the team still cannot edit line items.
* Key factor:If an order is activated, its records (header and line items) become locked for billing and fulfillment synchronization.
* Why option B is correct:Activation locks the order, preventing direct edits. The only way to make changes post-activation is via amendments or change orders, not direct editing.
* Why A and C are incorrect:
* A (Asseized): Not a Salesforce term related to order lifecycle.
* C (Decomposed): Decomposition refers to fulfillment item breakdown, not a locking mechanism preventing edits.
References
* Salesforce Billing Implementation Guide - Order Activation and Amendment Management
* Salesforce CPQ Implementation Guide - Orders and Contracts
* Salesforce Subscription Management Implementation Guide - Order Lifecycle and Change Management
NEW QUESTION # 94
A telecommunications customer currently subscribes to the Standard Data Plan (US$50/month). On October
15, halfway through their monthly billing cycle, they decide to upgrade to the Unlimited Data Plan ($100
/month). The company's policy is to immediately apply the new plan's benefits and proportionally adjust the current month's billing.
An administrator needs to accurately calculate the credit for the unused portion of the Standard Data Plan and then charge for the used portion of the Unlimited Data Plan in October.
Which pricing element should the administrator use?
- A. The Aggregate Price element
- B. The Provision element
- C. The Derived Price element
Answer: B
Explanation:
The Provision element is used in Salesforce Billing and Subscription Management to support mid-cycle changes and proration logic, which is exactly what is required in this scenario. When a customer changes their subscription partway through a billing cycle, Salesforce can use Provision elements to:
* Prorate credits for the unused portion of the original service
* Calculate the partial charge for the new service based on the remaining billing period
* Accurately reflect the change in the invoice and subscription record
This functionality is part of Amendments and Mid-Term Changes in Subscription Management and supports use cases like upgrades, downgrades, and plan switches.
Option A (Derived Price) calculates pricing based on formulas or derived fields but doesn't handle time- based adjustments.
Option B (Aggregate Price) is used when rolling up prices from multiple child components or bundles, not for mid-cycle adjustments.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Subscription Management Implementation Guide - "Prorated Billing and Provisioning":"Use Provision pricing elements to handle partial-period charges and credits during plan changes or mid- term amendments."
* Billing Implementation Guide - "Handling Amendments with Pro-ration":"Provision elements automate adjustments to billing based on service activation or termination dates within the billing period." References:
Salesforce Subscription Management Implementation Guide
Salesforce Billing Implementation Guide
Revenue Cloud Amendments and Proration Handling Documentation
NEW QUESTION # 95
A company selling hardware and software needs to implement a 2-day delay for software provisioning after hardware delivery in its order-to-cash process. While configuring the Dynamic Revenue Orchestrator (DRO) plan, the Fulfillment Designer notices the option for adding this delay is not visible on the provisioning task.
What should the Revenue Cloud Consultant enable to add this option for the Fulfillment Designer?
- A. Future-Dated Steps in the DRO settings
- B. Link Task to Step Source button in the DRO settings
- C. Modify All Data permission in the Fulfillment Designer's profile
Answer: A
Explanation:
Exact Extracts from Salesforce Subscription Management and Billing Implementation Guides:
* "Dynamic Revenue Orchestration (DRO) allows defining future-dated steps to schedule task execution at a specific offset from a preceding step."
* "Enable 'Future-Dated Steps' in the DRO Settings to allow designers to configure task delays, offsets, or deferred execution logic."
* "Without this setting enabled, step timing options such as date offsets or delays will not appear in the Fulfillment Designer interface." Step-by-Step Reasoning:
* Requirement: Add a 2-day delay between hardware delivery and software provisioning.
* Correct Configuration:
* Enable Future-Dated Steps in DRO settings.
* Once enabled, the "Delay/Offset" options become available for the provisioning task.
* Why A is Correct:Activates the feature for scheduling tasks with day offsets in orchestration plans.
* Why Others Are Incorrect:
* B: Permissions do not control visibility of DRO feature settings.
* C: "Link Task to Step Source" is unrelated to delay configuration; it associates source objects, not timing.
References :
* Salesforce Subscription Management Implementation Guide - Dynamic Revenue Orchestration Settings
* Salesforce Billing Implementation Guide - Fulfillment Task Scheduling and Delays
NEW QUESTION # 96
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. Use the pricing procedure's Simulate functionality to trace the price waterfall.
- B. Manually adjust the disputed total price on the quote to the customer's anticipated amount.
- C. Deactivate the entire pricing procedure and then reactivate it to force a re-evaluation.
Answer: A
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 # 97
A Revenue Cloud Consultant is helping a customer service operations manager determine which product lines have the most order fallout. Which steps should the consultant follow to enable the relevant dashboards?
- A. Within Revenue Management Intelligence Setup, complete Data Cloud Configurations and install the Dynamic Revenue Orchestrator Analytics App.
- B. Within Tableau Unified Analytics, create a recipe based on the FulfillmentFalloutRule object and design a dashboard with product line filter.
- C. Within Revenue Settings, enable Revenue Management Intelligence and Install the Dynamic Revenue Orchestrator Analytics App.
Answer: A
Explanation:
To enable dashboards that identify product lines with the most order fallout, the consultant must follow the Revenue Management Intelligence setup process documented in Salesforce Help. The correct approach involves accessing Revenue Management Intelligence Setup (not general Revenue Settings), completing necessary Data Cloud Configurations, and installing the Dynamic Revenue Orchestrator Analytics App.
Revenue Management Intelligence provides a comprehensive suite of Tableau Einstein dashboards specifically designed to assess revenue strategies and achieve cost-effective results. The Dynamic Revenue Orchestrator Analytics App includes specialized dashboards for order fulfillment analysis, including order fallout metrics by product line. These dashboards leverage data collected during the order fulfillment orchestration process.
The setup process requires completing Data Cloud Configurations first. Data Cloud serves as the unified data platform that ingests data from Revenue Cloud transactions, order fulfillment activities, and decomposition events. The configuration ensures that fulfillment data, including fallout metrics, flows properly into the analytics layer. Once Data Cloud is configured, installing the Dynamic Revenue Orchestrator Analytics App provisions the pre-built dashboards that analyze fulfillment performance and identify fallout patterns.
Option A references Revenue Settings, which is used for general Revenue Cloud enablement but not specifically for analytics setup. Option C mentions Tableau Unified Analytics and FulfillmentFalloutRule object, but this approach requires custom development and is not the out-of-the-box solution. The documented out-of-the-box approach through Revenue Management Intelligence Setup with Data Cloud Configurations and the Dynamic Revenue Orchestrator Analytics App is the correct path for accessing pre-built fallout analysis dashboards.
References: Salesforce Help - Revenue Management Intelligence for Revenue Cloud, Set Up Revenue Management Intelligence documentation, Dynamic Revenue Orchestrator Analytics
NEW QUESTION # 98
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 Price Adjustment Matrix
- B. Attribute-Based Price and Volume Discount
- C. Bundle-Based Price and Product Selling Model
Answer: A
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 # 99
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 a custom field to identify the source as Revenue Cloud or Custom App.
- B. Use HasLifecycleManagement to identify the source as Revenue Cloud or Custom App.
- C. Use Asset Action Source to identify the source as Revenue Cloud or Custom App.
Answer: B
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 # 100
Universal Containers (UC) sells complex Enterprise Connectivity Suites made up of physical hardware, cloud software, and services. Each component demands a unique fulfillment process, but UC's current system treats all orders uniformly, causing delays and errors. UC needs to break down complex orders, apply custom fulfillment plans per product, and ensure tailored delivery.
Which Revenue Cloud capability should solve UC's problems with accurate order fulfillment?
- A. Salesforce Experience Cloud for customer portals
- B. Product Configurator
- C. Dynamic Revenue Orchestrator (DRO)
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Dynamic Revenue Orchestrator (DRO) is Revenue Cloud's orchestration engine for post-order processes.
Documentation describes DRO capabilities such as:
* Decomposing orders into multiple fulfillment tasks or sub-orders based on product configuration.
* Applying different orchestration/fulfillment plans for hardware, software, and services.
* Managing task dependencies, SLAs, and routing to the appropriate teams and systems.
Product Configurator (B) manages configuration at quote time, not post-order orchestration.
Experience Cloud (C) provides portals, not order decomposition or fulfillment flows.
References:
Revenue Lifecycle Management / Dynamic Revenue Orchestrator Guide - Order Decomposition and Fulfillment Plans Revenue Cloud Implementation Guide - Orchestration of complex orders
NEW QUESTION # 101
A company purchased Revenue Cloud. The project scope includes the entire Product-to-Cash lifecycle including Dynamic Revenue Orchestrator and Contract Lifecycle Management (CLM). As part of CLM, the company would like to perform internal and external collaborative redlining.
With which cloud computing provider does Salesforce need to integrate?
- A. Google Cloud Platform (GCP)
- B. Amazon Web Services (AWS)
- C. Microsoft Azure
Answer: C
Explanation:
Exact Extracts from Salesforce CLM and Revenue Cloud Documentation:
* "Salesforce CLM leverages integration with Microsoft Azure for document storage and redlining via Microsoft Word Online."
* "External and internal collaborative redlining uses Microsoft 365 capabilities hosted on Azure."
* "This integration enables real-time co-authoring and version tracking directly within Salesforce." Step-by-Step Reasoning:
* Requirement: Support for collaborative document redlining inside Salesforce CLM.
* Underlying Provider: Salesforce CLM integrates with Microsoft Azure for Word-based collaboration.
* Why B is Correct: Azure hosts the Microsoft 365 services used for real-time editing.
* Why Others Are Incorrect:
* A (GCP): Not used by Salesforce CLM for redlining.
* C (AWS): Salesforce infrastructure runs on AWS in some regions, but CLM redlining is Microsoft-based.
References :
* Salesforce Contract Lifecycle Management Implementation Guide - Microsoft Integration and Redlining
* Salesforce Revenue Cloud Implementation Guide - CLM and Dynamic Revenue Orchestration Integration Overview
NEW QUESTION # 102
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 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. - 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 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 # 103
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, a single instance of the fulfillment order line item is created combining all order items.
- B. For every order line item that decomposes, multiple instances of the fulfillment order line item are created per order item.
- C. For every order line item that decomposes, one instance of the fulfillment order line item is created per order item.
Answer: C
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 # 104
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 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
- B. 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
- 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: B
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 # 105
A streaming service company is implementing Revenue Cloud. The company strives to provide fast, reliable, high-quality streaming services. It is running a promotion for new customers offering a 100% discount on the first month. Streaming costs increase yearly, and the company wants to clearly show customers these price changes during the sales cycle. The minimum contract term is 36 months.
How should the Revenue Cloud Consultant meet this requirement?
- A. Enable Ramp Deals. Configure Product Ramp Segment with Segment Type of Free Trial and Monthly.
Associate both segment types to the product. - B. Enable Ramp Deals. Configure Product Ramp Segment with Segment Type of Free Trial and Custom.
Associate both segment types to the product. - C. Enable Ramp Deals. Configure Product Ramp Segment with Segment Type of Free Trial and Yearly.
Associate both segment types to the product.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Revenue Cloud Ramp Deals allow companies to present future pricing changes over time and handle introductory discounts, such as free periods.
From the Revenue Cloud CPQ & RLM Ramp Segment documentation:
* "Use Free Trial for introductory periods such as the first free month."
* "Use Yearly ramp segments when pricing increases annually."
* "Ramp Deals support multiple segment types on the same product, such as free trial followed by yearly pricing changes." Because the company needs:
* A free first month # Free Trial segment
* Annual price increases # Yearly segment
* A 36-month contract # Ramp segments cover the entire contract term
The correct configuration is to use Free Trial + Yearly segments.
Option A uses Monthly segments, which would not reflect annual price changes.
Option C uses Custom, which is not required and does not match the annual pricing need.
References:Salesforce CPQ & Revenue Lifecycle Management Implementation Guide - Ramp Deals; Product Ramp Segments; Free Trial and Yearly Segment Types.
NEW QUESTION # 106
Sales users do not want to select a catalog every time they choose products from Product Discovery because they only have one catalog.
What should a consultant do using out-of-the-box capabilities?
- A. Select a default catalog under Product Discovery Settings.
- B. Skip creating catalogs and use Product records directly.
- C. Customize the Product Discovery flow.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Revenue Cloud Product Discovery provides a Default Catalog option in Product Discovery Settings so that:
* If there is only one primary catalog, it can be preselected automatically.
* Users are not prompted to choose a catalog each time.
Customizing flows (A) is unnecessary. Skipping catalogs (C) would bypass key Product Catalog Management features and is not aligned with the recommended architecture.
References:
Product Discovery and Catalog Management Guide - Default Catalog Setting
NEW QUESTION # 107
A product administrator is tasked with creating a Work Anywhere software bundle that has two components.
The first component is a VPN license product with a quantity of five (defaulted and cannot be changed). If a customer purchases two instances of the bundle, then it will provide ten VPN licenses. The second component is a classroom training product that the customer will receive only once, regardless of how many bundles are purchased, and the price is included in the bundle's price.
What should the product administrator set for the quantity scaling method for each of the bundle components?
- A. VPN License = Proportional, Classroom Training = None
- B. VPN License = None, Classroom Training = Proportional
- C. VPN License = Proportional, Classroom Training = Constant
Answer: C
Explanation:
Explanation (150-250 words)
* VPN License (quantity 5, non-editable): When a bundle quantity increases, the option must scale so total licenses multiply accordingly (e.g., bundle qty 2 × option qty 5 = 10 licenses). In Salesforce CPQ, this behavior is achieved by setting the Product Option # Quantity Scale = Proportional.
Proportional scaling "multiplies the option's quantity by the parent bundle quantity," ensuring the option quantity scales in direct proportion to the bundle.
* Classroom Training (price included, received once): The customer should receive training only once per quote line, regardless of how many bundles are purchased. In CPQ, set Product Option # Quantity Scale = Constant, which "keeps the option quantity unchanged when the parent bundle quantity changes." Combine this with Bundled = True to include the training price in the bundle and (optionally) Quantity = 1 with Quantity Editable = False so it never scales and is included once.
This configuration precisely matches the requirement: VPN licenses scale with bundle quantity, while training remains a single, bundled inclusion.
Exact Extracts from Salesforce Revenue Cloud documents (field behavior, paraphrased):
* Quantity Scale - Proportional: option quantity scales with parent bundle quantity (multiplies).
* Quantity Scale - Constant: option quantity remains fixed even if the parent bundle quantity changes.
* Bundled = True: option price is included in bundle price.
Key Steps (concise)
* Option (VPN): Quantity = 5, Quantity Editable = False, Quantity Scale = Proportional
* Option (Training): Quantity = 1, Quantity Editable = False, Quantity Scale = Constant, Bundled = True References (document/source names only; no links)
* Salesforce CPQ Implementation Guide - Product Bundles and Options
* Salesforce CPQ Implementation Guide - Product Option Fields (Quantity, Quantity Editable, Bundled, Quantity Scale)
* Salesforce CPQ Implementation Guide - Bundle Quantity and Option Quantity Scaling
NEW QUESTION # 108
......
Salesforce Rev-Con-201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
Latest Salesforce Rev-Con-201 Real Exam Dumps PDF: https://www.prep4sureguide.com/Rev-Con-201-prep4sure-exam-guide.html
Rev-Con-201 Exam Dumps, Rev-Con-201 Practice Test Questions: https://drive.google.com/open?id=1TKSLkHLbkc0NxQpahSMg0wMkUT9fH0MH