Universal Containers is implementing Revenue Cloud for a business unit that already uses a legacy CPQ system, what consideration should be taken asthe implementation partner?
Correct Answer: C
When implementingSalesforce Revenue Cloud for a business unit that already uses a legacy CPQ system, the following considerations should be taken: AMap legacy CPQ system capabilities to ensure there is no loss of logic from the older system: It's important to understand the capabilities of the legacy CPQ system and map these to the new system to ensurethat there is no loss of functionality or business logic12. B . Transform the customer's business processes, capture new requirements for the new Revenue Cloud technology: Implementing a new system like Revenue Cloud often requires a transformation of existing business processes. It's crucial to capture new requirements that align with the capabilities of Revenue Cloud13. D . Customize Revenue Cloud's user interface so the customer experiences no major interruption to the new system: To ensure a smooth transition, it can be beneficial to customize the user interface of Revenue Cloud to match the look and feel of the legacy system. This can help minimize disruption for end users14. Reference Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across Any Channel -Salesforce Sales Salesforce Revenue Cloud: A Guide | BillingPlatform CRM Implementation Considerations- Salesforce The Ultimate Guide to Salesforce CRM and CPQ Integration Oracle CPQ Cloud and Salesforce.com Integration
Question 82
A revenue cloud customer has posted a cash payment that was created on account A by mistake. what are the steps to apply this to the correct invoice on account B?
Correct Answer: B
Scenario: A payment is posted on the wrong Account It must be applied to an invoice on a different Account Payment is already posted Salesforce Billing rules: A posted payment cannot be reparented A payment allocated to an invoice cannot simply be moved Correct process is: ✔ B - If allocated, create a refund, then create a new payment on the correct accountDetailed steps: Reverse (refund) the incorrect payment Create a new payment on the correct account Allocate that payment to the correct invoice This ensures: Proper audit trail Compliance with financial controls Correct ledger entries Why the other options are wrongOption Why Incorrect A . Allocate payment to Account B invoice Not allowed: payment is tied to Account A. C . Reparent payment to Account B Posted payments cannot be reparented. D . Cancel the payment Cancelling alone does not reverse ledger impact; refund process is required. Thus B is correct.
Question 83
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 commercialry viable?
Correct Answer: B
Question 84
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?
Correct Answer: B
Question 85
What fields are required on the usage record to load and rate the usage?
Correct Answer: B
To correctly load and rate Usage in Salesforce Billing, a Usage Record must contain the minimum required fields that allow the Billing Engine to: Identify which subscription/order product the usage belongs to Determine the billing period Retrieve the correct rating method (per unit, tiered, etc.) Apply account-level and billing-level context Roll up usage into a Usage Summary for invoicing Salesforce Billing documentation specifies that the following fields are required for rating: Required Fields for Usage RatingField Why it is required Order Product (SBQQB__OrderProduct__c) Links usage to the billable product and its pricing model Start Date/Time Used to determine billing period & usage summary matching (End Date/Time) Optional, depending on rating model Quantity Required for rating calculation Unit of Measure Required to match usage with the product's usage rate Usage Summary Lookup (optional but required for import batching) Groups usage records for processing Account Required for Billing Context Option B is the only choice that correctly includes: Order Product (mandatory for rating) Start Date/Time Quantity Unit of Measure Usage Summary Lookup Account This matches Salesforce Billing's usage rating prerequisites. ✔ Why other options are incorrect:A - Missing Order Product IDUsage cannot be rated without knowing which subscription/order product it belongs to. So A is invalid. "Matching ID" and "Matching Attribute" are not standard required fields for usage rating. Overly broad and mixes irrelevant fields. C - Includes fields that Salesforce does not require D - Only includes UOM + QuantityInsufficient. Missing the essential contextual fields (Order Product, Date/Time, Account). ✔ Final Confirmed AnswerB. lookup start date time, order product ID, unit of measure, quantity, usage summary lookup, account
