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

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

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

 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

 Issue Context:

Not all Quote Lines are generating Opportunity Product records during the Amendment process.

 Possible Causes:

A. Net Total = 0:

Salesforce CPQ does not create Opportunity Products for Quote Lines with a Net Total of zero.

D. Exclude from Opportunity:

If the Product has the Exclude from Opportunity checkbox set to TRUE, it prevents Opportunity Product creation.

 Steps to Investigate:

Verify the Net Total of the Quote Lines.

Check the Product configuration for the Exclude from Opportunity setting.

 Validation:

Update the relevant fields and test the Amendment process to ensure all eligible Quote Lines generate Opportunity Products.

 Requirement Overview:

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

 Solution Details:

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

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

 Steps to Configure:

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

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

 Requirement Overview:

Universal Containers wants 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 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.

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:

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:

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.

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

 Considerations for Authorizing Calculation Service:

The Calculation Service must be authorized by a user who has sufficient privileges and stable permissions.

 Solution Steps:

Option B: Use a non-human admin user (e.g., an integration user) to authorize the Calculation Service. This ensures consistent access and avoids disruptions due to personnel changes.

Option C: Place the user at the top of the Role Hierarchy to ensure full visibility and access across relevant objects.

 Salesforce CPQ Reference:

Proper user configuration for the Calculation Service is outlined in the CPQ Authorization 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:

Universal Containers wants to aggregate the quantities of all Product Options in Feature A to determine the Discount Tier.

 Key Configuration:

Assign the Discount Schedule to the Product Feature itself.

Enable the Cross Orders checkbox to aggregate quantities across multiple orders or contracts.

 Steps to Configure:

Navigate to the Product Feature record for Feature A.

Set the Discount Schedule field to the appropriate Discount Schedule.

On the Discount Schedule, check the Cross Orders box.

 Validation:

Add multiple Product Options from Feature A to a Quote and verify that their quantities are aggregated for discount calculation.

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

 Requirement:

A unique license number needs to be stored on the Asset record for each unit of a downloadable product sold.

 Solution:

Setting the Asset Conversion field to One per Unit ensures that an individual Asset record is created for each unit of the product. This allows each Asset to store a unique license number.

 Why Other Options Are Incorrect:

A & B: Null or custom values do not enforce one Asset per unit, making it impossible to assign unique license numbers.

D: One per Quote Line creates only one Asset for the entire Quote Line, which is not suitable for unit-level licensing.

 Salesforce CPQ Reference:

The behavior of Asset Conversion is detailed in CPQ Asset Configuration documentation ​.

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

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

Business Requirement Context:

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

Each Order generated will correspond to a unique Start Date.

Key Salesforce CPQ Features:

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

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

Step-by-Step Configuration:

Navigate to the Quote in Salesforce CPQ.

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

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

Expected Outcome:

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

Validation and Testing:

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

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

References:

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

 Issue:

Contract creation fails when the Contracted checkbox is checked on an Opportunity.

 Possible Causes:

A: If the Subscription Conversion Behavior is set to None, the product is not converted into a Subscription, preventing the Contract from being created.

B: The Opportunity requires a Primary Quote to generate a Contract, as the Contract details are derived from the Quote.

 Why Other Options Are Incorrect:

C: If the Subscription Pricing field is blank, the product is treated as non-subscription but does not prevent Contract creation.

D: Products with Subscription Pricing = One-time are not converted to Subscriptions, but they do not block Contract creation.

 Salesforce CPQ Reference:

Contract creation requirements and behaviors are documented under CPQ Subscription Management Guidelines ​.

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

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

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

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

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

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

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

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

 Scenario Overview:

The Custom value for the Condition Met field allows for complex logical operations using a mix of AND/OR across multiple Price Conditions.

 Use Case:

When a Price Rule has three or more conditions and requires specific combinations of AND and OR logic, the Custom option is required.

 Implementation:

Navigate to the Price Rule.

Set Condition Met to Custom.

Specify the logic (e.g., (Condition 1 AND Condition 2) OR Condition 3).

 Validation:This ensures Salesforce CPQ evaluates the Price Rule as intended, supporting mixed logical conditions.

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 .

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

 Requirement:

Certain products should only be available as part of a bundle, not sold separately.

 Solution:

Setting the Component checkbox to TRUE on the Product ensures it is only available as a component within a bundle.

 Why Other Options are Incorrect:

A: Removing Price Book Entries restricts pricing but does not limit availability.

B: Configuration Event field is unrelated to this functionality.

D: Product Rules are not required for this basic configuration.

 Salesforce CPQ Reference:

The Component checkbox functionality is documented under Product Configuration in CPQ ​.

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

Limit users from selecting more than 10 product options within a specific Product Feature.

 Key Mechanism:

The Max Options field on the Feature record limits the maximum number of product options that can be selected for that feature.

 Steps to Configure:

Navigate to the Feature Record associated with the Product Bundle.

Set the Max Options field to 10.

Save and test by adding the Product Bundle to a Quote.

 Validation:

When a user attempts to select more than 10 product options within the feature, Salesforce CPQ will prevent further selections and display an appropriate message.

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:

When a fixed bundle is selected, users should bypass the configuration process entirely.

 Solution:

Setting the Configuration Type to Allowed ensures users can configure the bundle if necessary.

Setting the Configuration Event to Always skips the configuration process automatically for preconfigured bundles.

 Why Other Options Are Incorrect:

A: Setting Configuration Type to Disabled prevents any configuration, which may not align with future flexibility requirements.

B: Required forces configuration instead of skipping it.

D: Configuration Event = Add requires the user to manually trigger the process during addition.

 Salesforce CPQ Reference:

Bundle Configuration Settings and their implications are detailed in CPQ Configuration Guidelines ​.

 Requirement Overview:

Display the sum of a custom field in the standard Line Editor table without replacing the subtotal or total fields.

 Solution Details:

The Summary Fields field set on the Quote Line object controls which fields appear as totals in the Line Editor.

 Steps to Configure:

Navigate to Setup > Object Manager > Quote Line.

Locate the Summary Fields Field Set.

Add the custom field to the field set.

 Validation:

Open the Quote Line Editor and confirm that the sum of the custom field appears in the standard table, alongside other totals.

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

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:

Calculate the pricing steps for a subscription product with a 24-month term.

 Calculation Details:

Regular Unit Price:

Default Subscription Term = 12 months.

Adjusted for 24 months: $120 × 24 / 12 = $216.00.

Customer Unit Price:

Apply 10% Volume Discount: $216.00 × (1 − 0.10) = $194.40.

Apply 20% Additional Discount: $194.40 × (1 − 0.20) = $172.80.

Net Unit Price:

Apply 5% Partner Discount: $172.80 × (1 − 0.05) = $164.16.

 Validation:

Verify each step in the Salesforce CPQ price waterfall to ensure accuracy.

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

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

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:

Allow users to choose options and define quantities during bundle configuration.

 Configuration Types:

None (A): Users can freely choose options and set quantities.

Allowed (C): Users can choose options and optionally set quantities.

Required (E): Users must configure the options and define quantities.

 Why Other Options Are Incorrect:

B: Configurable is not a valid value for the Configuration Type field.

D: Disabled prevents any configuration, which contradicts the requirement.

 Salesforce CPQ Reference:

Configuration Types are documented under Bundle Configuration Guidelines ​.

 Requirement Overview:

Reduce scrolling in the configurator for a bundle with many Features and Options.

 Solutions:

A. Option Selection Method = Add: Allows users to select options from a pop-up window instead of scrolling through the configurator.

D. Group Features into Tabs: Use the Category field to group Features into tabs for easier navigation.

E. Option Layout = Tabs: Configure the bundle to display Options in a tabular format, reducing scrolling.

 Steps to Configure:

Set the Option Selection Method to Add on relevant Product Features.

Populate the Category field on Product Features to group them into tabs.

Change the Option Layout on the bundle Product to Tabs.

 Validation:

Test the configurator to ensure the layout reduces scrolling and improves usability.

 Requirement Overview:

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

 Solution:

Configure the Discount Schedule to:

Set the Discount Unit to Amount.

Choose All from the Override Behavior picklist.

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

 Steps to Configure:

Navigate to the Discount Schedule Record.

Set the Discount Unit to Amount.

Select All from the Override Behavior picklist.

Check the Use Price for Amount box.

 Validation:

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

 Requirement Overview:

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:

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

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

 Issue Context:

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

 Root Cause:

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

 Solution Steps:

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

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

 Validation:

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

 Salesforce CPQ Documentation Reference:

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

 Requirement:

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

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:

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:

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:

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.

 Requirement:

Clients can negotiate a discount for Product A until a specified date before contract activation.

 Relevant Fields on the Contracted Price Record:

Product: Identifies Product A as the subject of the negotiated price.

Expiration Date: Specifies the end of the discount eligibility period.

Discount: Sets the agreed discount percentage for the negotiated price.

 Salesforce CPQ Reference:

Contracted Price Record management is key to implementing client-specific pricing strategies ​.

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

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