Sales-Admn-202 Practice Exam Questions with Answers Salesforce Certified CPQ Administrator Certification

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

? Issue:

The validation error message appears immediately after a user sets a specific value in the Configuration Attribute, even before saving.

? Solution:

Setting Apply Immediately to False ensures that changes in Configuration Attributes do not trigger immediate validations. Instead, validations occur only upon clicking Save.

? Why Other Options Are Incorrect:

A: Evaluation Action does not exist as a field for Product Rule Error Conditions.

C: Changing the Apply Immediately field for Product Options does not affect the Configuration Attribute's behavior.

D: Setting Evaluation Event to Save applies to the rule's scope but does not address Configuration Attribute settings.

? Salesforce CPQ Reference:

Configuration Attribute Settings are explained in CPQ Configuration Attribute documentation ?.

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

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:

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:

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

Scenario:

Renewal Pricing Method is set to List, and the Quote contains standalone fixed-price subscription and non-subscription products.

Behavior:

Discounts from the original Quote are carried forward to the renewal Quote automatically as part of the renewal process, ensuring consistency in pricing.

Salesforce CPQ Reference:

Renewal Quote generation processes consider discounting rules as part of the Renewal Pricing Method ?.

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

? Scenario:

A subscription product does not appear in the Product Selection screen during search.

? Possible Causes:

A: The Active checkbox must be TRUE for the product to appear.

D: The product requires a Pricebook Entry in the corresponding Quote’s Pricebook.

E: If the Component checkbox is TRUE, the product is treated as a bundle component, not standalone, and will not appear in search results.

? Why Other Options Are Incorrect:

B: Cost records are unrelated to product visibility.

C: The Optional checkbox determines bundling behavior, not search visibility.

? Salesforce CPQ Reference:

Product visibility settings are detailed in CPQ Product Selection Configuration ?.

? Requirement:

Ensure the price of Tiny Boxes ($0.005) is handled with proper decimal precision.

? Solution:

Adjust the Unit Price Scale to 3 in the Pricing and Calculation Package Settings, enabling Salesforce CPQ to handle prices up to three decimal places.

? Why Other Options Are Incorrect:

A: Field-level precision on Quote Line does not control pricing precision.

C: The Product record's Unit Price Scale cannot override global settings.

D: Price Rules are unnecessary for simple decimal precision adjustments.

? Salesforce CPQ Reference:

Decimal precision configuration is described in CPQ Pricing Settings ?.

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

? CPQ Price Calculation Sequence:

The Regular Price is calculated as part of the price waterfall, and several factors influence it.

? Key Contributors:

Prorate Multiplier: Adjusts prices for subscription products based on term alignment.

Contracted Price: Overrides the List Price for specific customers.

Discount Schedules: Apply volume or tiered discounts during price calculation.

? Why Other Options Are Incorrect:

A: Additional Discount Fields apply after Regular Price is calculated.

D: Target Customer Amount is used in quoting, not directly in Regular Price calculation.

? Salesforce CPQ Reference:

Price waterfall and Regular Price contributors are detailed in CPQ Pricing Configuration ?.

? Requirement Overview:

Admin needs to generate one Asset record for each unit of the Product upon contracting.

? Solution Details:

The Asset Conversion field determines how Salesforce CPQ creates Asset records from Quote Lines.

Setting Asset Conversion to One per Unit ensures that for each quantity of the Product, a corresponding Asset is created.

? Steps to Configure:

Navigate to the Product record.

Locate the Asset Conversion picklist and select One per Unit.

Save and test the configuration by creating a Quote, contracting it, and verifying the Asset creation.

? Requirement Overview:

Universal Containers needs to attach required PDF documents stored in Salesforce Documents to the Quote output.

? Solution:

Use the Additional Document feature on the Quote Template to include PDF files in the generated output.

? Steps to Configure:

Navigate to the Quote Template.

Create an Additional Document for each required PDF:

Reference the document stored in Salesforce.

Save the Quote Template.

? Validation:

Generate a Quote document and confirm that the Additional Documents are included as attachments.

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

Notify users in the Quote Line Editor when approval is required to discourage excessive discounting.

? Solution:

Use a Product Rule with Alert Action to display a notification or message in the Quote Line Editor when a user exceeds predefined discount thresholds.

