B. Implement lookup price rules where applicable
C. Implement Quote Calculator Plugin where Possible to replace price rules.

Answer DescriptionExplanation:

A Salesforce CPQ implementation can suffer from poor performance due to a large number of active price rules supporting complex pricing requirements. To improve performance in this area, a Revenue Cloud Consultant can consider the following tactics:

Implement lookup price rules where applicable (Option B): Lookup price rules in Salesforce CPQ allow for the mapping of data points on a quote line to data in a custom object, finding a matching record with the same values, and retrieving an associated field value from the matched record1.

This can help reduce the number of price rules needed, thereby improving performance1.

Implement Quote Calculator Plugin where possible to replace price rules (Option C): The Quote Calculator Plugin in Salesforce CPQ allows for the addition of extra functionality to the quote line editor with custom JavaScript code2. This can change how calculations are performed and manage page-level security such as field visibility2. By replacing some price rules with functionalities in the Quote Calculator Plugin, the number of price rules can be reduced, leading to improved performance2.

References:

Salesforce CPQ Lookup Price Rules

Salesforce CPQ Quote Calculator Plugin

C. using compressed image formats for image files included in the quote document

Answer DescriptionExplanation:

Reducing processing times during quote document generation in Salesforce CPQ can be achieved through various optimizations. One effective method is using compressed image formats for image files included in the quote document. This reduces the file size of the images, leading to faster loading and processing times when generating quote documents. While the specific reference to this practice is not directly available in the provided Salesforce Revenue Cloud documents, it is a widely recognized optimization technique in document generation processes to enhance performance and reduce loading times​​.

B. Complete a source to target mapping of the fields that will integrate between systems
D. Design an architecture view of how data integrates and flows between systems

Answer DescriptionExplanation:
The steps that an implementation team should take to integrate Revenue Cloud with another system are:

B. Complete a source to target mapping of the fields that will integrate between systems: This step involves defining how data fields in Revenue Cloud correspond to data fields in the external system. It is crucial for ensuring accurate data flow and integration functionality between the systems.

D. Design an architecture view of how data integrates and flows between systems: This involves creating a detailed architectural blueprint that outlines how data will be transferred and managed between Revenue Cloud and the external system. It helps in identifying potential integration challenges and ensuring that the integration supports the business processes effectively.

These steps are based on best practices in systems integration, focusing on data consistency and integrity, along with a structured approach to designing integration flows.

A. Contracted Pricing

Answer DescriptionExplanation:

Contracted pricing is a feature of Salesforce Revenue Cloud that allows sales users to create new quotes with established rate cards and account specific discounts. Contracted pricing enables sales users to honor the pricing that was originally negotiated with current customers, regardless of any changes in the product catalog or price book. Contracted pricing works by creating contracted price records for each product and account combination, and applying them to the quote lines when creating a new quote. Contracted pricing can be created manually or automatically, and can be based on existing quotes, orders, or contracts. Contracted pricing is the best option to fulfill the user story, as it can store the legacy data of the original pricing agreements and use them for future quotes.

Subscription is not the best option, as it is a feature of Salesforce Revenue Cloud that allows sales users to create recurring revenue streams from products or services that are sold on a periodic basis. Subscription does not store or apply the legacy data of the original pricing agreements, but rather uses the current product catalog and price book. Subscription is useful for creating quotes for new or renewing customers, but not for honoring the pricing that was originally negotiated with current customers. 3

Order products are not the best option, as they are records that represent the products or services that are sold to a customer through an order. Order products do not store or apply the legacy data of the original pricing agreements, but rather use the current product catalog and price book. Order products are useful for creating invoices and revenue schedules, but not for creating new quotes with established rate cards and account specific discounts.

Entitlements are not relevant to the user story, as they are records that represent the service level agreements or support terms that a customer is entitled to based on their purchase. Entitlements do not store or apply the legacy data of the original pricing agreements, but rather use the current product catalog and price book. Entitlements are useful for managing customer service and support, but not for creating new quotes with established rate cards and account specific discounts.

References:

1: Contracted Pricing - Salesforce

