CPQ-Specialist Salesforce Certified CPQ Specialist (WI25) Questions and Answers

Scenario Breakdown:

List Price = $100

Quantity = 5

Discount Schedule Type = Slab

Discount Unit = Percent

Slab Discount Mechanism:

In a Slab Discount Schedule, the discount applies to the units within each tier individually, not cumulatively.

If the quantity is within the first slab, no discount applies unless specified for that slab.

Calculation:

Assuming the Discount Schedule for the first slab (1–5) has a 6% discount:

Regular Unit Price = List Price × (1 - Discount Percent)

Regular Unit Price = $100 × (1 - 0.06) = $94 per unit.

For 5 units: Total Price = $94 × 5 = $470.

Validation:This approach aligns with Salesforce CPQ Discount Schedule functionality for Slab Type Discount​​.

==================

 Data Import Order for Quote Templates:

Salesforce CPQ requires Quote Template data to be imported in a structured order to ensure that relationships between objects are correctly established.

Quote Template: Base structure for the quote document.

Template Sections: Define sections of the quote.

Line Columns: Specify how data appears in tables within the quote.

Template Content: Includes HTML and text for the quote layout.

Quote Terms: Define legal or contractual terms.

Term Conditions: Conditions related to the terms.

 Salesforce CPQ Reference:

Best practices for Quote Template imports align with Salesforce CPQ implementation guides for maintaining dependencies .

 Requirement Overview:

Ensure the Renewal Quote is accurate and includes all renewable products from the original Contract.

 Solution:

C. Renewal Quoted Checkbox:

Select the Renewal Quoted checkbox on the Contract to generate Renewal Quotes automatically.

D. Renew Contracts Button:

Use the Renew Contracts button from the Account’s Contract Related List to create Renewal Quotes directly.

 Steps to Configure:

Ensure the Contract is active and associated with the correct Account.

Use either the Renewal Quoted checkbox or the Renew Contracts button to generate Renewal Quotes.

 Requirement Overview:

Display Configuration Attribute X on the configuration page of a bundle and in a Line Item Column on the output document.

 Solution Details:

Product Option: Add the Configuration Attribute X custom field to ensure it appears during the configuration process.

Quote Line: Add the same custom field to enable its display as a Line Item Column in the Quote output.

 Steps to Configure:

Create a custom field named Configuration Attribute X on the Product Option and Quote Line objects.

Add the field to the relevant field sets and templates for visibility in both the configurator and the output document.

 Requirement Overview:

Universal Containers wants the Shipping Plus product to appear at the top of the Product Selection list.

 Key Configuration:

The Sort Order field determines the sequence of Products in Product Selection.

Products with lower numerical Sort Order values appear at the top.

 Steps to Configure:

Navigate to the Product Record for Shipping Plus.

Set the Sort Order field to the lowest available value (e.g., 1).

Save and test the configuration in the Product Selection screen.

 Validation:

Ensure that Shipping Plus appears at the top of the Product Selection list.

 Requirement Overview:

Configure tiered pricing for Product A specific to a customer for all future Quotes.

 Solution Details:

Use a Discount Schedule with tiered pricing.

Assign the Discount Schedule to a Contracted Price record tied to the customer's Account.

 Steps to Configure:

Create the Discount Schedule with the desired tiers.

Navigate to the customer’s Account.

Create a Contracted Price record:

Reference Product A.

Assign the Discount Schedule.

 Validation:

Generate a Quote for the customer and confirm the tiered pricing is applied correctly.

 Requirement Overview:

Universal Containers wants to restrict sales reps to accessing only region-specific Products while allowing managers to access all Products.

 Solution:

C. Price Books per Region: Create a separate Price Book for each region, associating only the relevant Products. Share each Price Book with the respective sales reps.

D. Product Rules: Use Product Rules to hide Products from sales reps outside their assigned regions.

 Steps to Configure:

Price Book Setup:

Navigate to Price Books.

Create a Price Book for each region and associate the specific Products.

Use Sharing Rules to share the Price Books with the appropriate sales reps.

Product Rule Setup:

Create a Product Rule with a Condition to hide Products based on the user’s region.

 Validation:

Test by logging in as a sales rep and verifying that they can only see Products for their assigned region.

 Scenario Overview:

A Product Rule triggers the addition of the Conference Pass Product when a related Product is selected.

 Key Trigger Mechanism:

Product Rules with an Action to add products execute as soon as the user selects a Product on the Quote.

 Steps to Verify:

