Salesforce CPQ-Specialist Salesforce Certified CPQ Specialist (WI25) Exam Practice Test

 Requirement Overview:

Reference specific Error Condition records in the Advanced Condition field of a Product Rule.

 Solution:

Use the Index field value from the Error Condition record in the Advanced Condition formula.

 Example:

If the Index field value is 1 for a specific Error Condition, reference it as 1 in the Advanced Condition (e.g., 1 AND 2).

 Requirement:

Apply a 10% discount to Product A on the Quote Line if the customer has previously purchased Product A (stored as an Asset).

 Solution:

Summary Variable:

Sum the Quantity field on Asset records for Product A.

Price Condition:

Verify that the Summary Variable is greater than 0 to confirm the customer has purchased Product A.

 Why Other Options are Incorrect:

B: Quote Lines do not track prior purchases; Assets do.

C, D: These do not align with the requirement to verify prior purchases via Assets.

 Salesforce CPQ Reference:

Summary Variables and their use in Price Rules are documented under CPQ Discounting Guidelines ​.

 Requirement:

Maintenance and Support products must display in separate sections during configuration.

Support products should appear above Maintenance products.

 Solution:

Product Features are used to organize Product Options into sections.

The Number field on Product Features determines the order in which the sections appear.

Support should have a lower Number value to appear above Maintenance.

 Salesforce CPQ Reference:

The Product Features Configuration Guidelines explain how to use features and their ordering mechanisms ​.

 Requirement Overview:

Universal Containers needs to attach required PDF documents stored in Salesforce Documents to the Quote output.

 Solution:

Use the Additional Document feature on the Quote Template to include PDF files in the generated output.

 Steps to Configure:

Navigate to the Quote Template.

Create an Additional Document for each required PDF:

Reference the document stored in Salesforce.

Save the Quote Template.

 Validation:

Generate a Quote document and confirm that the Additional Documents are included as attachments.

 Requirement Overview:

Limit the Product Options displayed in a bundle based on the service level selected by the user via a Configuration Attribute.

 Solution Details:

Selection Price Rule: Use a Selection Price Rule to dynamically show or hide Product Options based on the selected value of the Configuration Attribute.

Apply Immediately: Ensures that changes based on the service level selection occur in real-time during configuration.

 Steps to Configure:

Create the Selection Price Rule:

Define the Price Rule with a Condition targeting the Configuration Attribute value.

Use a Price Action to show or hide Product Options.

Set Apply Immediately:

Navigate to the Configuration Attribute.

Set Apply Immediately to TRUE.

 Validation:

Test the bundle configuration by changing the service level and verifying the Product Options displayed dynamically update.

 Requirement:

Ensure the Warranty Period from the Product is correctly transferred to the Asset record.

 Solution:

Create a twin field on the Quote Line because:

The Quote Line stores product-specific information during quoting.

When the Quote is contracted, the twin field ensures the value is passed to the Order Product and then to the Asset record.

 Why Other Options Are Incorrect:

A: The Product Option is used within bundles and does not directly transfer to the Asset.

B: The Order Product receives data from the Quote Line, so the twin field must originate there.

C: The Opportunity Product is not involved in the CPQ twin field data flow.

 Salesforce CPQ Reference:

Twin fields and their data flow from Quote Line to Asset are detailed in CPQ Field Mapping Documentation ​.

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

 Scenario:

Original subscription: $600 Net Unit Price × Quantity 10 × 24 months = $14,400.

Refund: Ten months into the contract, 14 months remain unused.

 Calculation:

Refund amount = ($600 × 10 × 14) ÷ 24 = -$3,500.

Amended subscription refund (Quantity = 0): 14 months refund prorated = -$2,500.

 Why Other Options Are Incorrect:

A, C, D: The refund calculations either overstate or understate the prorated refund based on the subscription term and remaining months.

 Salesforce CPQ Reference:

Prorated refunds and subscription amendments are explained in CPQ Subscription Pricing Documentation ​.

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

 Scenario:

