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

 Scenario Overview:

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

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

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

 Price Calculation:

List Unit Price remains the standard price of $150.

Regular Unit Price applies the contracted price of $100.

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

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

 Salesforce CPQ Reference:

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

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

 Solution Mechanics:

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

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

 Steps to Implement:

Create a new Process Builder.

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

Define criteria to determine the dynamic value.

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

 Advantages of Process Builder:

Allows for dynamic and conditional logic.

Automates the default value population without user intervention.

 Testing and Validation:

Create a test bundle with the Configuration Attribute.

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

 Requirement Overview:

When Product A is selected, Product B should be automatically selected within the bundle.

The admin created a Product Rule, but it fails to trigger immediately.

 Key Mechanism:

The Apply Immediately checkbox ensures that the Product Rule executes as soon as the parent Product (Product A) is selected. Without this, the rule may not fire until additional actions (e.g., clicking Calculate) occur.

 Steps to Resolve:

Navigate to the Product Option record for Product A.

Set the Apply Immediately field to True.

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

 Justification:

"Apply Immediately" is required for Product Rules to trigger instant actions, ensuring dependencies like auto-selection are respected without delay​​.

 Requirement:

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

 Solution:

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

 Mechanism:

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

 Salesforce CPQ Reference:

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

 Requirement Overview:

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.

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

Contracts are not being generated for activated Orders containing subscription-based products.

 Why Debug Logs?

Debug Logs capture real-time system activity, including Apex triggers and CPQ package processes.

They provide detailed error messages and can identify issues such as missing triggers, misconfigured objects, or dependency errors.

 Steps to Investigate:

Enable Debug Logs in Salesforce Setup for the affected user or system process.

Perform the action that generates the error (e.g., activating the Order).

Review the logs for errors related to Contract generation.

Requirement:

Implement a price change for Product A when its quantity exceeds 10.

Solution:

Price Conditions:

Verify that the product is Product A.

Check that the quantity of Product A exceeds 10 using a Summary Variable.

Price Action:

Inject the value $50 into the Unit Price field for Product A.

Why Other Options Are Incorrect:

B, C, D: These options involve unnecessary actions, such as injecting values into the Quantity field, which is unrelated to the requirement.

Salesforce CPQ Reference:

Configuring Price Rules with Conditions and Actions for specific scenarios ​.

 Requirement:

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

 Solution:

Summary Variable:

Sum the Quantity field on Asset records for Product A.

Price Condition:

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

 Why Other Options are Incorrect:

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

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

 Salesforce CPQ Reference:

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

 Requirement:

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

 Solution Steps:

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

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

 Why Other Options Are Incorrect:

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

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

 Salesforce CPQ Reference:

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

 Root Cause:

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

 Steps to Resolve:

Navigate to Setup > Object Manager > Quote.

Locate the Calculating Fields field set.

Add the Primary field to the field set.

 Testing:

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

 Salesforce CPQ Reference:

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

 Requirement Overview:

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

 Solution Details:

B. Summary Variable:

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

Configure the Max aggregation function to evaluate discounts.

C. Price Condition:

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

 Steps to Configure:

Summary Variable:

Navigate to Summary Variables and create one with:

Target Object: Quote Line.

Aggregate Function: Max.

Aggregate Field: SBQQ__Discount__c.

Price Condition:

Add a condition to the Price Rule:

Object: Quote Line.

Field: SBQQ__Discount__c.

Operator: Greater Than.

Filter Value: 0.

 Validation:

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

Scenario Breakdown:

List Price = $100

Quantity = 5

Discount Schedule Type = Slab

Discount Unit = Percent

Slab Discount Mechanism:

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

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

Calculation:

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

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

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

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

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

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

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

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

 Solution Steps:

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

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

 Why Other Options Are Incorrect:

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

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

 Salesforce CPQ Reference:

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

Requirement:

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:

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

To manage a subset of eco-friendly products for opportunities flagged as eco-friendly while allowing flexibility to include all bundles, follow these steps:

Step 1: Create a Filter Product Rule

Filter Product Rules help define dynamic filtering of products displayed during the quoting process.

Navigate to Product Rules

Go to Salesforce Setup → Product Rules and click New.

Set the Type to Filter and define a clear Name such as "Eco-Friendly Product Filter."

Configure the Filter Logic

Define the conditions to identify eco-friendly and bundle products.

Use the Conditions related list to target the relevant product fields (e.g., a custom checkbox for eco-friendly products and a type field for bundles).

Example condition:

Field = Eco-Friendly Checkbox

Operator = Equals

Value = True

Step 2: Set up the Product Action

Product Actions define what the rule does when triggered.

Add a Product Action

In the Product Rule, go to the Product Actions related list and click New.

Set the Type to Optional Filter. This allows the system to apply the filter by default but enables users to remove the filter and see all bundles.

Link to Add Products Button

Make sure this action links to the Add Products custom action.

Step 3: Ensure Opportunity Integration

The Opportunity flagged as eco-friendly must drive this behavior.

Custom Field Dependency

Ensure the Opportunity has a field (e.g., Eco-Friendly Checkbox) that can be referenced in the Filter Product Rule or through a related custom formula on the Quote.

Dynamic Behavior

When the Opportunity is flagged, the filter is applied dynamically, displaying only eco-friendly and bundle products in the Add Products dialog.

Step 4: Test and Validate

Test the behavior by flagging different Opportunities as eco-friendly and verifying the Add Products functionality:

Eco-Friendly flag → Default to eco-friendly products and bundles.

