REVENUE-CLOUD-CONSULTANT Practice Questions

To design a multi-leveled approval matrix for controlling discounts on quotes, Universal Containers

should consider the following:

Identify backup approvers in case the primary approver is out of the office. This will ensure that the

approval process is not delayed or stalled due to the unavailability of the primary approver. Backup

approvers can be assigned using the Delegated Approver feature in Salesforce, which allows users to

delegate their approval authority to another user for a specific period of time. 1

Define the discount threshold or limit allowed for the sales reps. This will help to enforce the pricing

policies and prevent excessive or unauthorized discounts. The discount threshold or limit can be

defined using the Approval Thresholds feature in Salesforce CPQ, which allows setting up different

approval rules based on the discount percentage, amount, or margin. 2

Document the discount approval levels for each approver. This will help to clarify the roles and

responsibilities of each approver and the criteria for approving or rejecting a quote. The discount

approval levels can be documented using the Approval Processes feature in Salesforce, which allows

creating a sequence of steps and actions that an approval request must go through. 3

Reference:

Approval Thresholds

Approval Processes

Delegated Approver

Customer Asset LifeCycle Management (CALM) is a feature of Salesforce Revenue Cloud that enables

businesses to manage the entire lifecycle of their customer assets, from creation to renewal to

termination. Customer assets are the goods and services that customers have purchased or

subscribed to, and they can be tracked and updated on a single platform. CALM provides an

aggregated view of the current customer assets on a contract, as well as their history, status, and

future changes. CALM also allows businesses to automate the creation and activation of orders,

amendments, and renewals based on the customer asset data. With CALM, businesses can gain

visibility and control over their revenue streams, optimize their customer relationships, and reduce

manual errors and inefficiencies. Reference:

https://www.salesforce.com/au/products/revenue-lifecycle-management/

https://www.g2.com/products/salesforce-salesforce-revenue-cloud/features

User stories are short, simple descriptions of a feature or functionality from the perspective of the

end user or customer. User stories are used to capture the requirements and value proposition of a

product or service in an agile framework. User stories should follow some best practices to ensure

clarity, consistency, and alignment with the business goals and user needs. 12

Some of the key steps when documenting user stories are:

Know which business process the requirement supports to categorize the user story. This helps to

prioritize and organize the user stories based on the business value and impact they deliver. It also

helps to avoid duplication and inconsistency among user stories. 3

Identify the actor or personas in this user story. This helps to define the user role, needs, goals, and

motivations that drive the user story. It also helps to create empathy and understanding for the user

and their context. 4

Identify the acceptance criteria or result for satisfying the user story. This helps to specify the

expected outcome, behavior, or functionality that the user story should deliver. It also helps to define

the scope, quality, and testability of the user story. 5

Designing the solution while the business process is being defined is not a key step when

documenting user stories. This can lead to premature or biased decisions that may not address the

real user problem or value proposition. User stories should focus on the what and why, not the how.

The solution design should be done after the user stories are validated and prioritized, and in

collaboration with the development team and other stakeholders. 6

Documenting user acceptance test scripts for the user story is not a key step when documenting user

stories. This can be done later, after the user stories are refined and detailed, and before the

development and testing phases. User acceptance test scripts are used to verify that the user story

meets the acceptance criteria and the user expectations. [7]

Reference:

1: User Stories | Examples and Template | Atlassian

2: How to Write Perfect User Stories (With Templates): A Step-By-Step Guide | airfocus

3: 10 Tips for Writing Good User Stories - Roman Pichler

4: The Anatomy of a User Story | Scrum Alliance | Includes Template

5: Best Practices to Succeed with User Stories - DZone

6: UX documentation: Guide, best practices, template

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 a Salesforce Revenue Cloud project, the role primarily responsible for project success is the Project

Manager1. The Project Manager is responsible for planning, overseeing, and leading projects from

ideation through to completion2. This includes managing resources, coordinating with different