A tiered pricing structure requires different amounts to be applied based on the quantity purchased.

 Solution:

Use a Discount Schedule with:

Type = Slab: Ensures different price amounts are applied for each tier.

Discount Unit = Amount: Specifies fixed dollar values for each tier.

 Why Other Options are Incorrect:

A, B: Block pricing is unsuitable because the requirement is tier-based, not fixed blocks.

C: Range type does not handle tiered pricing accurately.

 Salesforce CPQ Reference:

Discount Schedules with Slab type are detailed in CPQ Discounting Guidelines ​.

 Requirement:

Ensure Configuration Attribute values are mapped only to parent bundle Quote Lines, not child Product Options.

 Solution:

Setting Apply to Product Options to False on the parent bundle ensures the Configuration Attribute’s value is mapped only to the parent Quote Line.

 Why Other Options Are Incorrect:

A: Changing Apply Immediately settings for child options does not control parent-quote mapping.

B: Auto-Select = False does not relate to mapping Configuration Attributes.

C: Apply to Product Options must be set on the parent bundle, not the Configuration Attribute itself.

 Salesforce CPQ Reference:

Configuration Attributes Mapping Behavior is detailed in CPQ Bundling Configuration Guidelines ​.

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

To allow sales reps to view a subset of products via a button in the Quote Line Editor.

 Solution:

A Custom Action with a Search Filter is configured to dynamically limit the displayed products.

 Mechanism:

The Custom Action triggers the Product Selection process, with the Search Filter applying criteria to display only the desired subset of products.

 Salesforce CPQ Reference:

Custom Actions and Search Filters are documented as the preferred method to customize product visibility in the Product Selection process .

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

 CPQ Price Calculation Sequence:

The Regular Price is calculated as part of the price waterfall, and several factors influence it.

 Key Contributors:

Prorate Multiplier: Adjusts prices for subscription products based on term alignment.

Contracted Price: Overrides the List Price for specific customers.

Discount Schedules: Apply volume or tiered discounts during price calculation.

 Why Other Options Are Incorrect:

A: Additional Discount Fields apply after Regular Price is calculated.

D: Target Customer Amount is used in quoting, not directly in Regular Price calculation.

 Salesforce CPQ Reference:

Price waterfall and Regular Price contributors are detailed in CPQ Pricing Configuration ​.

 Scenario:

Automatically select the Diamond Warranty Option in the child bundle if Premium Container is selected in the parent bundle and no warranty is selected.

 Solution:

Child Bundle Condition Level = 1: Ensures the condition applies at the child bundle level.

Child Bundle Action Level = None: Prevents overwriting user-selected options but enables automatic defaulting when none are selected.

 Why Other Options Are Incorrect:

B & C: Setting inappropriate levels may lead to overwriting user selections or incorrect rule execution.

D: Setting both levels to None results in no action or condition enforcement.

 Salesforce CPQ Reference:

Configuration rules and child bundle handling are outlined in CPQ Bundle Configuration Guidelines ​

 Scenario Breakdown:

The original subscription starts with 100 licenses.

After the first year, the count decreases to 80 licenses.

After the second year, the count increases to 120 licenses.

 Quantity Adjustments:

Original Subscription: The initial agreement is for 100 licenses over 36 months.

First Amendment: Reduces the quantity to 80 licenses for the remaining term after the first year.

Second Amendment: Increases the quantity to 120 licenses after the second year.

 Validation:

Salesforce CPQ keeps track of subscription adjustments through the Contract object.

Amendments reflect updated quantities while preserving the history of original and amended subscriptions.

 Hierarchy of Discount Schedule Application:Salesforce CPQ applies Discount Schedules based on object precedence.

Contracted Price: Overrides Discount Schedules at the Product or Feature level when specific pricing agreements are in place for an Account.

Product Option: A Discount Schedule on a Product Option takes precedence over one defined at the Product Feature level.

 Key Configurations:

Contracted Price: Navigate to the Contracted Price record and add the Discount Schedule.

