Salesforce Certified Revenue Cloud Consultant Accredited Professional Practice Test - Questions Answers, Page 6

Upon noticing unacceptable performance times in Salesforce CPQ, particularly when the primary quote syncs to the opportunity, and identifying the cause as being due to extensive process builders referencing the quote and opportunity alongside other heavy customizations, the recommended strategy is to extend customization using coding best practices to improve scalability. This involves reviewing and optimizing the existing customizations, possibly refactoring process builders into more efficient code-based solutions that are better optimized for performance and scalability. This approach helps in addressing the technical debt and ensures that the Revenue Cloud solution is built on a solid and performant foundation.

The three common CPQ design mistakes to avoid while implementing CPQ for your customer are:

A .Using price book entries to handle attribute based variations instead of lookup price rules: Price book entries are not designed to handle attribute-based variations. Instead, lookup price rules should be used.These rules allow you to adjust pricing based on specific product attributes, providing more flexibility and accuracy1.

C .Creating process builders and flows to pass data between fields instead of using twin field mapping: Process builders and flows can be complex and difficult to maintain. Instead, twin field mapping should be used.This feature allows you to map fields between objects, ensuring data consistency and reducing the need for custom code1.

D .Writing customizations for product selection or validation instead of using option constraints, product rules, and bundles: Customizations can be time-consuming and costly to implement and maintain. Instead, Salesforce CPQ provides built-in features like option constraints, product rules, and bundles that can handle product selection and validation.These features are designed to enforce business rules and ensure that only valid product combinations are selected1.

https://inspireplanner.com/blog/5-common-salesforce-cpq-implementation-challenges-and-how-to-avoid-them/

A Revenue Cloud consultant needs to understand the client's business, their products or services, and their sales process before they can effectively scope a Revenue Cloud project.

A .A sample proposal the client provides to their customers: This document can give the consultant insights into the client's current sales process, pricing strategies, and customer interactions1.

B .Brochures that provide detail to the products and services the client offers: These materials can help the consultant understand the client's product offerings, their unique selling points, and how they position themselves in the market1.

D .An approval matrix documentation that describes the approvals needed before a quote is sent to the customer: This document can help the consultant understand the client's internal approval processes, which is crucial for configuring the approval workflows in Revenue Cloud2.

C .The latest release notes found at help.salesforce.com>salesforce CPQ patch notes: While these notes are important for staying updated on the latest features and bug fixes in Salesforce CPQ, they may not directly help the consultant understand the client's specific project requirements3.

E .The client's income statements and balance sheet: While these financial documents can provide valuable insights into the client's financial health and performance, they may not directly contribute to understanding the client's Revenue Cloud project requirements1.

In Salesforce CPQ, if a custom field is an input to product prices and you want a change in this field to trigger a recalculation, you should add this field to the calculating fields field set.This is because Salesforce CPQ's Advanced Quote Calculator determines quote and quote line prices in response to user or automated actions1. Therefore, adding the 'partner type' field to the calculating fields field set will ensure that setting the partner type on the quote triggers a new calculation.Reference

The CPQ Quote Calculation Sequence - Salesforce

In Salesforce Revenue Cloud, the evaluation event of a product rule specifies when the rule should be evaluated. The options are:

Load: The rule will be evaluated when the product bundle is opened.

Edit: The rule will be evaluated when the product bundle is edited.

Save: The rule will be evaluated upon Save.

Always: The rule will be evaluated during any event.

In the context of the question, the requirement is to hide the hardware firewall product option while configuring the bundle if the customer has purchased a hardware firewall in the past. This means that the rule needs to be evaluated when the product bundle is being edited, not just when it is loaded or saved. Therefore, the correct answer is ''Load and Edit''.

Reference

Salesforce CPQ Product Rules: General Considerations

Decide When Rules Evaluate Unit | Salesforce Trailhead

Product Rules - Salesforce

In Salesforce CPQ, a bundle is a group of products that are known to be sold together.There are three types of bundles: static, configurable, and nested1.The bundle configuration is a significant part of CPQ, and it can make selling complex product offerings easier by providing sales reps with premade product bundles to choose from1.However, whether a customer needs a bundle configuration or not depends on their specific needs and preferences2.Therefore, it's important to introduce the concept of bundle configuration as part of a CPQ project, but the decision to implement it should be left up to the customer2.Reference

Learn About Configuration in the Sales Process - Trailhead

Product Bundles in Salesforce CPQ - SkyPlanner

Multi Dimensional Quoting (MDQ) is a pricing functionality in Salesforce CPQ that allows you to break a long subscription into smaller segments, such as months, quarters, or years, and apply different quantities, discounts, or uplifts to each segment. This way, you can offer flexible and customized pricing to your customers based on their needs and preferences. For example, if you sell boxes based on size, you can use MDQ to create a quote with different prices for different dimensions of the boxes, such as length, width, and height. You can also adjust the prices for each dimension based on the duration of the subscription, such as offering a lower price for the first year and a higher price for the second year. MDQ helps you to create complex and dynamic quotes with ease and accuracy, and increase customer satisfaction and loyalty.Reference:

Create a Multidimensional Quote

Revenue Management Platform & CPQ Solution

Explain Multi Dimensional Quoting (Price Dimension) in Salesforce CPQ

Hold Billing is a feature of Salesforce Revenue Cloud that allows businesses to control when an order product is invoiced, based on certain criteria or events. By setting the Hold Billing field to Yes on an order product, the billing process is paused for that order product and all its usage summaries. This means that no invoice lines or invoice documents are generated for the order product until the hold is released. The hold can be released by setting the Hold Billing field to No or null, either manually or automatically through a workflow or trigger. When the hold is released, Salesforce Billing will create an invoice as soon as possible, and include all the invoice lines that were accumulated during the hold period. This ensures that the customer is billed for the full amount of the order product, regardless of the hold duration. For example, if an order product has a monthly billing frequency and a hold billing period of two months, the first invoice after the hold will include three invoice lines: one for the current month and two for the previous months when the hold was active.Reference:

https://help.salesforce.com/s/articleView?id=sf.blng_hold_billing.htm&language=en_US&type=5

https://trailhead.salesforce.com/users/officialblaze/trailmixes/revenue-cloud-get-started-with-billing

Salesforce CPQ (Configure, Price, Quote) allows admins to automate price calculations and update quote line fields1.In the context of Universal Containers, they have three product families and want to view the net totals of these families at the quote level1.The current solution involves creating three separate price rules that use summary variables to add the net total for quote lines that belong to a particular product family1.However, from a performance standpoint, it would be more efficient to use a single price rule with three price actions12.This is because price rules can inject a static value, field value, or summary variable into a quote or quote line field1.Therefore, having a single price rule with multiple price actions can streamline the process and improve performance12.Reference:12