Sales-Admn-202 Salesforce Certified CPQ Administrator Question and Answers

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

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.

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

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.

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

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

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

For the Fulfillment team’s requirement, Order Item dates need to reflect the order creation date rather than Quote Line start dates. Option C achieves this by using Process Builder to set the Order Product Date to "Today" upon record creation, overriding any inherited Quote Line dates. For the Account Management team’s requirement, all items from one order must appear on a single contract. Option A accomplishes this by setting the Contracting Method on the Order to "Single Contract," ensuring all order products are grouped under one contract regardless of subscription terms. Option B (Default Order Start Date) is a package-level setting that doesn’t directly apply to individual order items. Option D (Quote Contracting Method) affects quote-to-contract mapping but doesn’t ensure order-based consolidation. Salesforce CPQ documentation supports these configurations for date and contract control.

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

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

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

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

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

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

Understanding the Requirement:

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

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

Salesforce CPQ Lookup Field Behavior:

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

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

Steps to Implement the Solution:

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

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

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

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

Step 5: Save the field set.

Integration with the Quote Line Editor:

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

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

Key Considerations:

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

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

Validation:

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

ï‚· Requirement Overview:

Admin needs to enable Additional Discounts at both the Quote and Group levels in the Line Editor.

ï‚· Solution Steps:

For the Quote Object:

Navigate to Setup > Object Manager > Quote.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

For the Quote Line Group Object:

Navigate to Setup > Object Manager > Quote Line Group.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

ï‚· Testing:

Open the Quote Line Editor and confirm the visibility of the Additional Discount fields at both levels.

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

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:

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.

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

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:

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.

ï‚· Scenario Breakdown:

Adventure in a Box:

List Price = $10

Discount = 50%

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

Premium Support:

Percent of Total Base = List Price.

Percent of Total = 10%.

ï‚· Calculation of Premium Support:

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

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

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

Requirement:

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:

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:

Reference specific Error Condition records in the Advanced Condition field of a Product Rule.

ï‚· Solution:

Use the Index field value from the Error Condition record in the Advanced Condition formula.

ï‚· Example:

If the Index field value is 1 for a specific Error Condition, reference it as 1 in the Advanced Condition (e.g., 1 AND 2).

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

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

ï‚· Explanation:

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

ï‚· Validation:

This behavior is standard and cannot be overridden without customizations.

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

ï‚· Requirement Overview:

Universal Containers wants to show Quote Line items grouped by Product Family with subtotals for each family in Quote Documents.

ï‚· Solution Details:

Salesforce CPQ allows grouping of Line Items in Quote Templates.

Setting SBQQ__ProductFamily__c as the Group field organizes the Quote Lines into separate sections for each Product Family.

ï‚· Configuration Steps:

Navigate to the Quote Template.

Create a new Line Items Section.

In the Grouping field, set SBQQ__ProductFamily__c.

Save and test the template by generating a Quote Document.

ï‚· Validation:

Confirm that the generated document displays separate tables for Hardware, Software, and Professional Services, with subtotals for each group.

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

Automatically apply a 25% discount to a specific Product Option within a bundle.

ï‚· Solution:

Option C: The Discounted by Package field ensures that the Product Option inherits discounts applied to the bundle as a whole.

Option D: A Price Rule specifically targeting this Product Option can enforce the 25% discount when it is added to the bundle.

ï‚· Why Other Options Are Incorrect:

A: The Option Discount (%) field on the Product Feature applies discounts to all options, not just a specific one.

B: The Option Discount (%) field on the Product Option does not dynamically apply discounts based on specific scenarios.

ï‚· Salesforce CPQ Reference:

Configuration and discounting for bundles and Product Options are documented under Bundle Pricing Configuration Guidelines ​.

ï‚· Requirement Overview:

A nonrenewable subscription Product priced annually.

ï‚· Key Field Configurations:

Subscription Term = 12: Specifies an annual subscription.

Subscription Type = One-Time: Indicates that the Product is nonrenewable.

Subscription Pricing = Fixed Price: Defines a flat annual price.

ï‚· Steps to Configure:

Navigate to the Product record.

Update the fields as specified above.

Save and test by adding the Product to a Quote.

ï‚· Validation:

Confirm the subscription term and pricing are applied correctly and the product does not renew automatically.

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

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

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

ï‚· Scenario:

Original subscription: $600 Net Unit Price × Quantity 10 × 24 months = $14,400.

Refund: Ten months into the contract, 14 months remain unused.

ï‚· Calculation:

Refund amount = ($600 × 10 × 14) ÷ 24 = -$3,500.

Amended subscription refund (Quantity = 0): 14 months refund prorated = -$2,500.

ï‚· Why Other Options Are Incorrect:

A, C, D: The refund calculations either overstate or understate the prorated refund based on the subscription term and remaining months.

ï‚· Salesforce CPQ Reference:

Prorated refunds and subscription amendments are explained in CPQ Subscription Pricing Documentation ​.

ï‚· Requirement:

Allow users to generate output documents in Microsoft Word format.

ï‚· Solution:

The Allow Output Format Change checkbox in User Settings enables users to select alternative formats like Microsoft Word during document generation.

ï‚· Why Other Options Are Incorrect:

A: The checkbox is user-specific, not template-specific.