Navigate to the Product Rule for the Conference Pass.

Ensure the Evaluation Event is set to fire On Initialization or Selection.

 Salesforce CPQ Reference:

Product Rules are typically triggered based on user actions such as adding Products or configuring attributes​​.

 Requirement:Populate a Configuration Attribute with a dynamic value when the configurator page loads.

 Solution Mechanics:

Process Builder can be used to dynamically set values on records based on predefined logic.

By targeting the Product Option field, which maps to the Configuration Attribute, Process Builder ensures that the value is set upon record creation.

 Steps to Implement:

Create a new Process Builder.

Trigger on the creation of the Quote Line record (or related record based on Configuration Attribute setup).

Define criteria to determine the dynamic value.

Use the Update Records action to populate the Product Option field with the default value.

 Advantages of Process Builder:

Allows for dynamic and conditional logic.

Automates the default value population without user intervention.

 Testing and Validation:

Create a test bundle with the Configuration Attribute.

Load the configurator and verify that the attribute is pre-populated.

 Evaluation Order Logic:

Calculator Evaluation Events determine when a rule is executed:

On Initialization: Executes before other events.

Before Calculate: Executes before the calculation phase.

On Calculate: Executes during the calculation phase.

Evaluation Order: Within the same event phase, rules execute based on their Evaluation Order (lower numbers execute first).

 Why Rule B Executes First:

Rule B uses the On Initialization event, which precedes all other events, regardless of the Evaluation Order.

 Why Other Options Are Incorrect:

A, B, and C: Rules with Before Calculate or On Calculate events execute after On Initialization.

 Salesforce CPQ Reference:

Pricing rule evaluation is covered in the CPQ Pricing Logic Guidelines ​.

Requirement Overview:

A product priced at 100 USD and 95 EUR needs to be included as part of a bundle.

Solution:

Bundled Products: Setting the Bundled field to True ensures the product is included in the bundle's total price.

Configure the Price Book Entries with the required prices for the respective currencies.

Steps to Configure:

Navigate to the Product in the 2019 Price Book.

Set 100 USD and 95 EUR as the Price Book Entries.

On the Product Option, mark the Bundled field as True.

Validation:

Test the bundle by adding it to a Quote and verifying the correct pricing behavior.

===============

 Requirement:

Ensure that the cubic volume selected at the bundle level applies to all Product Options.

 Solution:

Option C: Setting the Configuration Attribute's Apply to Product Options to True ensures the selected value cascades to all Product Options within the bundle.

Option D: Creating a bundle-level Configuration Attribute allows sales reps to select a single cubic volume value that governs all Product Options in the bundle.

 Why Other Options Are Incorrect:

A: Lookup Price Rules reference external objects but are not relevant to syncing a volume value across Product Options.

B: Feature-level Configuration Attributes are scoped to specific features, not the entire bundle.

 Salesforce CPQ Reference:

The functionality of Configuration Attributes and their application to Product Options is documented in Bundle Configuration Guidelines ​.

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

 Scenario Breakdown:

List Price = $100.00 per unit.

Quantity = 21 units.

Discount Schedule:

First Level (1–11 units): 10% discount.

Second Level (11–21 units): 25% discount.

Third Level (21+ units): 50% discount.

 Slab Discount Calculation:

First Level (1–11 units):

Price = $100 × 10 = $1,000

Discount = 10% = $1,000 × 0.10 = $100

Net = $1,000 - $100 = $900

Second Level (11–21 units):

Price = $100 × 10 = $1,000

Discount = 25% = $1,000 × 0.25 = $250

Net = $1,000 - $250 = $750

Total Net = $900 + $750 = $1,700

 Validation:This matches Salesforce CPQ's standard behavior for Slab Discount Schedules, where discounts are applied per tier.

 Scenario Overview:

Asset Conversion is set to One per Unit, so each unit sold creates a separate Asset record.

 Object Relationships:

During Order and Contract processes:

Order Product: Reflects the total quantity of Product A as a single record.

Asset: Creates two Asset records, one for each unit.

 Validation:

Confirm that the Asset records show separate entries for each unit sold, while other objects (e.g., Order Product) do not duplicate records.

 Requirement:

Sales reps need to identify Product Options linked to Quote Lines in the Quote Line Editor.

 Solution:

Enabling Visualize Product Hierarchy organizes Quote Lines based on their position within the bundle, displaying the parent-child relationship.

 Why Other Options Are Incorrect:

