CPQ-Specialist Salesforce Certified CPQ Specialist (SP25) Free Practice Exam Questions (2025 Updated)

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

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

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

 Root Cause:

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

 Steps to Resolve:

Navigate to Setup > Object Manager > Quote.

Locate the Calculating Fields field set.

Add the Primary field to the field set.

 Testing:

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

 Salesforce CPQ Reference:

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

In Salesforce CPQ, importing data for products and bundles requires a specific order to ensure referential integrity, as certain objects depend on others being present. The correct sequence starts with the Product (the parent record), followed by Product Features (defining sections or categories within the bundle), Product Options (specific selectable items under features), Option Constraints (rules governing option selections), and finally Configuration Attributes (additional settings for dynamic configuration). Option A reflects this hierarchical dependency accurately. Option B includes unrelated objects like Product Action and Error Conditions, which pertain to rules rather than bundle structure. Option C starts with Product Option before Product, which violates dependency rules since options require a parent product. Option D begins with Product Features before Product, which is incorrect as features need a product to associate with. Salesforce CPQ documentation emphasizes this order for successful data imports.

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

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:

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

In Salesforce CPQ, Product Selection Rules automatically add products to a Quote based on defined conditions. These rules typically evaluate and execute when the Quote is saved, as this triggers the full application of rules and updates to the Quote Lines. Option D aligns with this behavior—saving the Quote ensures the Conference Pass is added. Option A (Configuration Attribute selection) relates to configurator actions, not quote-level rules. Option B (Product selection) triggers option-specific rules, not quote-wide additions. Option C (Quote calculation) updates pricing, not product additions. Salesforce CPQ documentation confirms rule execution on save.

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

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

 Requirement Overview:

Prevent users from making price changes to Quotes or Quote Lines that have already been approved.

 Solutions:

C. Validation Rule:

Create a Validation Rule to block any material changes to approved Quotes or Quote Lines.

D. Product Rule:

Use a Validation Product Rule to prevent edits to pricing fields once a Quote has been approved.

 Steps to Configure:

Validation Rule:

Navigate to Setup > Validation Rules for the Quote and Quote Line objects.

Create rules to restrict edits when the status is set to Approved.

Product Rule:

Create a Validation Product Rule targeting Quote or Quote Line fields.

 Validation:

Test by attempting to edit an approved Quote and verifying the system prevents changes.

Requirement Overview:

A product priced at 100 USD and 95 EUR needs to be included as part of a bundle.

Solution:

Bundled Products: Setting the Bundled field to True ensures the product is included in the bundle's total price.

Configure the Price Book Entries with the required prices for the respective currencies.

Steps to Configure:

Navigate to the Product in the 2019 Price Book.

Set 100 USD and 95 EUR as the Price Book Entries.

On the Product Option, mark the Bundled field as True.

Validation:

Test the bundle by adding it to a Quote and verifying the correct pricing behavior.

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

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

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

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.

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