? Why Other Options Are Incorrect:

A: Validation Rules prevent actions but do not notify users.

B: Filter Rules are used for restricting product selection, not notifications.

D: Selection Rules govern product compatibility and are irrelevant here.

? Salesforce CPQ Reference:

Alert actions in Product Rules are outlined in CPQ Product Rule Configuration

? Hierarchy of Discount Schedule Application:Salesforce CPQ applies Discount Schedules based on object precedence.

Contracted Price: Overrides Discount Schedules at the Product or Feature level when specific pricing agreements are in place for an Account.

Product Option: A Discount Schedule on a Product Option takes precedence over one defined at the Product Feature level.

? Key Configurations:

Contracted Price: Navigate to the Contracted Price record and add the Discount Schedule.

Product Option: Assign the Discount Schedule on the Product Option record.

? Validation:

Test configurations to confirm the Discount Schedule is applied at the appropriate level and overrides the Feature-level Discount Schedule.

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

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.

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

Block pricing in Salesforce CPQ is used when a fixed price applies to a quantity range, as in this tiered pricing scenario (e.g., $1,800 for 6-10 licenses). Option A sets the Pricing Method to "Block" on the Product, enabling this model. Option E involves creating Block Pricing records for each tier (e.g., 1-5 = $1,000), defining the fixed prices. Option B (Non Discountable = True) ensures no further discounts apply, meeting the requirement. Option C (Fixed Price) applies a single price regardless of quantity, not tiered pricing. Option D (Slab Discount Schedule) is for percentage-based discounts, not fixed block prices. Salesforce CPQ documentation validates this setup for block pricing.

? Issue:

Quote Lines on Quote A are grouped incorrectly in the output document.

? Possible Causes:

C: Quote Line Groups: Existing Quote Line Groups on the Quote override the Group Field setting in the template.

D: Group Field in Template Section: The Group Field value in the Line Items template section may cause unexpected grouping.

? Why Other Options Are Incorrect:

A: The Modified By field has no impact on template grouping.

B: Configuration Attributes like location affect product selection, not grouping in Quote templates.

? Salesforce CPQ Reference:

Grouping behavior is explained in the Quote Templates and Line Item Configuration documentation ?.

? Scenario:

Automatically select the Diamond Warranty Option in the child bundle if Premium Container is selected in the parent bundle and no warranty is selected.

? Solution:

Child Bundle Condition Level = 1: Ensures the condition applies at the child bundle level.

Child Bundle Action Level = None: Prevents overwriting user-selected options but enables automatic defaulting when none are selected.

? Why Other Options Are Incorrect:

B & C: Setting inappropriate levels may lead to overwriting user selections or incorrect rule execution.

D: Setting both levels to None results in no action or condition enforcement.

? Salesforce CPQ Reference:

Configuration rules and child bundle handling are outlined in CPQ Bundle Configuration Guidelines ?

? Issue Context:

A Contract could not be created from an Order for a new customer.

? Troubleshooting Steps:

A. Confirm Order Product Activation:

Contracts can only be generated for activated Order Products.

C. Check Apex Jobs:

Errors in the contracting process are logged in Apex Jobs. Review these logs for potential issues.

E. Ensure Subscription-Based Order Product:

Contracts require at least one subscription-based Product on the Order.

? Validation:

Verify that all conditions are met and retest the Contract creation process.

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

Understanding the Requirement:

Universal Containers wants a bundle with pre-selected Product Options.

Sales reps should mostly leave the default configuration as-is but need the flexibility to make changes when required.

Salesforce CPQ Feature Overview:

Configuration Type:

Determines whether sales reps can modify the configuration of a bundle product.

Setting it to Allowed permits the flexibility to configure without mandating it.

Configuration Event:

Defines when the bundle configurator is accessible.

Setting it to Edit prevents the configurator from opening automatically but allows sales reps to access it by clicking the "Reconfigure" link.

Configuration Steps:

Navigate to the Bundle Product record in Salesforce CPQ.

Set the Configuration Type field to Allowed. This ensures the configurator is optional and not enforced.

Set the Configuration Event field to Edit. This enables the configurator to be accessible only upon user action.

Key Behaviors:

With these settings, sales reps can use the default configuration but still make changes if needed by accessing the configurator manually.