A: The Product Option Drawer enables detail viewing but does not organize Quote Lines.

B: Preserve Bundle Structure applies to output documents, not the Line Editor.

D: Keep Bundle Together affects grouping but not hierarchy visualization.

 Salesforce CPQ Reference:

Hierarchy settings are covered in the Quote Line Editor Configuration documentation ​.

 Requirement Overview:

A Percent of Total option in a multi-level bundle must calculate its value based on other options in the same level.

 Key Configuration:

The Percent of Total Scope field determines the scope of the calculation.

Setting it to Components limits the calculation to options within the same bundle level.

 Steps to Configure:

Navigate to the Product Option record for the Percent of Total option.

Set Percent of Total Scope to Components.

 Validation:

Add the bundle to a Quote and verify that the Percent of Total calculation includes only the options at the same level.

 Requirement:

Allow users to generate output documents in Microsoft Word format.

 Solution:

The Allow Output Format Change checkbox in User Settings enables users to select alternative formats like Microsoft Word during document generation.

 Why Other Options Are Incorrect:

A: The checkbox is user-specific, not template-specific.

C: Creating a second template is unnecessary when users can dynamically change the format.

D: Template Sections do not control output formats.

 Salesforce CPQ Reference:

Configuring user settings for document generation is detailed in CPQ Quote Templates Documentation ​.

 Requirement:

Organize quoted products by project milestones and generate a separate Order for each Quote Line Group.

 Solution:

Use Salesforce automation to set the Order by Quote Line Group field on the Quote. This ensures the system generates separate Orders based on the grouping in the Quote Line Editor.

 Why Other Options Are Incorrect:

B: Relying on notes is manual and error-prone, lacking automation for generating separate Orders.

C: Validation Rules prevent specific actions but do not help organize Orders by Quote Line Group.

D: Custom picklist fields are unnecessary when Order by Quote Line Group exists as a standard feature.

 Salesforce CPQ Reference:

The Order by Quote Line Group feature is outlined in Order Management Configuration ​.

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

When a user performs a contract renewal and finds that the Price Book on the Renewal Opportunity or Quote is incorrect, the issue often arises due to the absence of a Price Book reference on the original Contract. To address this, the Renewal Pricebook ID field on the Contract must be populated. This field ensures the correct Price Book is carried over during the renewal process.

Step 1: Understand the Renewal Pricebook ID Field

Field Location: The SBQQ__RenewalPricebookId__c field is on the Contract object.

Purpose: It specifies which Price Book Salesforce CPQ should use for renewal quotes and opportunities created from the contract.

Without this field populated, Salesforce CPQ defaults to another Price Book, which can lead to inaccuracieste the Renewal Pricebook ID**

Access the Contract Record:

Navigate to the relevant Contract record in Salesforce.

Edit the Contract:

Populate the Renewal Pricebook ID field with the 18-digit Salesforce ID of the desired Price Book.

This ID corresponds to the Price Book you want Salesforce CPQ to apply during renewals.

Save the Changes:

Ensure the field is correctly updated and the changes are saved .

Step 3: **

Attempt the renewal process again by clicking Renew on the Contract.

Confirm that the Renewal Opportunity and associated Quote now reference the correct Price Book.

Step 4: Consider Automation for Future Accuracy

Automate Field Population:Use Process Builder or a Flow to automatically populate the Renewal Pricebook ID field based on the contract's associated Account or Opportunity. This reduces manual errors and ensures consistency.

Data Validation:Enforce validation rules to prevent contracts from being saved without a valid Renewal Pricebook ID .

By ensuring the Renewal Pricebook ID is coesolve the issue of incorrect Price Books during renewals and prevent similar occurrences in the future.

 Requirement:

Set Product A’s price back to its List Price ($300) for a business unit account while ignoring parent account contracted pricing.

 Solution Steps:

Option B: Create a new contracted price record for Product A at $300 for the business unit account.

Option D: Mark the Ignore Parent Contracted Prices checkbox as TRUE on the business unit account to override inherited contracted pricing.

 Why Other Options Are Incorrect:

A: This would affect all contracted prices under the parent account, which is not the desired behavior.

C: Creating a new contracted price with Ignore Parent Contracted Prices set to TRUE is redundant; the account-level setting (D) achieves this.

 Salesforce CPQ Reference:

Contracted Pricing functionality, including parent-child account handling, is outlined in CPQ Pricing Guidelines ​.

 Issue:

The validation error message appears immediately after a user sets a specific value in the Configuration Attribute, even before saving.

 Solution:

Setting Apply Immediately to False ensures that changes in Configuration Attributes do not trigger immediate validations. Instead, validations occur only upon clicking Save.

 Why Other Options Are Incorrect:

A: Evaluation Action does not exist as a field for Product Rule Error Conditions.

C: Changing the Apply Immediately field for Product Options does not affect the Configuration Attribute's behavior.

D: Setting Evaluation Event to Save applies to the rule's scope but does not address Configuration Attribute settings.

 Salesforce CPQ Reference:

Configuration Attribute Settings are explained in CPQ Configuration Attribute documentation ​.

 Simplification Method:

By adding the PDF as a required Additional Document in the Quote Template, Salesforce CPQ ensures the PDF is automatically included with each generated Quote.

 Steps to Configure:

Navigate to the Quote Template.

Add the PDF file under the Additional Documents section.

Mark it as required for automatic inclusion.

 Salesforce CPQ Reference:

The Additional Documents feature simplifies document management in Quote Templates ​.

 Scenario:

Multiple Approval Chains appear in Advanced Approvals, and the order of completion depends on the Final Approval Step value.

 Behavior:

Advanced Approvals prioritizes chains based on their Final Approval Step value, processing the chain with the lowest value first.

 Why Other Options Are Incorrect:

A: Approval Chains are not completed independently but follow the step order.

B: The display order on the screen does not determine completion order.

C: Lowest Approval Step applies to individual steps, not the entire chain.

 Salesforce CPQ Reference:

Approval Chains and step prioritization are detailed in Advanced Approvals Configuration ​.

 Root Cause:

The Primary Quote field must be included in the Calculating Fields field set to trigger synchronization between the Quote and Opportunity.

 Steps to Resolve:

Navigate to Setup > Object Manager > Quote.

Locate the Calculating Fields field set.

Add the Primary field to the field set.

 Testing:

Change the Primary Quote for an Opportunity and verify that the Quote Lines and Opportunity values sync properly.

 Salesforce CPQ Reference:

The Calculating Fields field set ensures proper updates between related objects during key actions like recalculations​​.

 Requirement Overview:

Identify any Quotes where a discount has been applied to options within a bundle.

 Solution Details:

B. Summary Variable:

Use a Summary Variable to check if any Quote Line within the bundle has a Discount > 0.

Configure the Max aggregation function to evaluate discounts.

C. Price Condition:

Add a condition to check if the Discount field (SBQQ__Discount__c) on a Quote Line is greater than 0.

 Steps to Configure:

Summary Variable:

Navigate to Summary Variables and create one with:

Target Object: Quote Line.

Aggregate Function: Max.

Aggregate Field: SBQQ__Discount__c.

Price Condition:

Add a condition to the Price Rule:

Object: Quote Line.

Field: SBQQ__Discount__c.

Operator: Greater Than.

Filter Value: 0.

 Validation:

Add bundle options with discounts to a Quote and verify that the rule identifies the discounted options.

 Requirement:

Apply different uplift rates to Product Families X and Y upon renewal.

 Solution Steps:

Option A: Set the Renewal Uplift Rate on each Subscription record for Product Families X and Y.

Option C: Configure the Account’s Renewal Pricing Method as "Uplift" to enable uplift calculations during renewal.

 Why Other Options Are Incorrect:

B and D: These options fail to apply the correct rates at the Subscription or Product Family level.

 Salesforce CPQ Reference:

Uplift rates and Renewal Pricing methods are outlined in CPQ Renewal Configuration Guidelines ​.

UESTION NO: 83

Users at Universal Containers want to know how Approval requests will be routed prior to submitting a Quote for approval.

How can the admin meet this requirement?

A. Using Native Approvals, build a custom Visualforce Page to display the Approval Process for the Quote.

B. Using Advanced Approvals, place the Preview Approval button on the Quote page layout.

C. Using Advanced Approvals, build a custom Visualforce Page to display the Approval Chains for the Quote.

D. Using Native Approvals, build a custom button to display the approval matrix to users.

Answer: B

 Requirement:

Sales reps need visibility into the Approval Chain before submitting a Quote for approval.

 Solution:

The Preview Approval button in Advanced Approvals allows users to view the Approval Chain directly from the Quote page.

 Why Other Options Are Incorrect:

A and C: Building custom Visualforce pages is unnecessary with Advanced Approvals.

D: Native Approvals do not offer a built-in preview feature.

 Salesforce CPQ Reference:

Advanced Approvals functionality, including the Preview Approval button, is detailed in CPQ Approval Configuration ​.

 Requirement Overview:

Sales reps want the Square Footage value on a Configuration Attribute to persist when renewing a Quote.

 Twin Field Mechanism:

Twin Fields ensure that data is retained and mapped between related objects.

Creating Twin Fields on the Asset and Subscription objects allows the Square Footage value to be carried forward during renewals.

 Steps to Configure:

Create a custom field for Square Footage on the Asset and Subscription objects.

Ensure the API names of these fields match the Configuration Attribute API name.

Test the renewal process to confirm the value persists.

 Validation:

The Square Footage value should automatically populate in the renewal Quote without manual entry by the sales rep​​.

 Requirement:

The processor is priced differently when sold as a standalone product versus as part of a laptop bundle.

 Solution:

Marking the processor as Bundled ensures the discounted price applies only when it is part of the laptop bundle.

 Mechanism:

When the Bundled checkbox is TRUE, Salesforce CPQ applies the discounted pricing for bundle components based on the defined Price Book Entry.

 Salesforce CPQ Reference:

Bundled pricing behavior is described in the Product Option and Bundle Configuration Guidelines ​.

 Requirement:

Automatically apply a 25% discount to a specific Product Option within a bundle.

 Solution:

Option C: The Discounted by Package field ensures that the Product Option inherits discounts applied to the bundle as a whole.

Option D: A Price Rule specifically targeting this Product Option can enforce the 25% discount when it is added to the bundle.

 Why Other Options Are Incorrect:

A: The Option Discount (%) field on the Product Feature applies discounts to all options, not just a specific one.

B: The Option Discount (%) field on the Product Option does not dynamically apply discounts based on specific scenarios.

 Salesforce CPQ Reference:

Configuration and discounting for bundles and Product Options are documented under Bundle Pricing Configuration Guidelines ​.

 Requirement Overview:

Universal Containers wants to update the Quantity of a specific Product in the Quote Line Editor via a Price Rule.

The Price Rule should target only this specific Product.

 Key Mechanism:

Use a Price Condition on the Price Rule to evaluate a Quote Line field that uniquely identifies the Product (e.g., Product Code or Product Name).

 Steps to Configure:

Navigate to the Price Rule.

Add a Price Condition:

Field: Select a field from the Quote Line that identifies the Product.

Operator: Equals.

Value: Enter the unique value (e.g., Product Code or Name).

Configure the Price Action to update the Quantity field.

 Validation:

Test the rule by adding the specific Product to a Quote and confirming that the rule updates its Quantity as expected.

 Requirement Overview:

Ensure that the Contract Name field is visible to users when initiating an Amendment.

 Key Configuration:

The Active Contract Lookup Field Set on the Contract object determines which fields appear when selecting a Contract for an Amendment.

 Steps to Configure:

Navigate to the Field Set named Active Contract Lookup on the Contract Object.

Add the custom Contract Name field to the Field Set.

 Validation:

Test the Amendment process to confirm that the Contract Name field is visible.

 Issue Context:

Users encounter a warning when searching Campaign records in the Quote Line Editor.

 Root Cause:

For Lookup fields to work correctly in Salesforce CPQ's Quote Line Editor, a Twin Field must exist on the target object (Campaign) with the same API name as the Quote Line lookup field.

 Solution Steps:

Create a custom field on the Campaign Object with the same API name as the lookup field on the Quote Line Object.

Ensure the field types match (e.g., both are Lookup fields or Text fields).

 Validation:

Test the functionality by searching for Campaign records in the Quote Line Editor. The warning message should no longer appear.

 Salesforce CPQ Documentation Reference:

This is a common configuration for CPQ Lookup fields in the Quote Line Editor​​.

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

 Requirement:

Use fixed pricing for quantity tiers without additional discounts.

 Solution Steps:

B: Marking the product as Non-Discountable prevents additional discounts.

D: Set the Pricing Method to Block to define fixed prices per quantity tier.

E: Create Block Pricing records to define fixed prices for each quantity tier (e.g., 1-5 licenses = $1,000).

 Why Other Options Are Incorrect:

A: Fixed Price is not suitable for tiered pricing.