No flag → All products, including non-eco-friendly bundles, are shown.

Additional Considerations:

Search Filter IntegrationThe Search Filter can complement this approach by providing additional options for users to refine their selections further​​.

User TrainingTrain sales reps on how to toggle the filter manually if needed.

This setup allows Universal Containers to meet its business objectives while maintaining flexibility for its sales team​.

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

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

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

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

Localize Quote Terms into three selectable languages for the quote PDF output.

Solution Steps:

Step A: Create a picklist field (e.g., Output Language) on the Quote object with language codes (e.g., EN, FR, DE) as values.

Step B: Create Localization records for each Quote Term in all three languages, ensuring the Quote PDF reflects the selected language.

Why Other Options Are Incorrect:

C: "Allow Output in Different Languages" is not an actual managed package setting.

D: Setting the Language field alone does not dynamically manage multiple languages for PDF generation.

Salesforce CPQ Reference:

Localization of Quote Terms is covered in CPQ Multi-Language Configuration Guidelines ​.

 Requirement Overview:

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

 Solution:

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

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

 Steps to Configure:

Create a bundle for each subset of products.

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

 Validation:

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

 Issue Context:

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

 Root Cause:

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

 Solution Steps:

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

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

 Validation:

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

 Salesforce CPQ Documentation Reference:

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

 Requirement Overview:Universal Containers needs the quantity of product options in a bundle to automatically scale based on the quantity of the parent bundle product.

 Salesforce CPQ Mechanism:

The Type field on the Product Option allows for specific configuration behaviors.

When the Type is set to Component, Salesforce CPQ automatically multiplies the option's quantity by the bundle product's quantity. This ensures that the dependent options align with the parent bundle quantity.

 Implementation Steps:

Navigate to the Product Option record associated with the bundle.

Set the Type field to Component.

Ensure that other configuration settings, such as quantity constraints, align with the desired outcome.

Test the functionality by adding the bundle to a quote and adjusting the quantity. The option quantities should scale proportionally.

 Relevant Salesforce CPQ Documentation:This behavior is a standard feature in Salesforce CPQ and is documented under Product Bundles and Options Configuration.

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

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

 Potential Causes:

Component Checkbox: Products marked as Components are typically excluded from being directly selectable in the Product Selection screen unless part of a bundle .

Search Filter: Custom Search Filters on the Add Products button limit the display of products based on criteria such as product attributes or field values.

 Excluded Reasons:

Hidden Checkbox: This is generally used to hide products from the Quote Line Editor, not the Product Selection screen.

Custom Action Condition: While these can limit the Add Products button's visibility, they do not directly affect individual product visibility.

 Salesforce CPQ Reference Points:

Documentation on Product Selection Behavior and Search Filters confirms these behaviors ​.

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

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

 Solution:

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

 Why Other Options Are Incorrect:

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

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

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

 Salesforce CPQ Reference:

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

 Requirement Overview:

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

 Key Configuration:

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

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

 Steps to Configure:

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

Set Percent of Total Scope to Components.

 Validation:

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

 Requirement:

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

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

 Dynamic SKU Generation:

A dynamic SKU is created based on user choices during the configuration process. This requires fields that define patterns and positions for combining components into a single SKU.

 Required Fields:

Component Code Position: Determines the position of each component in the SKU.

Component Code: Represents individual product codes that contribute to the SKU.

Configured Code Pattern: Defines the overall pattern of the dynamically generated SKU.

 Salesforce CPQ Reference:

Dynamic SKU creation is described under Configuration and Product Bundling 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:

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.

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

 Subscription Term and List Price:

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

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

 Proration and Ranged Discount Schedule:

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

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

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

 Regular Price Calculation:

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

 Key Salesforce CPQ Reference Points:

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

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

 Requirement Overview:

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.

 Issue Analysis:

Products not syncing to Opportunity Products is usually caused by specific CPQ conditions or rules.

 Reasons for Failure:

B: Products with an Effective Quantity of zero are excluded from syncing.

C: Validation Rules on the Opportunity Product object may silently block the sync process if they are not met.

D: Products with a price of zero do not sync by default.

 Why Other Options Are Incorrect:

A: Missing Price Book Entries prevent quoting entirely, not syncing issues.

E: The Exclude from Opportunity checkbox applies to the Product Option, not the syncing process.

 Salesforce CPQ Reference:

CPQ guidelines for syncing Quote Lines to Opportunity Products ​.

 Requirement Overview:

Control the visibility of fields in the Quote Line Editor.

 Solution:

The Edit Lines Field Set Name special field on the Quote object references the field set used to control which Quote Line fields are visible in the editor.

 Steps to Configure:

Navigate to the Field Set on the Quote Line object.

Add or remove fields from the field set referenced in the Edit Lines Field Set Name field.

 Validation:

Test the Quote Line Editor to ensure only the configured fields are visible.

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

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

 Data Import Order for Quote Templates:

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

Quote Template: Base structure for the quote document.

Template Sections: Define sections of the quote.

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

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

Quote Terms: Define legal or contractual terms.

Term Conditions: Conditions related to the terms.

 Salesforce CPQ Reference:

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

 Requirement:

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

 Solution:

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

 Why Other Options Are Incorrect:

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

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

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

 Salesforce CPQ Reference:

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

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

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

 Requirement Overview:

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

 Solution:

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

 Steps to Configure:

Navigate to the Product Record for the item.

Select the Component checkbox.

Save the changes.

 Validation:

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

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