teams, and ensuring that the project is completed on time and within budget2.

When an escalation happens, the Project Manager is typically the one who steps in to resolve the

issue. They work closely with all stakeholders, including the Solution Architect, Technical Architect,

Customer Success Manager, and Developer, to ensure that the project stays on track and meets its

objectives1.

Reference:

What Does a Salesforce Project Manager Do? - Salesforce Ben

Learn About the Salesforce Admin Role - Trailhead

Contracted Pricing is the object that stores the negotiated prices and discounts for each account and

product combination. Contracted Pricing allows sales users to create new quotes with the same

pricing terms that were agreed upon in previous contracts, without having to manually adjust the

prices or discounts. Contracted Pricing also enables businesses to maintain pricing consistency and

accuracy across different channels and systems. To use Contracted Pricing, legacy data from

accounts, contracts, and quotes need to be loaded into the Contracted Pricing object, along with the

relevant price book entries and product options. 12 Reference:

Contracted Pricing - Salesforce

Migrate Legacy Data to Contracted Pricing - Salesforce

In Salesforce Revenue Cloud, the feature needed to split Order Products into different Invoice runs is

the Invoice Group. The Invoice Group field on the order product is used to define more levels of

grouping. After the invoice run groups order products by their billing account and payment terms, it

then considers the order’s invoice grouping. This process is useful for invoicing certain types of order

products separately from your other order products1.

Reference:

Grouping Order Products into Invoices - Salesforce

To split Order Products into different Invoice runs, the feature needed is "Invoice Group." Salesforce

Billing allows for the customization of invoice groups, enabling the billing of order products that

meet specific criteria separately. This functionality is particularly useful for separating invoices with

different billing or payment terms and for consolidating several order products into a single invoice

when needed. By defining an Invoice Group ID, users can control the invoicing process for order

products more granularly, ensuring that invoicing aligns with business requirements  .

When a customer indicates the need for customization to Salesforce CPQ due to a process in a legacy

system, the first step in ensuring the requirement is accounted for in scoping is to ask follow-up

questions to ensure the legacy process has a business justification. This is important because it helps

to understand the business needs and requirements better, and ensures that the customization will

add value to the business. It’s crucial to understand the ‘why’ behind the need for customization

before proceeding with it. This approach helps in avoiding unnecessary customizations and ensures

that the solution aligns with the business objectives. Reference: Salesforce Introduces Revenue

Cloud, Starting with CPQ: 8 Most Common Reasons for Customization

The matching ID field is used to link usage records to usage summaries based on a common

identifier. This field is especially useful when there are amendments to the order products, as it

allows usage records to be uploaded to the correct usage summary without having to change the

order product ID or the usage summary ID. The matching ID field can be used as an external ID to

simplify usage uploads after amendments, as it can be populated by a workflow rule or a formula

based on certain criteria. 12 Reference:

Usage Summary and Usage Fields - Salesforce

Differences between the ‘External ID’ field and the ‘Unique ID’ field setting - Salesforce

SKU rationalization is a process that involves reviewing and trimming down the product variety to

focus on the most profitable SKUs1. This process is crucial in managing SKU proliferation, which

refers to the creation of multiple product records for various product combinations offered, even

though they are the same product, merely sold under different scenarios2.

In the context of Salesforce Revenue Cloud, SKU rationalization can be achieved through the

consolidation of products in the following areas:

B . Same product names with different attribute values: Products that are essentially the same but

have different attribute values can be consolidated. This reduces the complexity of the product

catalog and makes it easier to manage2.

D . Same product names commonly found in the same bundle: Products that are often sold together

in the same bundle can be consolidated. This not only simplifies the product catalog but also makes it

easier for customers to make purchases2.

E . Same product names with different Term length: Products that are the same but have different

term lengths can be consolidated. This can simplify the product catalog and make it easier for

customers to understand the products they are purchasing2.

Reference: 2

https://www.simplus.com/sku-rationalization-strategy/