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

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

ï‚· Requirement:

Universal Containers wants to control whether the Additional Discount column appears on the Quote Template.

ï‚· Solution:

By creating a custom checkbox field (Show_Discount__c), administrators can dynamically control the visibility of the Additional Discount column.

This checkbox is referenced in the Conditional Print Field of the Quote Template Line Column settings for the Additional Discount column.

ï‚· Mechanism:

When the Show_Discount__c checkbox is TRUE, the column appears.

When FALSE, it does not display.

ï‚· Salesforce CPQ Reference:

Conditional Print Field functionality in Quote Templates allows for dynamic content visibility based on field values ​.

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

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

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

Universal Containers wants to sell monthly subscriptions and round additional days up to the nearest month when calculating prorated prices.

ï‚· Solution Details:

Subscription Term Unit = Month: Ensures that subscriptions are billed on a monthly basis.

Subscription Prorate Precision = Month: Rounds up additional days to the next month.

ï‚· Steps to Configure:

Navigate to CPQ Package Settings > Subscription and Renewal Settings.

Set the Subscription Term Unit to Month.

Set the Subscription Prorate Precision to Month.

Save and test the configuration by creating a Quote with subscription products.

ï‚· Validation:

Ensure that additional days are rounded up to the next month in the prorated pricing calculation​​.

ï‚· Requirement Overview:

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

ï‚· Solution:

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

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

ï‚· Steps to Configure:

Navigate to the Product Record.

Set the Subscription Type to Renewable/Evergreen.

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

ï‚· Validation:

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

ï‚· Requirement Overview:

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.

Requirement:

Prevent users from reconfiguring a bundle after its initial configuration.

Solution:

Set Configuration Type to Allowed to permit configuration during initial setup.

Set Configuration Event to Add to allow configuration only when the product is added, blocking reconfiguration later.

Why Other Options Are Incorrect:

A: Disabled blocks all configuration, including initial setup.

B: Configuration Event = Always allows continuous reconfiguration.

D: Reconfigure Line Custom Action is unrelated to this requirement.

Salesforce CPQ Reference:

Configuration Type and Event settings are documented in Bundle Configuration ​.

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

ï‚· Requirement:

Migrate existing contracts to a new Product version upon renewal.

ï‚· Solution:

Update the Renewal Product field to specify the new version of the Product.

Enable the Renewal Forecast checkbox on the Contract to ensure renewal Quotes reference the new Product version.

ï‚· Why Other Options Are Incorrect:

B: Changing the Product Lookup on the Subscription directly bypasses standard renewal processes.

C: Selection Product Rules enforce configurations during quoting but are not suitable for renewals.

D: Price Rules do not modify Product references during renewal Quotes.

ï‚· Salesforce CPQ Reference:

Renewal product management is outlined in the CPQ Subscription and Renewal Guidelines ​.

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

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

Tiered pricing in Salesforce CPQ applies a cumulative price where each tier has a marginal rate (e.g., $9 per unit above 100). This matches the scenario: $1,000 for 0-100 units, then $9/unit for 101-500, $8/unit for 501-1,000, and $7/unit above 1,000, building on the prior tier’s total (e.g., $4,600 at 500). Option B (Tiered) supports this incremental pricing model. Option A (Block) uses fixed prices per range, not cumulative rates. Option C (Segmented) isn’t a standard CPQ pricing method. Option D (List) applies a flat unit price, ignoring tiers. Salesforce CPQ documentation defines Tiered pricing for this use case.

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:

Hide products with the Product Family "Software" when a Configuration Attribute is set to "Perpetual."

ï‚· Solution:

Use an Error Condition to evaluate the Product Family value on the Product Option record.

Configure a Product Action to Show all products except those with the Product Family "Software."

ï‚· Mechanism:

The Error Condition evaluates the Configuration Attribute's value against the Product Option.

The Product Action ensures visibility is dynamically controlled based on the evaluated condition.

ï‚· Salesforce CPQ Reference:

Error Conditions and Product Actions are key components of Product Rules in CPQ to implement dynamic product behavior ​.

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

Migrate new CPQ functionality from a sandbox, ensuring that record relationships are preserved.

ï‚· Migration Sequence:

Products: Base level of the bundle.

Options: Product Options depend on the Product.

Attributes: Attributes are referenced by Product Options.

Rules: Product Rules depend on Products, Options, and Attributes.

ï‚· Steps to Migrate:

Export and import Products first.

Migrate Options, followed by Attributes, and finally Rules.