C: Creating a second template is unnecessary when users can dynamically change the format.

D: Template Sections do not control output formats.

ï‚· Salesforce CPQ Reference:

Configuring user settings for document generation is detailed in CPQ Quote Templates Documentation ​.

ï‚· Real-Time Calculation:

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

ï‚· Field Behavior:

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

ï‚· Salesforce CPQ Reference:

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

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.

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

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

ï‚· Simplification Method:

By adding the PDF as a required Additional Document in the Quote Template, Salesforce CPQ ensures the PDF is automatically included with each generated Quote.

ï‚· Steps to Configure:

Navigate to the Quote Template.

Add the PDF file under the Additional Documents section.

Mark it as required for automatic inclusion.

ï‚· Salesforce CPQ Reference:

The Additional Documents feature simplifies document management in Quote Templates ​.

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

In Salesforce CPQ, amendments adjust subscription quantities incrementally. The original sale (Quote Line and Subscription) is 100. The first amendment reduces to 80, a decrease of 20, so the Quote Line is 80 (absolute), and the Subscription delta is -20 (reflecting the change). The second amendment increases to 120, an increase of 40 from 80, so the Quote Line is 120, and the Subscription delta is 40. Subscription quantities in amendments show the net change (-20, 40) rather than absolute values (80, 120), aligning with CPQ’s amendment mechanics. Option B correctly reflects this: Quote Lines (100, 80, 120) show user-facing totals, while Subscriptions (100, -20, 40) show deltas. Salesforce CPQ documentation explains this behavior in amendment scenarios.

Background Context:When amending a contract in Salesforce CPQ, issues with net pricing arise if the amendment impacts existing subscription products. Subscription products often rely on Discount Schedules for calculating discounts, especially when quantity changes. The "Cross Order" field on Discount Schedules ensures discounts account for cumulative quantities across multiple orders or contracts.

Problem Analysis:

The reported issue involves incorrect net pricing specifically when the quantity of existing products is adjusted during contract amendments.

This aligns with the functionality of Discount Schedules, where the total quantity determines the discount applied. Without "Cross Order" enabled, Salesforce CPQ considers only the current order's quantities rather than aggregating across orders.

Root Cause Identification:

Discount Schedule and Cross Order:If the Discount Schedule associated with these products does not have "Cross Order" enabled, any amendments won't consider cumulative quantities. Instead, the system recalculates based on only the new or adjusted quantities, leading to incorrect net pricing.

Supporting Evidence:

Salesforce documentation highlights that Cross Order must be selected in the Discount Schedule for accurate discount calculations across multiple orders or contracts. Otherwise, amendments operate in isolation​​.

The feature ensures that ongoing contracts retain accurate pricing based on total historical quantities.

Recommended Resolution:

Navigate to the Discount Schedule associated with the affected products.

Verify and enable the Cross Order checkbox:

Go to Setup > Discount Schedules.

Locate the relevant Discount Schedule.

Edit the schedule and enable Cross Order.

Test the functionality by amending the contract and verifying the net pricing calculations.

Preventative Actions:

For all subscription-based products relying on Discount Schedules, ensure Cross Order is enabled during initial configuration.

Provide training to Salesforce CPQ admins to understand the implications of Discount Schedule settings on pricing.

By following these steps and verifying the Discount Schedule configuration, the issue can be resolved, ensuring consistent and accurate net pricing during contract amendments.

ï‚· Scenario Overview:

Asset Conversion is set to One per Unit, so each unit sold creates a separate Asset record.

ï‚· Object Relationships:

During Order and Contract processes:

Order Product: Reflects the total quantity of Product A as a single record.

Asset: Creates two Asset records, one for each unit.

ï‚· Validation:

Confirm that the Asset records show separate entries for each unit sold, while other objects (e.g., Order Product) do not duplicate records.

ï‚· Requirement:

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:

Restrict the products visible during the configuration of a dynamic bundle.

ï‚· Solution:

Use a Default Filter in a Product Rule. This ensures only the specified set of products is displayed in the configurator for the dynamic bundle.

ï‚· Why Other Options Are Incorrect:

A: Optional filter is not a valid Product Action.

B: The Show action determines visibility but does not enforce restrictions on selections dynamically.

D: Enable action is used to activate a previously disabled product but does not filter selections.

ï‚· Salesforce CPQ Reference:

Dynamic bundles and filtering actions are detailed in CPQ Product Rule Configuration Guidelines ​.

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

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

ï‚· Advanced Approvals Context:

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

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

ï‚· Functionality:

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

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

ï‚· Validation:

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

ï‚· Requirement:

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

In Salesforce CPQ, the Option Layout field on the Product record determines how bundle options are presented in the configurator. To allow users to view all available and selected options by scrolling on a single page, the "Sections" layout is ideal. This layout organizes options into collapsible sections based on Product Features, keeping everything visible on one page without requiring navigation steps like a wizard. Option A (Wizard) presents options step-by-step across multiple pages, which doesn’t meet the single-page requirement. Option B (assigning all options to one feature) limits organization and doesn’t address the layout requirement. Option C (Dynamic selection method) controls runtime behavior of options but doesn’t influence the single-page scrolling display. Salesforce CPQ documentation confirms that the "Sections" layout supports a scrollable, single-page view.