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

ï‚· 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:

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

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 .

ï‚· 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 ​.

ï‚· 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 .

In Salesforce CPQ, Product Selection Rules automatically add products to a Quote based on defined conditions. These rules typically evaluate and execute when the Quote is saved, as this triggers the full application of rules and updates to the Quote Lines. Option D aligns with this behavior—saving the Quote ensures the Conference Pass is added. Option A (Configuration Attribute selection) relates to configurator actions, not quote-level rules. Option B (Product selection) triggers option-specific rules, not quote-wide additions. Option C (Quote calculation) updates pricing, not product additions. Salesforce CPQ documentation confirms rule execution on save.References: Salesforce CPQ Documentation - "Product Selection Rules" and "Quote Process Events".

ï‚· 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.

ï‚· Requirement Overview:

Admin needs to generate one Asset record for each unit of the Product upon contracting.

ï‚· Solution Details:

The Asset Conversion field determines how Salesforce CPQ creates Asset records from Quote Lines.

Setting Asset Conversion to One per Unit ensures that for each quantity of the Product, a corresponding Asset is created.

ï‚· Steps to Configure:

Navigate to the Product record.

Locate the Asset Conversion picklist and select One per Unit.

Save and test the configuration by creating a Quote, contracting it, and verifying the Asset creation.

ï‚· Requirement Overview:

Prevent non-admin users from editing a specific Quote Term.

ï‚· Key Configuration:

The Locked checkbox on a Quote Term record ensures that the term is non-editable for all users except admins.

ï‚· Steps to Implement:

Navigate to the Quote Term record.

Check the Locked checkbox.

Save and test by logging in as a non-admin user to confirm editing is disabled.

ï‚· 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​​.

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

ï‚· 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 ​.

ï‚· 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 ​.

Universal Containers requires a dynamic approach to display the Monthly Price column on the Quote Document only when the Payment Terms field is set to "Net 30". Here's how to achieve this:

Step 1: Create a Monthly Price Line Column

Navigate to Quote Templates in Salesforce CPQ.

Select the relevant Quote Template.

In the Line Columns related list:

Create a new Line Column for "Monthly Price."

Configure the desired settings for how the Monthly Price should display in the PDF.

Step 2: Create a Custom Formula Field

Navigate to Setup > Object Manager > Quote.

Create a custom formula field (e.g., Show_Monthly_Price) on the Quote object:

Type: Formula (Checkbox).

Formula Logic: IF(Payment_Terms__c = "Net 30", TRUE, FALSE).

Replace Payment_Terms__c with the API name of the Payment Terms field.

This formula ensures the field returns TRUE only when Payment Terms equals "Net 30."

Step 3: Configure Conditional Print Field on the Line Column

Return to the Quote Template and edit the Monthly Price Line Column.

Set the Conditional Print Field to Show_Monthly_Price.

This links the visibility of the Monthly Price column to the custom formula field you created​​.

Step 4: Validate in Quote Document

Generate a Quote Document for a Quote where Payment Terms are set to "Net 30."

The Monthly Price column should appear in the PDF.

Change the Payment Terms to a value other than "Net 30" and regenerate the document.

The Monthly Price column should not appear.

Step 5: Optional Enhancements

Discard Width When Hidden:In the Monthly Price Line Column, enable this setting to avoid column width adjustments when the column is hidden.

Test Across Use Cases:Validate across different Payment Terms to ensure robust behavior.

By using a combination of the Conditional Print Field and a custom formula field, Universal Containers can dynamically control the visibility of the Monthly Price column​​.

ï‚· 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.

ï‚· 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 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.

Understanding the Requirement:

Universal Containers wants sales reps to associate Campaign records with Quote Lines using a lookup field in the Quote Line Editor.

The requirement includes avoiding warning messages when searching for Campaign records.

Salesforce CPQ Lookup Field Behavior:

When a lookup field is added to the Quote Line Editor, Salesforce CPQ searches for records in the target object (e.g., Campaign).

To avoid warnings, the target object (Campaign) must have a specific field set named CPQ_Lookup, which defines the fields displayed in the search results.

Steps to Implement the Solution:

Step 1: Navigate to the Campaign object in Salesforce Setup.

Step 2: Go to the "Field Sets" related list and click "New."

Step 3: Name the field set CPQ_Lookup (case-sensitive).

Step 4: Add the fields you want to display in the lookup search results (e.g., Campaign Name, Start Date, Owner).

Step 5: Save the field set.

Integration with the Quote Line Editor:

The system will now use the fields defined in the CPQ_Lookup field set when sales reps perform a search for Campaign records.

This ensures the lookup field operates without errors or warnings in the Quote Line Editor.

Key Considerations:

Ensure that all required fields for identifying Campaign records are included in the CPQ_Lookup field set.

Test the lookup functionality in the Quote Line Editor to confirm smooth operation.

Validation:

Add a Campaign lookup field to a Quote Line in the Quote Line Editor and test the search functionality. Verify that the fields defined in the CPQ_Lookup field set appear in the search results without warnings.

References:

Salesforce CPQ documentation on setting up lookup fields and field sets emphasizes creating a CPQ_Lookup field set to avoid warnings

ï‚· Requirement:

Amend an active contract and adjust prices for subscriptions and assets based on new discounts.

ï‚· Solution:

Use the Amend Contract process.

Adjust prices for subscriptions or assets directly by modifying the Net Price or Price field.

Use the Refresh Prices button to apply changes to the amended contract.

ï‚· Why Other Options are Incorrect:

A: Cloning Quote Lines is unnecessary and inefficient for contract amendments.

B: Changing the contract status to Draft is not supported in standard CPQ.

D: Creating a new Price Book is not required for this use case.

ï‚· Salesforce CPQ Reference:

The Amendments Process is extensively documented in CPQ Subscription Management ​.

ï‚· 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.

ï‚· Scenario Overview:

The Additional Discount field cannot be edited during amendments by design in Salesforce CPQ.

ï‚· Explanation:

Salesforce CPQ locks certain fields on amendment Quotes to preserve the original pricing structure and prevent inconsistencies.

ï‚· Validation:

This behavior is standard and cannot be overridden without customizations.

https://help.salesforce.com/s/articleView?id=000382118 &type=1

ï‚· Requirement:

Different profiles need to see distinct sets of fields in the Quote Line Editor.

ï‚· Solution:

Create two field sets on the Quote Line object, one for each profile.

Use a text formula field named EditLinesFieldSetName on the Quote object to dynamically return the appropriate field set name based on the user’s profile.

ï‚· Why Other Options Are Incorrect:

A & B: Field sets must be created on the Quote Line object, not the Quote object.

D: This duplicates C but introduces a typo or incorrect description in the explanation.

ï‚· Salesforce CPQ Reference:

Field set configurations for the Quote Line Editor are detailed in CPQ Field Configuration Documentation ​.

ï‚· 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 ​.

Amendment Functionality:

Amendments are used to modify existing contracts by adjusting quantities, discounts, or adding products while maintaining contract continuity.

Supported Scenarios:

A: Quantity changes with new discounts can be applied during amendments.

C: New products can be added and aligned with the contract’s existing term (co-terminated).

Salesforce CPQ Reference:

Amendments are extensively documented under Contract and Subscription Management ​.

ï‚· Scenario Breakdown:

Adventure in a Box:

List Price = $10

Discount = 50%

Net Price = $5 (after 50% discount).

Premium Support:

Percent of Total Base = List Price.

Percent of Total = 10%.

ï‚· Calculation of Premium Support:

Percent of Total applies to the Net Price of Adventure in a Box.

Net Total of Premium Support = $5 × 10% = $0.50 per month.

