Free Salesforce CPQ-Specialist Practice Exam with Questions & Answers

 Requirement Overview:

A nonrenewable subscription Product priced annually.

 Key Field Configurations:

Subscription Term = 12: Specifies an annual subscription.

Subscription Type = One-Time: Indicates that the Product is nonrenewable.

Subscription Pricing = Fixed Price: Defines a flat annual price.

 Steps to Configure:

Navigate to the Product record.

Update the fields as specified above.

Save and test by adding the Product to a Quote.

 Validation:

Confirm the subscription term and pricing are applied correctly and the product does not renew automatically.

 Scenario:

Product A has no Subscription Pricing, while Product B uses Percent of Total with a shared category.

During renewal, Product A has a Net Total of zero.

 Reason:

When the Renewal Model is set to Asset-Based, only assets tied to the Contract are included in the renewal.

Since Product A has no Subscription Pricing, it is not treated as a subscription and thus has a Net Total of zero.

 Why Other Options Are Incorrect:

B: Product A is not pre-owned in this scenario.

C: The Include Net-New Products in Maintenance setting applies to maintenance scenarios, not standard renewals.

D: Asset Conversion determines asset behavior, not renewal totals.

 Salesforce CPQ Reference:

Renewal behaviors with Asset-Based Models are covered in CPQ Renewal Settings Documentation ​.

 Requirement:

Ensure that custom field data from original Quote Lines flows into Renewal Quote Lines.

 Solution:

Use twin fields on the Asset and Subscription objects to store and transfer data. Twin fields are automatically mapped during renewal processes, ensuring data flows seamlessly.

 Why Other Options Are Incorrect:

A: A formula field cannot persist data on Renewal Quotes.

B: Automatic mapping does not apply to custom fields without twin fields.

C: A Price Rule is unnecessary when twin fields handle this data flow.

 Salesforce CPQ Reference:

Twin fields and their functionality are described in CPQ Subscription Management ​.

 Requirement Overview:

Calculate the pricing steps for a subscription product with a 24-month term.

 Calculation Details:

Regular Unit Price:

Default Subscription Term = 12 months.

Adjusted for 24 months: $120 × 24 / 12 = $216.00.

Customer Unit Price:

Apply 10% Volume Discount: $216.00 × (1 − 0.10) = $194.40.

Apply 20% Additional Discount: $194.40 × (1 − 0.20) = $172.80.

Net Unit Price:

Apply 5% Partner Discount: $172.80 × (1 − 0.05) = $164.16.

 Validation:

Verify each step in the Salesforce CPQ price waterfall to ensure accuracy.

 Requirement Overview:

Universal Containers uses multiple currencies (USD, EUR, GBP) and requires specific pricing based on regions (America, Asia Pacific, Europe).

 Solution Details:

Create four Price Books, where each Price Book covers a unique combination of region and currency.

America - USD: Prices for American customers.

Asia Pacific - USD: Prices for Asia Pacific customers.

Europe - EUR: Prices for European customers using EUR.

Europe - GBP: Prices for European customers using GBP.

 Steps to Configure:

Navigate to Setup > Price Books and create a new Price Book for each combination.

Assign relevant Price Book Entries for the products in each Price Book.

Use sharing rules to restrict access to the appropriate Price Books for users in each region.

 Validation:

Ensure users can access and use the correct Price Book based on their region and currency.

 Smart Approvals Overview:

Salesforce CPQ's Smart Approvals streamline the approval process by re-evaluating previously approved records to avoid redundant approvals.

 Rejected Quotes Resubmission:

If a quote is rejected, and the user resubmits it without exceeding previously approved values, it bypasses the full approval chain and is sent directly to the person who rejected it.

This functionality minimizes unnecessary delays and ensures efficient quote handling.

 Documentation Alignment:

Smart Approvals Configuration and behavior as outlined in CPQ guidelines ensure approval efficiency ​.

 Requirement Overview:

Ensure the Standard Warranty (a Percent of Total product) generates an Order Product when a partial Order is created.

 Solution:

When generating a partial Order, selecting a Shipping Container product triggers the automatic creation of a Standard Warranty Order Product, as the warranty is based on the container’s Net Price.

 Steps to Test:

Add a Shipping Container Quote Line and the Standard Warranty Quote Line to a Quote.

Create a partial Order, selecting the Shipping Container.

Verify that the Standard Warranty Order Product is generated.

 Requirement Overview:

Universal Containers wants to hide lid Products from the Product Selection screen since they are only sold as part of a container Product.

 Solution:

By selecting the Hidden checkbox on the lid Product record, the Product is removed from the Product Selection page while remaining available within bundles.

 Steps to Configure:

Navigate to the Product Record for each lid Product.

Select the Hidden checkbox.

Save the changes.

 Validation:

Verify that the lid Products no longer appear on the Product Selection screen but remain accessible as part of their parent container bundles.

Understanding the Requirement:

Within a bundle, Products A and B must be mutually exclusive, allowing the user to select either but not both.

If both products are selected, the system should automatically remove Product B and retain Product A.

Optimal Salesforce CPQ Solution:

Product Selection Rule:

This rule dynamically evaluates conditions and executes actions, such as adding or removing products.

It is suitable for automating the removal of conflicting products based on user selections.

Summary Variables:

Used to check if both products are selected during configuration.

Implementation Steps:

Step 1: Create a Product Rule:

Navigate to Product Rules in Salesforce CPQ.

Create a new rule with the following settings:

Type: Selection

Evaluation Event: Always

Scope: Product

Step 2: Define Error Conditions:

Add two Error Conditions to evaluate if both Product A and Product B are selected:

Error Condition 1: Check if Product A is selected using a Summary Variable.

Error Condition 2: Check if Product B is selected using a Summary Variable.

Step 3: Configure Product Action:

Add a Product Action to Remove Product B if both Error Conditions are true.

Ensure the rule prioritizes retaining Product A over Product B.

Rationale for Option A:

Option A is the most direct and efficient approach, leveraging Product Selection Rules to automatically enforce the requirement.

Options C and D use alert or validation rules, which display messages and rely on user intervention, failing the requirement of automatic resolution.

Option B introduces conflicting rules with differing evaluation orders, which can lead to complex and unpredictable behavior.

Validation and Testing:

Add the bundle to a Quote and configure it to select both Product A and Product B.

Verify that Product B is automatically removed, and Product A is retained.

 Requirement Overview:

Adjust the List Price dynamically based on the geographic area using a custom Price Multiplier stored in a custom object.

 Solution Details:

Custom List Unit Price Field: Store the adjusted List Price for the specific geographic area.

Lookup Price Rule: Retrieve the multiplier from the custom object and calculate the adjusted List Price.

 Steps to Configure:

Create a Custom Field (e.g., Custom List Unit Price) on the Quote Line.

Create a Lookup Price Rule to:

Retrieve the Price Multiplier from the custom object.

Calculate and populate the custom List Unit Price field.

 Validation:

Generate a Quote and confirm the List Price reflects the appropriate multiplier for the geographic area.