Product Option: Assign the Discount Schedule on the Product Option record.

 Validation:

Test configurations to confirm the Discount Schedule is applied at the appropriate level and overrides the Feature-level Discount Schedule.

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

 Subscription Term and List Price:

Subscription Product A has a Subscription Term of 6 months with a List Price of $100.

When added to a Quote with a Term of 12 months, the List Price is prorated to account for the longer term.

 Proration and Ranged Discount Schedule:

A Ranged Discount Schedule applies discounts based on quantity, volume, or term thresholds.

For the 12-month term, the price is prorated to $200 (2 times the List Price for 6 months).

The Discount Schedule applies a 25% discount to the prorated price, reducing it to $150.

 Regular Price Calculation:

The Regular Price reflects the discounted value after applying the Discount Schedule:Regular Price=200×(1−0.25)=150×0.5=75\text{Regular Price} = 200 \times (1 - 0.25) = 150 \times 0.5 = 75Regular Price=200×(1−0.25)=150×0.5=75.

 Key Salesforce CPQ Reference Points:

Ranged Discount Schedules modify the List Price based on configured thresholds .

Subscription Pricing Logic ensures correct proration for products with terms different from the Quote Term .

 Requirement Overview:

Show or hide price-related data in the Quote PDF based on the Primary Checkbox field value.

 Solution Details:

The Conditional Print Field on Template Sections enables dynamic visibility.

Add the Primary Checkbox as a reference in the Conditional Print Field for the section containing price-related columns.

 Steps to Configure:

Navigate to the Quote Template.

Locate the section containing price-related data.

Set the Conditional Print Field to reference the Primary Checkbox.

 Validation:

Generate PDFs with the Primary checkbox set to both True and False and confirm the expected visibility of pricing data.

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

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.

To set a dynamic default value for a Configuration Attribute when the configuration page loads, automation must populate the associated Product Option field automatically. Option A uses a Flow to update the Product Option field tied to the Configuration Attribute, triggered upon record creation (e.g., when the Quote Line is initiated), ensuring the value is set dynamically at page load. Option B (Price Rule) requires manual user action ("Apply Rules"), which doesn’t meet the "moment the page loads" requirement. Option C (Quote formula field) isn’t directly supported as a default source for Configuration Attributes without additional customization. Option D (Quote Line field with Price Rule) lacks real-time dynamism and alignment with page load timing. Salesforce CPQ documentation highlights Flows as a robust solution for dynamic defaults.References: Salesforce CPQ Documentation - "Configuration Attributes" and "Using Flows in CPQ".

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The "Revised Quantity" field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn’t target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn’t directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn’t directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the "Revised Quantity" field is a key factor in amendment scenarios impacting pricing consistency.References: Salesforce CPQ Documentation - "Amending Subscriptions" and "Subscription Fields" (Revised Quantity).

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

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

To update Product Option B’s quantity in real time when Product Option A is selected, a Price Rule must trigger dynamically in the configurator. Option A sets the Evaluation Scope to "Configurator" (for real-time updates during configuration), the Configurator Evaluation Event to "Edit" (triggering when edits occur), and "Apply Immediately" on Product Option B (ensuring its quantity updates instantly). Option B (Calculator scope) applies during price calculation, not real-time configuration. Option C targets Product Option A’s immediacy, but the rule must affect B’s quantity. Option D combines Calculator scope with A’s immediacy, missing the real-time configurator need. Salesforce CPQ documentation supports Configurator scope for real-time updates.References: Salesforce CPQ Documentation - "Price Rules" and "Configurator Events".

 Requirement Overview:

Sales reps need to know when manual overrides on a Discount Schedule will remain unaffected by Admin updates.

 Key Behavior:

When the Save or Quick Save button is clicked, the manual override is committed, and the Discount Schedule changes made by the Admin will not affect it.

 Validation:

Test the behavior by manually overriding a discount, saving the Quote, and confirming that Admin updates to the Discount Schedule do not impact the saved Quote.

 Scenario:

The customer wants to increase the subscription quantity for the last month of the contract. The renewal Opportunity must reflect this change.

 Solution:

Generate an Order from the amendment Opportunity to capture the changes.

Contract the amendment Order to update the Contract.

Refresh the renewal Quote to synchronize the increased quantity.

 Why Other Options Are Incorrect:

B: Terminating the contract with a specific end date is unnecessary for this scenario.

C & D: Deleting Renewal Opportunities or Quotes adds unnecessary manual steps and risks data integrity.

 Salesforce CPQ Reference:

The process for handling amendments and renewals is detailed in Amendments and Renewal Configuration Guidelines ​.

 Requirement Overview:

Northern Trail Outfitters wants future renewals to be reflected in the Opportunity pipeline as soon as a Contract is created.

 Solution Details:

The Renewal Quoted checkbox ensures that the renewal Opportunity is created and linked to the pipeline when the Contract is generated.

 Steps to Automate:

Use a Process Builder or Flow to automatically set the Renewal Quoted checkbox on the Contract upon creation.

 Validation:

Test the process by creating a new Contract and verifying that the renewal Opportunity is added to the pipeline.

 Requirement Overview:

Product A must always be included in the bundle.

Product B should be included by default but can be removed by the user.

 Key Configurations:

Required = FALSE: This ensures that Product B is not mandatory and can be removed by the user.

Selected = TRUE: This includes Product B by default when the bundle is added to the Quote.

 Steps to Configure:

Navigate to the Product Option record for Product B.

Set Required to FALSE.

Set Selected to TRUE.

Save and test the behavior by adding the bundle to a Quote.

 Validation:

Product B should be pre-selected in the Quote Line Editor but can be deselected by the user.

This setup ensures flexibility for Product B while ensuring Product A remains mandatory​​.

 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 Overview:

The C-LID-L product (Lid) should only be selectable if the C-STOR-L product (Container) is included in the bundle.

 Key Configuration:

The Constrained Option field identifies the dependent option in an Option Constraint.

In this case, C-LID-L is the constrained option.

 Steps to Configure:

Navigate to the Option Constraint record.

Set C-LID-L as the Constrained Option.

Set C-STOR-L as the Constraining Option.

 Validation:

Add the bundle to a Quote and verify that C-LID-L is only available when C-STOR-L is selected.

In Salesforce CPQ, importing data for products and bundles requires a specific order to ensure referential integrity, as certain objects depend on others being present. The correct sequence starts with the Product (the parent record), followed by Product Features (defining sections or categories within the bundle), Product Options (specific selectable items under features), Option Constraints (rules governing option selections), and finally Configuration Attributes (additional settings for dynamic configuration). Option A reflects this hierarchical dependency accurately. Option B includes unrelated objects like Product Action and Error Conditions, which pertain to rules rather than bundle structure. Option C starts with Product Option before Product, which violates dependency rules since options require a parent product. Option D begins with Product Features before Product, which is incorrect as features need a product to associate with. Salesforce CPQ documentation emphasizes this order for successful data imports.References: Salesforce CPQ Documentation - "Importing Product Data" and "Bundle Configuration Setup".

In Salesforce CPQ, when search filters are configured with predefined values and visible to sales reps, their interaction with the filter is determined by the filter’s configuration and available operators. The behavior described here is tied to Search Filters in the Product Selection screen, which allow users to refine the list of displayed products based on specific criteria.

Search Filter Configuration:

Predefined Filter Value: Here, the filter is set with a value ("Green").

Operator: The operator “starts with” limits the search to product codes beginning with the text "Green."

Sales Rep Interaction with the Filter:

The visibility of the search filter enables sales reps to view and interact with the criteria during product selection.

Specifically, sales reps have the ability to delete the predefined text to ignore the filter and retrieve a broader or unrestricted product list.