For 12 months: $0.50 × 12 = $12.00.

ï‚· Requirement:

Minimize maintenance and ensure scalability for professional services in enterprise server bundles.

New professional services are introduced frequently, requiring dynamic handling.

ï‚· Solution Steps:

Dynamic Feature (B): Allows dynamic grouping and population of professional services products, ensuring that new services are automatically included in the configuration without manual updates.

Filter Product Rule (D): Ensures only compatible professional services are displayed by applying a filtering condition with a Product Action.

ï‚· Why Other Options Are Incorrect:

A: Custom Actions are useful for guiding users during selection but do not minimize maintenance or scale dynamically.

C: A nested bundle containing all services is cumbersome to maintain as new services are introduced.

ï‚· Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are key tools for managing scalable configurations ​.

ï‚· Requirement Overview:

Restrict sales reps to only selecting subscription Products when using the Add Subscriptions Custom Action.

ï‚· Solution Details:

The Search Filter for the Add Subscriptions action should include only subscription Products.

Setting the Filter Value to Hidden ensures that only Products matching the filter criteria are displayed.

ï‚· Steps to Configure:

Navigate to the Search Filter related to the Add Subscriptions action.

Set the Filter Value to True.

Mark the Hidden checkbox to restrict visibility to subscription Products.

ï‚· Validation:

Test the Custom Action to confirm that only subscription Products are visible.

ï‚· 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.

ï‚· 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:

Separate products into different Line Item tables by Product Family when rendering a document.

Solution:

The Group Field functionality within a single Template Section can group Line Items by Product Family dynamically, avoiding the need for multiple Template Sections.

Why Other Options Are Incorrect:

B & D: Creating multiple Template Sections for each Product Family introduces redundancy and is less efficient.

C: LineSortField sorts products but does not create separate tables.

Salesforce CPQ Reference:

Group Field functionality is explained in the Quote Templates and Template Sections guidelines ​.

ï‚· 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.

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

ï‚· 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:

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.

ï‚· Requirement Overview:

Universal Containers wants to use split Orders to manage fulfillment by separating items based on their shipping schedules.

ï‚· Key Considerations:

Component-type Options: When splitting Orders, component-type Options are treated independently and can be split into different Orders.

Bundle Structure: Splitting Orders does not maintain the bundle structure, meaning the parent-child relationships of the bundle are not preserved in the split Orders.

ï‚· Steps to Configure:

Ensure that the Order by Quote Line Group field or a custom grouping field is used to facilitate splitting the Orders based on shipment schedules.

ï‚· Validation:

Test the split Order functionality by creating a Quote with a hardware bundle and ensuring that the bundle and components can be split appropriately.

ï‚· 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.

ï‚· 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:

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

ï‚· Requirement:

Ensure a Product Rule fires only within a specific bundle.

ï‚· Solution:

Associating the Configuration Rule with the Parent Product ensures that the rule executes only during configuration of the specified bundle.

ï‚· Why Other Options Are Incorrect:

A, B, C: Associating the rule with Product records, Features, or Options does not scope the rule specifically to the parent bundle.

ï‚· Salesforce CPQ Reference:

Configuration Rules and their association with Parent Products are documented in CPQ Configuration Rule Guidelines ​.

ï‚· Requirement Overview:

A user must have the ability to approve any approval request, regardless of who the request is assigned to.

ï‚· Solution:

Granting the Modify All Data permission provides administrative privileges across all Salesforce objects, including the ability to approve any approval request in Advanced Approvals.

ï‚· Steps to Configure:

Navigate to the user’s Profile or Permission Set.

Add the Modify All Data permission.

Save and test the user’s ability to approve any request.

ï‚· Validation:

Confirm the user can approve approval requests without assignment restrictions.

ï‚· 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.

ï‚· 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 ​.

ï‚· 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:

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 .

