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

 Requirement:

Ensure that custom field data from original Quote Lines flows into Renewal Quote Lines.

 Solution:

Use twin fields on the Asset and Subscription objects to store and transfer data. Twin fields are automatically mapped during renewal processes, ensuring data flows seamlessly.

 Why Other Options Are Incorrect:

A: A formula field cannot persist data on Renewal Quotes.

B: Automatic mapping does not apply to custom fields without twin fields.

C: A Price Rule is unnecessary when twin fields handle this data flow.

 Salesforce CPQ Reference:

Twin fields and their functionality are described in CPQ Subscription Management ​.

 Requirement:

Apply different uplift rates to Product Families X and Y upon renewal.

 Solution Steps:

Option A: Set the Renewal Uplift Rate on each Subscription record for Product Families X and Y.

Option C: Configure the Account’s Renewal Pricing Method as "Uplift" to enable uplift calculations during renewal.

 Why Other Options Are Incorrect:

B and D: These options fail to apply the correct rates at the Subscription or Product Family level.

 Salesforce CPQ Reference:

Uplift rates and Renewal Pricing methods are outlined in CPQ Renewal Configuration Guidelines ​.

UESTION NO: 83

Users at Universal Containers want to know how Approval requests will be routed prior to submitting a Quote for approval.

How can the admin meet this requirement?

A. Using Native Approvals, build a custom Visualforce Page to display the Approval Process for the Quote.

B. Using Advanced Approvals, place the Preview Approval button on the Quote page layout.

C. Using Advanced Approvals, build a custom Visualforce Page to display the Approval Chains for the Quote.

D. Using Native Approvals, build a custom button to display the approval matrix to users.

Answer: B

 Requirement:

Sales reps need visibility into the Approval Chain before submitting a Quote for approval.

 Solution:

The Preview Approval button in Advanced Approvals allows users to view the Approval Chain directly from the Quote page.

 Why Other Options Are Incorrect:

A and C: Building custom Visualforce pages is unnecessary with Advanced Approvals.

D: Native Approvals do not offer a built-in preview feature.

 Salesforce CPQ Reference:

Advanced Approvals functionality, including the Preview Approval button, is detailed in CPQ Approval Configuration ​.

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

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 .

 Scenario:

Multiple Approval Chains appear in Advanced Approvals, and the order of completion depends on the Final Approval Step value.

 Behavior:

Advanced Approvals prioritizes chains based on their Final Approval Step value, processing the chain with the lowest value first.

 Why Other Options Are Incorrect:

A: Approval Chains are not completed independently but follow the step order.

B: The display order on the screen does not determine completion order.

C: Lowest Approval Step applies to individual steps, not the entire chain.

 Salesforce CPQ Reference:

Approval Chains and step prioritization are detailed in Advanced Approvals Configuration ​.

 Requirement Overview:

Ensure that the Contract Name field is visible to users when initiating an Amendment.

 Key Configuration:

The Active Contract Lookup Field Set on the Contract object determines which fields appear when selecting a Contract for an Amendment.

 Steps to Configure:

Navigate to the Field Set named Active Contract Lookup on the Contract Object.

Add the custom Contract Name field to the Field Set.

 Validation:

Test the Amendment process to confirm that the Contract Name field is visible.

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

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:

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

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

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

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

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

Ensure a Product Rule fires only within a specific bundle.

 Solution:

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

 Why Other Options Are Incorrect:

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

 Salesforce CPQ Reference:

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

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

 Dynamic Features:

A Dynamic Feature allows administrators to automatically update or populate Product Options for a bundle based on defined rules and conditions.

 Filter Product Rules:

Applying a Filter Product Rule ensures that only relevant or newly available products appear as options for the bundle. This reduces manual maintenance while keeping the bundle dynamic.

 Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are part of advanced bundling techniques documented under Product Configuration ​.

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

 Requirement Overview:

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

 Solution:

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

 Steps to Configure:

Navigate to the Premier Support Product record.

Populate the Renewal Product field with Premier Pro.

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

 Validation:

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

 Requirement:

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

 Issue:

Sales reps experience excessive horizontal scrolling to access the Clone and Delete actions in the Quote Line Editor.

 Solution:

Quote Line Editor Drawers provide a compact and user-friendly way to access actions without excessive scrolling.

 Steps to Configure:

Navigate to Setup > Custom Actions.

Configure the Clone and Delete actions to appear in the Quote Line Editor drawers.

 Validation:

Open the Quote Line Editor and confirm that the actions are accessible without horizontal scrolling.

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

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.

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

 Scenario:

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

 Solution:

Use a Discount Schedule with:

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

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

 Why Other Options are Incorrect:

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

C: Range type does not handle tiered pricing accurately.

 Salesforce CPQ Reference:

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

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

Prevent users from selecting both Product C and Product D in a bundle configuration.

 Solution:

Using an Option Constraint with Type = Exclusion ensures that selecting one product automatically excludes the other.

 Why Other Options Are Incorrect:

A: Dependency constraints ensure one product depends on another, which is the opposite of the requirement.

B & D: Setting Min Options and Max Options in a Product Feature does not enforce mutual exclusivity.

 Salesforce CPQ Reference:

Option Constraints and their configuration are detailed in CPQ Bundling Guidelines ​.

 Scenario:

Product A has a 36-month Subscription Term with a List Price of $36,000.

Product B has a 1-month Subscription Term with a List Price of $2,000.

Quote Subscription Term is 18 months.

 Calculation:

Product A Prorate Multiplier = 18 / 36 = 0.5.

Net Total = $36,000 × 15 × 0.5 = $270,000.

Product B Prorate Multiplier = 18 / 1 = 18.

Net Total = $2,000 × 15 × 18 = $36,000.

 Why Other Options Are Incorrect:

A: The Net Total for Product B is incorrectly inflated.

C: The Prorate Multiplier for Product B should reflect the Quote Term-to-Subscription Term ratio, not default to 1.

 Salesforce CPQ Reference:

Prorated pricing and multiplier calculations are explained in Subscription Pricing Guidelines ​.

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

Step 1: Create a Monthly Price Line Column

Navigate to Quote Templates in Salesforce CPQ.

Select the relevant Quote Template.

In the Line Columns related list:

Create a new Line Column for "Monthly Price."

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

Step 2: Create a Custom Formula Field

Navigate to Setup > Object Manager > Quote.

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

Type: Formula (Checkbox).

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

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

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

Step 3: Configure Conditional Print Field on the Line Column

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

Set the Conditional Print Field to Show_Monthly_Price.

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

Step 4: Validate in Quote Document

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

The Monthly Price column should appear in the PDF.

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

The Monthly Price column should not appear.

Step 5: Optional Enhancements

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

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

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

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

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:

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

 Solution:

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

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

 Why Other Options Are Incorrect:

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

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

 Salesforce CPQ Reference:

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

 Requirement Overview:

Universal Containers wants to update the Quantity of a specific Product in the Quote Line Editor via a Price Rule.

The Price Rule should target only this specific Product.

 Key Mechanism:

Use a Price Condition on the Price Rule to evaluate a Quote Line field that uniquely identifies the Product (e.g., Product Code or Product Name).

 Steps to Configure:

Navigate to the Price Rule.

Add a Price Condition:

Field: Select a field from the Quote Line that identifies the Product.

Operator: Equals.

Value: Enter the unique value (e.g., Product Code or Name).

Configure the Price Action to update the Quantity field.

 Validation:

Test the rule by adding the specific Product to a Quote and confirming that the rule updates its Quantity as expected.

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

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:

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.

 Scenario Breakdown:

Product A has a base list price of $100.

A quantity of 15 is entered on the quote.

Gold Hardware Maintenance Discount applies because contracted pricing is enabled.

Discount for the quantity range (11–20) is 15% (as shown in the table).

 Net Price Calculation:

List Price = $100

Discount = 15%

Quantity = 15

Net Total Price = $100 × 15 × (1 - 0.15) = $1,275.

 Justification for Selected Discount:According to Salesforce CPQ guidelines, when contracted pricing applies, it takes precedence over other Discount Schedules. The Gold Discount Schedule is therefore applied.

 Testing and Validation:Test the configuration using a sample quote to ensure the correct schedule is applied and the net total price matches the expected value.

 Requirement Overview:

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

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

 Key Configurations:

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

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

 Steps to Configure:

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

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

 Validation:

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

When a user performs a contract renewal and finds that the Price Book on the Renewal Opportunity or Quote is incorrect, the issue often arises due to the absence of a Price Book reference on the original Contract. To address this, the Renewal Pricebook ID field on the Contract must be populated. This field ensures the correct Price Book is carried over during the renewal process.

Step 1: Understand the Renewal Pricebook ID Field

Field Location: The SBQQ__RenewalPricebookId__c field is on the Contract object.

Purpose: It specifies which Price Book Salesforce CPQ should use for renewal quotes and opportunities created from the contract.

Without this field populated, Salesforce CPQ defaults to another Price Book, which can lead to inaccuracieste the Renewal Pricebook ID**

Access the Contract Record:

Navigate to the relevant Contract record in Salesforce.

Edit the Contract:

Populate the Renewal Pricebook ID field with the 18-digit Salesforce ID of the desired Price Book.

This ID corresponds to the Price Book you want Salesforce CPQ to apply during renewals.

Save the Changes:

Ensure the field is correctly updated and the changes are saved .

Step 3: **

Attempt the renewal process again by clicking Renew on the Contract.

Confirm that the Renewal Opportunity and associated Quote now reference the correct Price Book.

Step 4: Consider Automation for Future Accuracy