C: Slab Discount Schedules are not used for block pricing.

 Salesforce CPQ Reference:

Tiered and Block Pricing setups are detailed in Pricing Configuration ​.

 Issue:

Quote Lines on Quote A are grouped incorrectly in the output document.

 Possible Causes:

C: Quote Line Groups: Existing Quote Line Groups on the Quote override the Group Field setting in the template.

D: Group Field in Template Section: The Group Field value in the Line Items template section may cause unexpected grouping.

 Why Other Options Are Incorrect:

A: The Modified By field has no impact on template grouping.

B: Configuration Attributes like location affect product selection, not grouping in Quote templates.

 Salesforce CPQ Reference:

Grouping behavior is explained in the Quote Templates and Line Item Configuration documentation ​.

 Approval Scenarios in Advanced Approvals:Salesforce CPQ Advanced Approvals allows flexible approval processes, including the ability to handle group approvals within a single step.

 Key Features:

Any group member may approve: If this option is configured, approval from one group member is sufficient to move the approval step forward.

All group members must approve: When this option is selected, every group member must approve the request before the step can proceed.

 Configuration Steps:

Navigate to the Approval Rule and ensure that the Approval Chain or Approval Step is configured to support group-based logic.

Specify the behavior for the group in the Approval Step Settings.

 Use Cases:

Use "Any group member may approve" for time-sensitive scenarios.

Use "All group members must approve" for critical approvals that require consensus.

 Dynamic Features:

A Dynamic Feature allows administrators to automatically update or populate Product Options for a bundle based on defined rules and conditions.

 Filter Product Rules:

Applying a Filter Product Rule ensures that only relevant or newly available products appear as options for the bundle. This reduces manual maintenance while keeping the bundle dynamic.

 Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are part of advanced bundling techniques documented under Product Configuration ​.

 Requirement:

Prevent users from selecting both Product C and Product D in a bundle configuration.

 Solution:

Using an Option Constraint with Type = Exclusion ensures that selecting one product automatically excludes the other.

 Why Other Options Are Incorrect:

A: Dependency constraints ensure one product depends on another, which is the opposite of the requirement.

B & D: Setting Min Options and Max Options in a Product Feature does not enforce mutual exclusivity.

 Salesforce CPQ Reference:

Option Constraints and their configuration are detailed in CPQ Bundling Guidelines ​.

 Scenario:

Apply a regional multiplier to the pricebook price and subsequently apply discounts.

 Solution:

The Customer Price field stores the post-regional multiplier price, enabling further discounting.

 Why Other Options Are Incorrect:

A: Special Price is used for manual overrides, not automated calculations.

B: Partner Price is unrelated to the customer's pricing structure.

D: List Price remains constant and does not reflect discounts or multipliers.

 Salesforce CPQ Reference:

Price Rules and field updates are detailed in CPQ Pricing Logic Guidelines ​.

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

 Requirement Overview:

Enable Renewal Uplift for the Account to adjust pricing for renewals.

 Steps to Configure:

Renewal Pricing Method:

Navigate to the Account record.

Set the Renewal Pricing Method field to Uplift.

Renewal Uplift (%):

On the related Contract record, populate the Renewal Uplift (%) field with the desired percentage increase.

 Validation:

Test the renewal process by generating a Renewal Quote and ensuring the Uplift applies to subscription pricing.

Scenario:

Renewal Pricing Method is set to List, and the Quote contains standalone fixed-price subscription and non-subscription products.

Behavior:

Discounts from the original Quote are carried forward to the renewal Quote automatically as part of the renewal process, ensuring consistency in pricing.

Salesforce CPQ Reference:

Renewal Quote generation processes consider discounting rules as part of the Renewal Pricing Method ​.

=========================

This question is a duplicate of Question No. 54, and the verified answer remains consistent.

 Requirement Overview:

Users need to define Discount Tiers where the values are treated as the Regular Price instead of amounts deducted from the List Price.

 Solution:

Configure the Discount Schedule to:

Set the Discount Unit to Amount.

Choose All from the Override Behavior picklist.

Select the Use Price for Amount checkbox to treat the tier values as Regular Prices.

 Steps to Configure:

Navigate to the Discount Schedule Record.

Set the Discount Unit to Amount.

Select All from the Override Behavior picklist.

Check the Use Price for Amount box.

 Validation:

Test the Discount Schedule to ensure the defined tier values are treated as Regular Prices.

 Requirement Overview:

Automatically split Orders by delivery location based on Quote Line Groups.

 Key Configurations:

Order by Quote Line Group: Ensures that each Quote Line Group generates a separate Order.

Ordered Field = TRUE: Triggers the creation of Orders for the Quote Lines.

 Steps to Configure:

Ensure the Order by Quote Line Group field is checked on the Quote.

Mark the Ordered field as TRUE.

Test the Order creation process to verify separate Orders are generated by location.

 Requirement Overview:

Universal Containers wants to create a subscription product that will persist indefinitely unless canceled by the customer.

 Key Configuration:

The Evergreen value in the Subscription Type field defines a perpetual subscription in Salesforce CPQ.

Using a Price Rule ensures this field is dynamically set on each Quote Line for the product, automating downstream processes such as contract generation and order management.

 Steps to Implement:

Create a Price Rule targeting the Quote Line object.

Set the Subscription Type field to Evergreen for the relevant Quote Lines.

Activate and test the Price Rule to confirm the behavior.

 Subscription Product Configuration:

Product B uses the Percent of Total pricing model based on Product A's Net Price.

Product B's Percent of Total Base is set to "Net," and its Percent of Total Target is set to Product A.

Product B's Percent of Total (%) is configured as 10%.

 Calculation:

Product A Net Total = $2,400

Product B Net Total = 10% of Product A Net Total = 2,400×0.1=2402,400 \times 0.1 = 2402,400×0.1=240.

 Salesforce CPQ Reference:

Percent of Total pricing logic is described under Percent of Total Products ​.

 Requirement Overview:

Each sales team needs access to a specific subset of products without requiring separate Price Books.

 Solution:

Use multiple bundles with validation Product Rules to restrict access to specific products based on user criteria (e.g., Profile or custom field).

This avoids the need to create and manage separate Price Books for each team.

 Steps to Configure:

Create a bundle for each subset of products.

Use Product Rules to validate and restrict access based on sales team criteria.

 Validation:

Test the Product Selection page to ensure that each sales team can access only their specific subset of products.

 Requirement Overview:

A product must be priced as 10% of the total fixed-priced products on the Quote.

 Solution Details:

Option A:

Setting the Pricing Method to Percent of Total ensures the price is calculated as a percentage of the total value of other products.

The Subscription Pricing is left blank since it is not a subscription product.

Option D:

Set the Pricing Method to List and Subscription Pricing to Percent of Total to achieve the same result with flexibility for subscription-based products.

 Issue Context:

Lookup Price Rules rely on the SBQQ__LookupObject__c field to reference the target object (e.g., Rental Rates).

If this API name is inaccurate or incorrectly input, the rule will fail to retrieve the desired value.

 Review Steps:

Go to the Price Rule record.

Check the SBQQ__LookupObject__c field. Confirm the API Name of the Rental Rates object is accurate.

Example: Ensure the API name matches exactly (e.g., Rental_Rates__c).

 Additional Checks:

Verify the Lookup Queries. Ensure the filter conditions correctly target a valid record on the referenced object.

 Salesforce Documentation Reference:This behavior follows Salesforce CPQ's guidelines on Lookup Price Rules configuration​​.

Business Requirement Context:

Universal Containers needs the ability to split Orders by the Start Dates of the Quote Lines.

Each Order generated will correspond to a unique Start Date.

Key Salesforce CPQ Features:

Order By Field: This field on the Quote allows CPQ specialists to specify the criteria for splitting orders. By selecting the SBQQ__StartDate__c field, orders will be created based on the Start Dates of Quote Lines.

Ordered Checkbox: Setting this to True ensures that the Quote Lines are converted into Orders during the ordering process.

Step-by-Step Configuration:

Navigate to the Quote in Salesforce CPQ.

Locate the Order By picklist field and set its value to SBQQ__StartDate__c. This ensures Quote Lines are grouped by their Start Dates for Order generation.

Check the Ordered checkbox on the Quote to mark it ready for Order generation.

Expected Outcome:

When the Orders are generated, CPQ will create separate Order records for each unique Start Date present in the Quote Lines.

Validation and Testing:

Create a Quote with multiple Quote Lines having different Start Dates.

Process the Quote through the Ordering process to verify separate Orders are created for each Start Date.

References:

This approach is aligned with Salesforce CPQ’s guidelines for managing multi-start date Orders and can be verified under "Guidelines for Splitting Orders" in the official Salesforce CPQ documentation​.