Block pricing in Salesforce CPQ is used when a fixed price applies to a quantity range, as in this tiered pricing scenario (e.g., $1,800 for 6-10 licenses). Option A sets the Pricing Method to "Block" on the Product, enabling this model. Option E involves creating Block Pricing records for each tier (e.g., 1-5 = $1,000), defining the fixed prices. Option B (Non Discountable = True) ensures no further discounts apply, meeting the requirement. Option C (Fixed Price) applies a single price regardless of quantity, not tiered pricing. Option D (Slab Discount Schedule) is for percentage-based discounts, not fixed block prices. Salesforce CPQ documentation validates this setup for block pricing.References: Salesforce CPQ Documentation - "Block Pricing" and "Pricing Methods".

ï‚· 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 Overview:

The Require Approved Quote setting prevents certain records from being created without an approved Quote.

ï‚· Solution Details:

When this setting is enabled, Salesforce CPQ blocks the creation of Order records unless the associated Quote has been approved.

ï‚· Validation:

Test by attempting to create an Order from an unapproved Quote and confirming that the system blocks the action.

ï‚· 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.

ï‚· Requirement:

Sell a non-renewable support SKU in 1-month increments, with the ability to cancel before the agreed end date.

ï‚· Solution:

SubscriptionType = One-Time: Ensures the product is treated as a one-time charge, not renewable.

SubscriptionTerm = Number of Months: Allows the quote to define the length of the support agreement.

ï‚· Why Other Options Are Incorrect:

A and C: These configurations do not align with the requirement to sell support in defined monthly increments.

D: Marking the product as Renewable contradicts the requirement that the product is non-renewable.

ï‚· Salesforce CPQ Reference:

SubscriptionType and SubscriptionTerm fields are detailed in the Subscription Products configuration guide ​.

ï‚· 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 ​.

ï‚· 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 ​

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:

Calculate the prorate multiplier when a subscription product’s End Date differs from the Quote’s End Date.

ï‚· Solution:

CPQ uses the Quote Line date (specific to the subscription product) to calculate the prorate multiplier. This ensures alignment with the subscription term.

ï‚· Why Other Options Are Incorrect:

A & D: Earliest or latest dates do not determine prorate multipliers.

B: The Quote date applies to the Quote as a whole, not individual subscription products.

ï‚· Salesforce CPQ Reference:

Prorate multiplier calculations are outlined in Subscription Management Guidelines ​.

The order of precedence for evaluating subscription dates is as follows

(1) Quote Line,

(2) Quote Line Group, and

(3) Quote

https://help.salesforce.com/s/articleView?id=000383503 &type=1

ï‚· Scenario Overview:

A Configuration Attribute displays a picklist with more values than the corresponding field on the Quote Line, which is restricted to a predefined set.

ï‚· Behavior:

When a user selects a value that is not in the Quote Line field’s restricted picklist, Salesforce CPQ prevents saving and displays an error.

ï‚· Validation:

The Quote Line enforces the picklist restriction, ensuring data integrity across the configuration and Quote Line Editor.

ï‚· Requirement:

Ensure the correct Distributor Discount is applied to Quote Lines based on the distributor's Discount_Level__c field value.

ï‚· Solution:

Configurator Scoped Price Rule:

A Price Condition checks whether the SBQQ__Quote__r.Distributor__c field is populated.

If the field is blank, the rule does not execute.

Price Action:

Injects the value of the Discount_Level__c field from the Distributor account into the Quote Line's SBQQ__DistributorDiscount__c field.

ï‚· Why Option A is Correct:

Configurator Scope ensures the rule is evaluated during configuration, applying discounts dynamically as the Quote is edited.

ï‚· Why Option B is Incorrect:

Calculator Scoped Price Rules execute during calculations (not configuration), which may result in delayed discount updates.

ï‚· Salesforce CPQ Reference:

Price Rules and their scopes are documented in the CPQ Pricing Logic Configuration ​.