The "Reconfigure" link in the quote line becomes available for editing.

Testing and Validation:

Add the bundle to a Quote.

Verify that the configurator does not open automatically.

Check that the "Reconfigure" link is accessible on the Quote Line for editing options.

? Requirement:

Sales reps need to identify Product Options linked to Quote Lines in the Quote Line Editor.

? Solution:

Enabling Visualize Product Hierarchy organizes Quote Lines based on their position within the bundle, displaying the parent-child relationship.

? Why Other Options Are Incorrect:

A: The Product Option Drawer enables detail viewing but does not organize Quote Lines.

B: Preserve Bundle Structure applies to output documents, not the Line Editor.

D: Keep Bundle Together affects grouping but not hierarchy visualization.

? Salesforce CPQ Reference:

Hierarchy settings are covered in the Quote Line Editor Configuration documentation ?.

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

Migrate existing contracts to a new Product version upon renewal.

? Solution:

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

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

? Why Other Options Are Incorrect:

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

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

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

? Salesforce CPQ Reference:

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

Requirement:

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

Ensure that the cubic volume selected at the bundle level applies to all Product Options.

? Solution:

Option C: Setting the Configuration Attribute's Apply to Product Options to True ensures the selected value cascades to all Product Options within the bundle.

Option D: Creating a bundle-level Configuration Attribute allows sales reps to select a single cubic volume value that governs all Product Options in the bundle.

? Why Other Options Are Incorrect:

A: Lookup Price Rules reference external objects but are not relevant to syncing a volume value across Product Options.

B: Feature-level Configuration Attributes are scoped to specific features, not the entire bundle.

? Salesforce CPQ Reference:

The functionality of Configuration Attributes and their application to Product Options is documented in Bundle Configuration Guidelines ?.

https://help.salesforce.com/s/articleView?id=sf.cpq_config_attribute_guidelines.htm &type=5

? Requirement Overview:

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:

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

? Expected Behavior:

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

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

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

? Why Other Options Are Incorrect:

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

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

? Salesforce CPQ Reference:

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

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:

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:

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

? Relevant Fields on the Contracted Price Record:

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

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

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

? Salesforce CPQ Reference:

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

? Requirement:

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

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:

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.

? Bundle Configuration:

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

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

Other Options (Option 2 and Option 3):

Medium Storage Container: Not selected.

Custom Box Label: Not selected.

? Calculation:

Bundle Parent Product Price: $5.00

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

? Why Other Answers Are Incorrect:

A: Ignores bundled Option 4 price.

C: Includes non-selected options in the total.

D: Excludes all Option prices, which is inaccurate.

? Salesforce CPQ Reference:

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

? Requirement Overview:

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.

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

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

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

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

Ensure that products available for selection are filtered by the Quote’s currency.

? Solution:

CPQ filters products based on the Price Book Entries associated with the Opportunity/Quote’s currency.

? Why Other Options Are Incorrect:

A: Active currencies do not determine product availability.

B: Dated Exchange Rates do not affect product selection directly.

C: Products with a zero Pricebook Entry are not valid for selection.

? Salesforce CPQ Reference:

Multi-currency product selection is documented in CPQ Multi-Currency Configuration ?.

? Requirement:

Group products in collapsible sections based on Product Family in the Add Products page.

? Solution:

Set the Product Results Group Field Name in Additional Settings to Product Family. This groups products by their Product Family in the Add Products page.

? Why Other Options Are Incorrect:

A: Solution Groups apply to Quote Lines, not the Add Products page.

B: Adding fields to the Search Results Field Set does not enable grouping functionality.

C: The Product Search Plugin is unrelated to grouping.

? Salesforce CPQ Reference:

Configuring product grouping is detailed in CPQ Product Search and Results Configuration ?.

? Requirement Overview:

Automatically split Orders by delivery location based on Quote Line Groups.

? Key Configurations:

Order by Quote Line Group: Ensures that each Quote Line Group generates a separate Order.

Ordered Field = TRUE: Triggers the creation of Orders for the Quote Lines.

? Steps to Configure:

Ensure the Order by Quote Line Group field is checked on the Quote.

Mark the Ordered field as TRUE.

Test the Order creation process to verify separate Orders are generated by location.

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

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