Documentation Alignment:According to Salesforce CPQ guidelines (as referenced in the Salesforce CPQ package settings and user behaviors), if filters are not marked as "required," users can remove or modify the filter values dynamically. This is designed to offer flexibility during quoting while maintaining filter defaults for ease of use.

The interaction described above aligns with Salesforce CPQ's behavior regarding visible search filters, emphasizing that sales reps can clear the filter text unless restricted by additional customization.

Use Case Reference:

When a sales rep begins a quote and searches for products, the filter defaults to "Green."

If the rep does not want to limit the product search to codes starting with "Green," they can simply remove the text and refresh the results.

Relevant Salesforce CPQ References:

Search Filters in the Quote Line Editor section of CPQ documentation .

Guidelines for Search Filter Configuration and behaviors when visible filters are not required .

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 one page 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.References: Salesforce CPQ Documentation - "Product Bundle Configuration" and "Option Layout Options".

 Requirement:

Ensure a product priced as a Percent of Total has a minimum price of $100.

 Solution Steps:

Option A: Create a Price Book Entry of $100 to set the minimum price for the product.

Option D: Create a $0 Price Book Entry to handle scenarios where Percent of Total calculation would otherwise drop below $100.

 Why Other Options Are Incorrect:

B: The custom Percent_of_Total_Target_c field is not used for minimum pricing enforcement.

C: The Percent of Total Constraint field alone does not enforce minimum pricing.

 Salesforce CPQ Reference:

Percent of Total pricing and minimum price settings are described in CPQ Pricing Configuration ​.

 Requirement Overview:

Ensure that the Configuration Attribute value is retained when reconfiguring a bundle.

 Solution:

Create a twin field on the Quote Line object with the same API name as the Configuration Attribute. This allows the value to persist and be passed between configurations.

 Steps to Configure:

Navigate to Setup > Object Manager > Quote Line.

Create a new custom field with the same API name as the Configuration Attribute.

Test the configuration to ensure the value persists during reconfiguration.

 Requirement Overview:

Universal Containers sells a Product exclusively as part of a bundle and does not want it to appear in the Product Selection screen.

 Solution:

The Component checkbox ensures the Product is only available as part of a bundle and is hidden from the general Product Selection screen.

 Steps to Configure:

Navigate to the Product Record for the item.

Select the Component checkbox.

Save the changes.

 Validation:

Confirm that the Product is not visible on the Product Selection screen but is available within its assigned bundles.

 Requirement Overview:

Universal Containers needs to send Approval Requests to both the Deal Desk and Finance teams simultaneously.

 Solution:

Use Advanced Approvals to configure multiple Approval Steps within a single Approval Chain.

Set the steps to run in parallel to minimize the time required for approval.

 Steps to Configure:

Navigate to Advanced Approvals in Salesforce CPQ.

Create an Approval Chain with two steps: one for the Deal Desk and one for the Finance team.

Configure both steps to run in parallel by assigning them the same step number.

 Requirement:

Allow customers to return asset Products and receive credit.

 Solution:

Setting the Asset Amendment Behavior to Allow Refund enables the product to be reduced in quantity on an Amendment Quote.

Reducing the Quantity on the Amendment Quote triggers a refund process in CPQ.

 Why Other Options Are Incorrect:

A: Negative quantities are not a supported standard in Amendment Quotes.

C & D: Asset records should not be manually edited as changes must flow through Quotes and Orders.

 Salesforce CPQ Reference:

Refund handling and Asset Amendment Behavior are described in Amendment and Renewal Processes ​.

Comprehensive Detailed Step-by-Step Explanation with all Salesforce CPQ References

Understanding the Issue:

The error message, “Product cannot be refunded. The quantity of Line # cannot decrease without a corresponding update,” occurs because the default behavior prevents a decrease in asset quantities unless explicitly allowed.

Asset Conversion for Product A is set to "One per Unit," requiring each unit to be treated as a separate asset.

Key Salesforce CPQ Setting:

Asset Amendment Behavior:

This field on the Product determines how CPQ handles amendments for asset-based products.