2: Contracted Pricing | Salesforce Subscription Management | Salesforce Developers

3: Subscriptions - Salesforce

4: Order Products - Salesforce

5: Entitlements - Salesforce

D. internal initialization →on Initialization→calculate formulas → Before Calculate→calculatequantities→ On Calculate→Price Waterfall Calculation→ After Calculate

Answer DescriptionExplanation:

The correct sequence of evaluation events for a price rule, quote calculator plugin (QCP), and CPQ package pricing engine is as follows:

Internal Initialization: This is the first step where the system prepares for the calculation process. On Initialization: At this stage, any price rules that are set to trigger ‘On Initialization’ are run. Calculate Formulas: The system evaluates formula fields.

Before Calculate: Any price rules that are set to trigger ‘Before Calculate’ are run. Calculate Quantities: The system calculates quantities, for example, bundle components. On Calculate: Any price rules that are set to trigger ‘On Calculate’ are run.

Price Waterfall Calculation: The system calculates out-of-the-box pricing tools such as block pricing, discount schedules, etc.

After Calculate: Any price rules that are set to trigger ‘After Calculate’ are run1. This sequence ensures that all calculations and price rules are applied in the correct order, providing accurate pricing information1. References:

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

https://help.salesforce.com/s/articleView?id=000388745 &language=en_US&type=1

B. Use automation to set the Tax Rule based on the value of the custom field

Answer DescriptionExplanation:

For a Revenue Cloud project where a product's taxability depends on a custom field that holds industry information, the appropriate solution is to use automation to set the Tax Rule based on the value of the custom field. This approach allows for dynamic application of tax rules to products based on industry-specific requirements, ensuring that the correct tax treatment is applied during the quoting and invoicing processes. Automation could involve using Process Builder, Flow, or Apex to update the tax rule assignments on products or quote lines based on the specified industry criteria. This ensures that products are taxed correctly according to the industry-specific regulations captured in the custom field. Reference: [Reference: Salesforce CPQ Taxation Guide, , , ]

B. To establish a communication plan between the implementation team, the customer and the work is coordinated between them
D. To get agreement on the roles and responsibilities of the implementation team and customer
E. To ensure the implementation team is aligned with the customer on assigned work.

Answer DescriptionExplanation: The reasons for establishing a governance structure as part of your Revenue Cloud project include:

B. To establish a communication plan between the implementation team, the customer, and the work is coordinated between them: This is essential to ensure clear and ongoing communication throughout the project, aligning all stakeholders towards common goals and facilitating timely resolution of issues.

D. To get agreement on the roles and responsibilities of the implementation team and customer: Defining roles and responsibilities helps in setting clear expectations, distributing tasks, and accountability which are critical for the organized progression of the project.

E. To ensure the implementation team is aligned with the customer on assigned work: Alignment on the assigned work ensures that both the implementation team and the customer have a mutual understanding of project objectives, deliverables, and expectations, leading to a smoother project flow and reducing the likelihood of misunderstandings and reworks.

These aspects are derived from the standard practices and objectives in implementing complex IT projects like Salesforce Revenue Cloud, where coordination, clear communication, and defined responsibilities are fundamental for success.

D. Experience in a selling role with quota responsibilities
E. Understanding design pitfalls and Mitigation actions to course correct

Answer DescriptionExplanation:

Excellent Communication Skills both verbal and written (A): This is crucial as it ensures clear and effective communication between all parties involved. It helps in understanding the requirements, setting expectations, and conveying plans and progress effectively.

Being effective at planning, monitoring, and reviewing (B): This is important for keeping the project on track. It involves setting realistic timelines, tracking progress against those timelines, and making necessary adjustments to ensure the project’s success.

Understanding design pitfalls and Mitigation actions to course correct (E): This involves having a deep understanding of common challenges that can arise during the implementation and how to navigate them. It also involves being proactive in identifying potential issues and taking corrective action early to prevent them from becoming major problems.

While having deep knowledge of competitor products © and experience in a selling role with quota responsibilities (D) can be beneficial in certain contexts, they are not as directly relevant to leading a revenue cloud scoping session as the other characteristics.