ï‚· Validation:

Test the migrated functionality to ensure all dependencies and relationships are intact.

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

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

ï‚· Real-Time Calculation:

The Calculate Immediately field in CPQ ensures that pricing calculations occur automatically when changes are made in the Quote Line Editor without requiring manual saving.

ï‚· Field Behavior:

Enabling this field configures CPQ to detect changes to the Partner Discount or other relevant fields and trigger real-time recalculations.

ï‚· Salesforce CPQ Reference:

Configuration settings for real-time pricing calculations are documented in the Pricing and Calculation Package Settings .

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

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

ï‚· Requirement Overview:

Assign generated Approval requests to the user's direct manager.

ï‚· Solution:

Salesforce CPQ's Advanced Approvals package includes the setting Next Automated Approver Determined By, which allows Approvals to be routed automatically to the user's manager.

ï‚· Steps to Configure:

Navigate to the Approval Process.

Set Next Automated Approver Determined By to Manager.

Save and test the Approval process to ensure it correctly assigns to the manager.

ï‚· Requirement Overview:

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

ï‚· Solution Details:

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

America - USD: Prices for American customers.

Asia Pacific - USD: Prices for Asia Pacific customers.

Europe - EUR: Prices for European customers using EUR.

Europe - GBP: Prices for European customers using GBP.

ï‚· Steps to Configure:

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

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

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

ï‚· Validation:

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

ï‚· Requirement:

The Color of containers (a Configuration Attribute) must be displayed in the output document.

ï‚· Solution:

Create a Color field:

On Product Option: Captures the color selection during configuration.

On Quote Line: Ensures the selected color is carried forward to the quote document.

ï‚· Why Other Options are Incorrect:

B, D: These options do not account for both configuration and quote visibility requirements.

C: The Product object alone cannot store configuration-specific selections like color.

ï‚· Salesforce CPQ Reference:

Configuration Attributes and their linkage to Quote Lines are documented in CPQ guidelines ​.

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

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

ï‚· Requirement Overview:

Prevent bundles from being reconfigured in Renewal Quotes while allowing configuration during new or amendment Quotes.

ï‚· Solution:

Use a Custom Action Condition to control when the Reconfigure Line action is available.

Set the condition to exclude Renewal Quotes (SBQQ__Type__c != "Renewal").

ï‚· Steps to Configure:

Navigate to the Custom Action Condition related to the Reconfigure Line action.

Set the condition criteria to ensure the action is only available for non-Renewal Quotes.

ï‚· Validation:

Test by creating Renewal, New, and Amendment Quotes and verifying the Reconfigure Line action behaves as expected.

ï‚· Requirement:

Track individual serial numbers for each unit of Product A sold.

ï‚· Solution Details:

Asset Conversion Field determines how assets are created from Quote Lines.

Setting Asset Conversion to One Per Unit creates one Asset record for each unit sold, allowing tracking of individual serial numbers.

ï‚· Implementation:

Navigate to the Product Record for Product A.

Set Asset Conversion to One Per Unit.

ï‚· Justification:

This setup aligns with Salesforce CPQ's approach for granular tracking of Assets associated with product sales​​.

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

Understanding the Requirement:

Universal Containers needs Product Option A to be automatically included with Product B during the configuration.

Sales reps should not be able to remove Product Option A.

Salesforce CPQ Mechanism:

The Required field on a Product Option ensures that it is mandatory within a bundle and cannot be deselected by the user during configuration.

Field Behavior:

When the Required checkbox is selected for a Product Option:

The option is always included in the bundle configuration.

Users cannot remove or modify it unless additional automation (like a product rule) overrides this setting.

Configuration Steps:

Navigate to the Product Option A record associated with Product B in Salesforce CPQ.

Select the Required checkbox and save the changes.

Ensure that no conflicting product or price rules exist that could affect this behavior.

Field Alternatives and Clarifications:

Bundled: Sets the option as a part of the bundle, but this primarily affects pricing (sets price to zero) and doesn't enforce inclusion.

Quantity Editable: Allows control over whether users can adjust the quantity but does not prevent removal.

Selected: Preselects the option during configuration but still allows users to deselect it.

Verification and Testing:

Create a test configuration with Product B as the parent and verify that Product A is always included in the bundle.

Attempt to remove Product A to confirm that it is not possible.

ï‚· Bundle Configuration:

Small Storage Container (Option 1): $2.00 × 10 = $20.00

Shipping (Option 4): $7.50 (bundled).