Setting it to "Allow Refund" enables sales reps to reduce the quantity of assets during amendment quotes without generating errors​​.

Configuration Steps:

Navigate to the Product Record for Product A in Salesforce CPQ.

Locate the Asset Amendment Behavior field.

Change its value to Allow Refund.

Save the changes.

Impact of the Change:

Sales reps can now amend the quantity of Product A on amendment quotes.

The system will process the reduction in quantity without triggering an error, as the refund behavior is explicitly enabled.

Verification:

Create an amendment quote for a contract involving Product A.

Adjust the quantity of Product A and confirm that the amendment processes successfully without errors.

References:

This approach is in line with Salesforce CPQ guidelines on managing amendments for asset-based products​​.

 Field Location and API Name:

The custom text field Additional_Text__c resides on the Quote object.

In Salesforce CPQ, the correct syntax to reference fields in HTML templates is to use the merge field syntax appropriate to the object.

 Syntax Explanation:

{!quote.Additional_Text__c} directly references the field from the Quote object in a format recognized by the CPQ document generation engine.

Alternative options such as {ISBQQ__Quote__r.Additional_Text__c} reference lookup relationships and do not apply here.

 Salesforce CPQ Reference:

As per the Quote Template Content documentation, use the merge fields directly associated with the object being utilized in the template ​.

 Requirement:

Group products in collapsible sections based on Product Family in the Add Products page.

 Solution:

Set the Product Results Group Field Name in Additional Settings to Product Family. This groups products by their Product Family in the Add Products page.

 Why Other Options Are Incorrect:

A: Solution Groups apply to Quote Lines, not the Add Products page.

B: Adding fields to the Search Results Field Set does not enable grouping functionality.

C: The Product Search Plugin is unrelated to grouping.

 Salesforce CPQ Reference:

Configuring product grouping is detailed in CPQ Product Search and Results Configuration ​.

 Requirement:

Bundle products should show on the Product Selection page, but their Product Options should not.

 Solution:

Setting the Component checkbox to TRUE for Product Options ensures they are excluded from the Product Selection page and only appear within their bundles.

 Why Other Options Are Incorrect:

B: The Hidden field does not dynamically manage visibility for Product Options.

C & D: Marking products inactive makes them completely unavailable, which is not the requirement.

 Salesforce CPQ Reference:

The Component checkbox’s functionality is explained in Product Configuration ​.

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

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

 Requirement Overview:

Maintenance Feature: At least one Product Option must be selected.

Support Feature: At least one and no more than two Product Options must be selected.

 Key Configurations:

Min Options = 1: Ensures users select at least one option.

Max Options = 2: Ensures users cannot select more than two options.

 Steps to Configure:

Navigate to the Feature Record for Maintenance and set Min Options = 1.

Navigate to the Feature Record for Support and set Min Options = 1 and Max Options = 2.

 Validation:

Test the bundle in the Quote Line Editor and verify the selection behavior for both Features.

 Requirement Overview:

Calculate the List Unit Price for Cloud Storage Support based on the Percent of Total pricing settings:

Percent of Total Base = Net.

Percent of Total (%) = 10%.

 Calculation:

Total Net Price of all applicable products = $2,250.

Cloud Storage Support List Unit Price = 10% of $2,250 = $225.

 Requirement Overview:

When renewing Contracts with Premier Support, it must automatically be replaced with Premier Pro.

 Solution:

The Renewal Product field on the Product record allows admins to specify a replacement Product for renewals.

 Steps to Configure:

Navigate to the Premier Support Product record.

Populate the Renewal Product field with Premier Pro.

Save and test the renewal process to confirm Premier Pro replaces Premier Support on the Quote.

 Validation:

Ensure all renewal Quotes replace Premier Support with Premier Pro automatically.

 Requirement:

Ensure approval requests are routed to a substitute manager during the original manager's absence.

 Solution:

The Delegated Approver lookup field on the Approver record allows the admin to specify a temporary approver.