Automate Field Population:Use Process Builder or a Flow to automatically populate the Renewal Pricebook ID field based on the contract's associated Account or Opportunity. This reduces manual errors and ensures consistency.

Data Validation:Enforce validation rules to prevent contracts from being saved without a valid Renewal Pricebook ID .

By ensuring the Renewal Pricebook ID is coesolve the issue of incorrect Price Books during renewals and prevent similar occurrences in the future.

 Scenario:

A Price Rule utilizes a Lookup Object and Lookup Queries, and multiple records meet the criteria for a single Quote Line.

 Behavior:

When more than one lookup record meets the criteria, Salesforce CPQ does not apply any value to the Target Field. Instead:

The Target Field retains its original value.

An error message is displayed in the Quote Line Editor, notifying the user of the conflict.

 Why Other Options Are Incorrect:

A & D: Salesforce CPQ does not resolve ties by sorting records alphabetically.

C: The system does not apply values based on record creation date.

 Salesforce CPQ Reference:

Lookup Queries behavior and error-handling are outlined in CPQ Price Rules Configuration Guidelines ​.

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

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

 Issue Context:

Some Opportunity Products are not syncing from the Quote, causing pipeline inaccuracies.

 Troubleshooting Steps:

A. Ensure the Quote’s Account lookup is populated:

A missing Account lookup can prevent synchronization as it ties the Quote to the Opportunity.

B. Ensure the Opportunity’s Primary Quote lookup is populated:

The Primary Quote must be explicitly linked to the Opportunity for synchronization to occur.

E. Check the Quote’s Primary checkbox for a value of True:

Only the Primary Quote syncs Opportunity Products. Ensure the checkbox is set to True.

 Validation:

Verify that Opportunity Products sync correctly after ensuring these fields are properly populated.

 Requirement Overview:

Prevent the user from selecting Product B unless Product A is also selected in the bundle.

 Key Configurations:

Type = Dependency: Ensures that one Product is dependent on the selection of another.

Active = True: Activates the Option Constraint for use in the configurator.

 Steps to Configure:

Navigate to the Option Constraint record.

Set the Type to Dependency.

Mark the Active checkbox as True.

Define Constrained Option (Product B) and Constraining Option (Product A).

 Validation:

Add the bundle to a Quote and confirm that selecting Product B is only possible when Product A is also selected.

 Requirement Overview:

Universal Containers wants to hide lid Products from the Product Selection screen since they are only sold as part of a container Product.

 Solution:

By selecting the Hidden checkbox on the lid Product record, the Product is removed from the Product Selection page while remaining available within bundles.

 Steps to Configure:

Navigate to the Product Record for each lid Product.

Select the Hidden checkbox.

Save the changes.

 Validation:

Verify that the lid Products no longer appear on the Product Selection screen but remain accessible as part of their parent container bundles.

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

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

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

 Scenario Breakdown:

List Price = $100.00 per unit.

Quantity = 21 units.

Discount Schedule:

First Level (1–11 units): 10% discount.

Second Level (11–21 units): 25% discount.

Third Level (21+ units): 50% discount.

 Slab Discount Calculation:

First Level (1–11 units):

Price = $100 × 10 = $1,000

Discount = 10% = $1,000 × 0.10 = $100

Net = $1,000 - $100 = $900

Second Level (11–21 units):

Price = $100 × 10 = $1,000

Discount = 25% = $1,000 × 0.25 = $250

Net = $1,000 - $250 = $750

Total Net = $900 + $750 = $1,700

 Validation:This matches Salesforce CPQ's standard behavior for Slab Discount Schedules, where discounts are applied per tier.

 Subscription Product Configuration:

Product B uses the Percent of Total pricing model based on Product A's Net Price.

Product B's Percent of Total Base is set to "Net," and its Percent of Total Target is set to Product A.

Product B's Percent of Total (%) is configured as 10%.

 Calculation:

Product A Net Total = $2,400

Product B Net Total = 10% of Product A Net Total = 2,400×0.1=2402,400 \times 0.1 = 2402,400×0.1=240.

 Salesforce CPQ Reference:

Percent of Total pricing logic is described under Percent of Total Products ​.

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

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:

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

A customer requires specific pricing for their account.

 Solution:

B. Contracted Price Record:

Directly create a Contracted Price record related to the customer’s Account.

D. Contracted Checkbox:

Select the Contracted checkbox on the Quote record to generate a Contracted Price automatically when the Quote is finalized.

 Steps to Configure:

Option B:

Navigate to the Account and create a Contracted Price record for the specific Product and pricing.

Option D:

On the Quote, select the Contracted checkbox and ensure the Quote is synced to generate the Contracted Price.

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

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

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

 Requirement:

Allow customers to return asset Products and receive credit.

 Solution:

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

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

 Why Other Options Are Incorrect:

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

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

 Salesforce CPQ Reference:

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

 Requirement:

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 .