Other Options (Option 2 and Option 3):

Medium Storage Container: Not selected.

Custom Box Label: Not selected.

ï‚· Calculation:

Bundle Parent Product Price: $5.00

Total Price: $5.00 (bundle) + $20.00 (Option 1) + $7.50 (Option 4) = $25.00

ï‚· Why Other Answers Are Incorrect:

A: Ignores bundled Option 4 price.

C: Includes non-selected options in the total.

D: Excludes all Option prices, which is inaccurate.

ï‚· Salesforce CPQ Reference:

Bundling logic and pricing are covered under Bundle Configuration Guidelines ​.

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

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:

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:

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

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

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

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

Warranty pricing should be based on the discounted prices of hardware products.

ï‚· Solution Details:

The Percent of Total Base field determines the pricing basis for Percent of Total Products.

To ensure the price reflects discounted values, set the Percent of Total Base to Net Price.

ï‚· Steps to Configure:

Navigate to the Warranty Product record.

Update the Percent of Total Base field to Net Price.

Save and test the configuration by adding hardware products and the Warranty to a Quote.

ï‚· Validation:

The Warranty price should now calculate as 10% of the discounted prices of hardware products​​.

ï‚· Requirement:

Ensure the Support SKU is available only in USD and EUR.

ï‚· Expected Behavior:

USD: The product is available and uses the Pricebook Entry's List Price.

EUR: The product is available and uses the Pricebook Entry's List Price.

GBP: The product is unavailable due to the absence of a Pricebook Entry in GBP.

ï‚· Why Other Options Are Incorrect:

A & D: These imply product unavailability in all currencies, which contradicts the configuration.

B: GBP would not add the product with a zero List Price due to Pricebook Entry restrictions.

ï‚· Salesforce CPQ Reference:

Multi-currency behavior and product availability are documented under CPQ Pricing and Product Management ​.

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

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

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

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

ï‚· Requirement:

Render separate Line Item sections for each Product Family and bundle on the output document.

ï‚· Solution Steps:

Option B: Create a Line Item section for each Product Family and use the Filter field to display only the relevant products for each section.

Option C: Use a formula field on the Quote Line object to identify the bundle's Name and Number, then set this field in the Group field to group lines within each section.

ï‚· Why Other Options Are Incorrect:

A: The Conditional Print field is not used for rendering specific Product Families in Line Item sections.

D: Sort Order on Product records does not meet the grouping and filtering requirements for the output document.

ï‚· Salesforce CPQ Reference:

Document generation and Line Item grouping are detailed in Quote Templates Configuration ​.

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

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

To display Maintenance and Support products in separate sections, the admin must create Product Features, as features define sections in the CPQ configurator. To control the order (Support above Maintenance), the "Number" field on the Product Feature determines the sequence, with lower values appearing first. Option B correctly specifies two features (Maintenance and Support) and assigns a lower Number to the Support Feature, ensuring it displays above Maintenance. Option A relies on alphabetical ordering, which doesn’t guarantee Support above Maintenance (e.g., "M" precedes "S"). Options C and D use Product Options, which don’t create sections—only features do—and thus fail the separate-sections requirement. Salesforce CPQ documentation confirms feature ordering via the Number field.

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

ï‚· Requirement Overview:

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

ï‚· Solutions:

C. Validation Rule:

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

D. Product Rule:

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

ï‚· Steps to Configure:

Validation Rule:

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

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

Product Rule:

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

ï‚· Validation:

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

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

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.

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

ï‚· Advanced Approvals Context:

The Opportunity Object is configured out-of-the-box to integrate fully with Advanced Approvals.

Other objects, like the CPQ Quote or Quote Line, may require additional customization.

ï‚· Functionality:

Advanced Approvals use Approval Rules, Chains, and Conditions to automate the approval process.

Predefined templates and configurations are readily available for the Opportunity Object.

ï‚· Validation:

After installation of the Advanced Approvals package, confirm the Opportunity Object's configuration. No additional setup is required for basic functionality​​.

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

A group of users should receive Approval requests simultaneously, and only one user's response is required to approve.

ï‚· Key Configuration:

Use a Group ID to associate the group of approvers.

Setting Unanimous = False ensures that only one approval is needed to proceed.

ï‚· Steps to Configure:

Navigate to the Approver Record related to the Approval Rule.

Reference the appropriate Group ID.

Set the Unanimous checkbox to False.

ï‚· Validation:

Test the Approval process by submitting a Quote for approval and confirming that one approval suffices.

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

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

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