Setting the Delegation End field ensures the delegation automatically ends upon the original manager’s return.

 Why Other Options Are Incorrect:

A: Using the Next Approver field for temporary delegation is not the intended functionality.

B: Creating an Approval Rule with start and end dates is overly complex and unnecessary.

D: Replacing the original Approver record risks permanent changes and is not recommended for temporary delegation.

 Salesforce CPQ Reference:

Delegated Approval Settings are documented under Advanced Approvals Configuration Guidelines ​.

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

 Scenario Overview:

List Unit Price: Product A's standard price is $150.

Contracted Price: CK has a contracted price of $100 for Product A.

Discretionary Discount: CK negotiated a 10% discretionary discount for this deal.

 Price Calculation:

List Unit Price remains the standard price of $150.

Regular Unit Price applies the contracted price of $100.

Customer Unit Price: After applying the 10% discretionary discount on the contracted price,Customer Unit Price=100−(100×0.1)=90\text{Customer Unit Price} = 100 - (100 \times 0.1) = 90Customer Unit Price=100−(100×0.1)=90.

Net Unit Price matches the Customer Unit Price for the 10 units being purchased, which is $90.

 Salesforce CPQ Reference:

Salesforce CPQ Contracted Price logic ensures negotiated prices override the List Price, and additional discretionary discounts apply as expected ​.

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

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.

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

Understanding the Requirement:

Universal Containers wants a bundle with pre-selected Product Options.

Sales reps should mostly leave the default configuration as-is but need the flexibility to make changes when required.

Salesforce CPQ Feature Overview:

Configuration Type:

Determines whether sales reps can modify the configuration of a bundle product.

Setting it to Allowed permits the flexibility to configure without mandating it.

Configuration Event:

Defines when the bundle configurator is accessible.

Setting it to Edit prevents the configurator from opening automatically but allows sales reps to access it by clicking the "Reconfigure" link.

Configuration Steps:

Navigate to the Bundle Product record in Salesforce CPQ.

Set the Configuration Type field to Allowed. This ensures the configurator is optional and not enforced.

Set the Configuration Event field to Edit. This enables the configurator to be accessible only upon user action.

Key Behaviors:

With these settings, sales reps can use the default configuration but still make changes if needed by accessing the configurator manually.

The "Reconfigure" link in the quote line becomes available for editing.

Testing and Validation:

Add the bundle to a Quote.

Verify that the configurator does not open automatically.

Check that the "Reconfigure" link is accessible on the Quote Line for editing options.

References:

This solution is aligned with Salesforce CPQ documentation on managing bundle configurations and providing sales reps with flexible configuration options​​.

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

Provide 80 products for general access while restricting access to 20 special products for a specific user group.

 Solution:

Two Price Books:

General Access Price Book: Includes only the 80 products available to all users.

Special Access Price Book: Includes all 100 products for users with elevated access.

Guided Selling: Dynamically assigns the appropriate Price Book based on user access level, ensuring visibility is controlled.

 Salesforce CPQ Reference:

The Price Book strategy with Guided Selling is detailed in the Product and Price Configuration guidelines ​.

 Requirement:

Deploy Price Rules with Lookup Queries that reference a new Rental Rates object.

 Best Practices for Deployment Order:

Step 1: Rental Rates: Deploy the object and data it references first to ensure lookup data is available.

Step 2: Price Rules: Deploy Price Rules to establish the logic governing pricing calculations.

Step 3: Price Conditions: These evaluate criteria for the rules to execute.

Step 4: Lookup Queries: Queries must reference both the object and conditions, so deploy them after both.

Step 5: Price Actions: Set last to ensure that the actions triggered by the rules execute correctly.

 Why Other Options Are Incorrect:

A, B, D: Deploying Lookup Queries or Price Actions before Rental Rates or Price Rules may cause execution errors due to missing references.

 Salesforce CPQ Reference:

Best practices for deploying CPQ Price Rules and Lookup Queries are detailed in Salesforce documentation ​.