Pass the Salesforce CPQ Specialist CPQ-Specialist Questions and answers with ExamsMirror

 Requirement Overview:

A product needs to support both renewable subscriptions (annual) and evergreen subscriptions (monthly, lasting perpetually).

 Solution:

C. Renewable/Evergreen: Set the Subscription Type field to Renewable/Evergreen to support both behaviors.

D. Default Subscription Term: Allow sales reps to define whether the subscription is sold monthly or annually by exposing the Default Subscription Term field in the Quote Line Editor.

 Steps to Configure:

Navigate to the Product Record.

Set the Subscription Type to Renewable/Evergreen.

Add the Default Subscription Term field to the Quote Line Editor Field Set.

 Validation:

Confirm that sales reps can toggle between selling the product monthly or annually.

 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.

 Requirement:

Ensure that quotes are recalculated with current information prior to approval without reopening the Quote Line Editor.

 Solution:

Option A: Adding or modifying a field in the Calculating Fields Field Set automatically triggers recalculation for quotes.

Option C: Including the Calculate button on the quote layout provides users with a manual option to trigger recalculation before approval.

 Why Other Options Are Incorrect:

B and D: These require additional customization (e.g., creating a custom Lightning button or Flow) and are not standard CPQ features.

 Salesforce CPQ Reference:

The Calculating Fields Field Set and Calculate Button functionalities are well-documented as standard CPQ tools ​.

 Issue Analysis:

Products not syncing to Opportunity Products is usually caused by specific CPQ conditions or rules.

 Reasons for Failure:

B: Products with an Effective Quantity of zero are excluded from syncing.

C: Validation Rules on the Opportunity Product object may silently block the sync process if they are not met.

D: Products with a price of zero do not sync by default.

 Why Other Options Are Incorrect:

A: Missing Price Book Entries prevent quoting entirely, not syncing issues.

E: The Exclude from Opportunity checkbox applies to the Product Option, not the syncing process.

 Salesforce CPQ Reference:

CPQ guidelines for syncing Quote Lines to Opportunity Products ​.

 Requirement Overview:

Prevent users from making price changes to Quotes or Quote Lines that have already been approved.

 Solutions:

C. Validation Rule:

Create a Validation Rule to block any material changes to approved Quotes or Quote Lines.

D. Product Rule:

Use a Validation Product Rule to prevent edits to pricing fields once a Quote has been approved.

 Steps to Configure:

Validation Rule:

Navigate to Setup > Validation Rules for the Quote and Quote Line objects.

Create rules to restrict edits when the status is set to Approved.

Product Rule:

Create a Validation Product Rule targeting Quote or Quote Line fields.

 Validation:

Test by attempting to edit an approved Quote and verifying the system prevents changes.

 Scenario:

A subscription product does not appear in the Product Selection screen during search.

 Possible Causes:

A: The Active checkbox must be TRUE for the product to appear.

D: The product requires a Pricebook Entry in the corresponding Quote’s Pricebook.

E: If the Component checkbox is TRUE, the product is treated as a bundle component, not standalone, and will not appear in search results.

 Why Other Options Are Incorrect:

B: Cost records are unrelated to product visibility.

C: The Optional checkbox determines bundling behavior, not search visibility.

 Salesforce CPQ Reference:

Product visibility settings are detailed in CPQ Product Selection Configuration ​.

In Salesforce CPQ, the Option Layout field on the Product record determines how bundle options are presented in the configurator. To allow users to view all available and selected options by scrolling on a single page, the "Sections" layout is ideal. This layout organizes options into collapsible sections based on Product Features, keeping everything visible on onepage without requiring navigation steps like a wizard. Option A (Wizard) presents options step-by-step across multiple pages, which doesn’t meet the single-page requirement. Option B (assigning all options to one feature) limits organization and doesn’t address the layout requirement. Option C (Dynamic selection method) controls runtime behavior of options but doesn’t influence the single-page scrolling display. Salesforce CPQ documentation confirms that the "Sections" layout supports a scrollable, single-page view.

Background Context:When amending a contract in Salesforce CPQ, issues with net pricing arise if the amendment impacts existing subscription products. Subscription products often rely on Discount Schedules for calculating discounts, especially when quantity changes. The "Cross Order" field on Discount Schedules ensures discounts account for cumulative quantities across multiple orders or contracts.

Problem Analysis:

The reported issue involves incorrect net pricing specifically when the quantity of existing products is adjusted during contract amendments.

This aligns with the functionality of Discount Schedules, where the total quantity determines the discount applied. Without "Cross Order" enabled, Salesforce CPQ considers only the current order's quantities rather than aggregating across orders.

Root Cause Identification:

Discount Schedule and Cross Order:If the Discount Schedule associated with these products does not have "Cross Order" enabled, any amendments won't consider cumulative quantities. Instead, the system recalculates based on only the new or adjusted quantities, leading to incorrect net pricing.

Supporting Evidence:

Salesforce documentation highlights that Cross Order must be selected in the Discount Schedule for accurate discount calculations across multiple orders or contracts. Otherwise, amendments operate in isolation​​.

The feature ensures that ongoing contracts retain accurate pricing based on total historical quantities.

Recommended Resolution:

Navigate to the Discount Schedule associated with the affected products.

Verify and enable the Cross Order checkbox:

Go to Setup > Discount Schedules.

Locate the relevant Discount Schedule.

Edit the schedule and enable Cross Order.

Test the functionality by amending the contract and verifying the net pricing calculations.

Preventative Actions:

For all subscription-based products relying on Discount Schedules, ensure Cross Order is enabled during initial configuration.

Provide training to Salesforce CPQ admins to understand the implications of Discount Schedule settings on pricing.

By following these steps and verifying the Discount Schedule configuration, the issue can be resolved, ensuring consistent and accurate net pricing during contract amendments.

 Behavior Explanation:

The Price Rule fails to apply correctly because formula fields used in Price Conditions are not natively supported for the first evaluation cycle.

The system requires additional recalculation to fetch and calculate the correct formula-derived value.

 Root Cause:

Price Rule evaluation relies on static field values at runtime. When formula fields are used, their values may not be immediately available due to dependency on intermediate calculations.

 Salesforce CPQ Reference:

Salesforce documentation discourages the use of formula fields in Price Conditions for real-time calculations and recommends using static fields or Lookup Queries for consistent behavior ​.