CPQ-Specialist Exam Dumps - Salesforce Certified CPQ Specialist (SP25)

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

ï‚· Field Location and API Name:

The custom text field Additional_Text__c resides on the Quote object.

In Salesforce CPQ, the correct syntax to reference fields in HTML templates is to use the merge field syntax appropriate to the object.

ï‚· Syntax Explanation:

{!quote.Additional_Text__c} directly references the field from the Quote object in a format recognized by the CPQ document generation engine.

Alternative options such as {ISBQQ__Quote__r.Additional_Text__c} reference lookup relationships and do not apply here.

ï‚· Salesforce CPQ Reference:

As per the Quote Template Content documentation, use the merge fields directly associated with the object being utilized in the template ​.

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.

ï‚· Requirement Overview:

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

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

ï‚· Key Mechanism:

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

ï‚· Steps to Resolve:

Navigate to the Product Option record for Product A.

Set the Apply Immediately field to True.

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

ï‚· Justification:

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

ï‚· Requirement:

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

ï‚· Solution:

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

ï‚· Why Other Options Are Incorrect:

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

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

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

ï‚· Salesforce CPQ Reference:

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

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

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

ï‚· Requirement Overview:

Universal Containers wants to use split Orders to manage fulfillment by separating items based on their shipping schedules.

ï‚· Key Considerations:

Component-type Options: When splitting Orders, component-type Options are treated independently and can be split into different Orders.

Bundle Structure: Splitting Orders does not maintain the bundle structure, meaning the parent-child relationships of the bundle are not preserved in the split Orders.

ï‚· Steps to Configure:

Ensure that the Order by Quote Line Group field or a custom grouping field is used to facilitate splitting the Orders based on shipment schedules.

ï‚· Validation:

Test the split Order functionality by creating a Quote with a hardware bundle and ensuring that the bundle and components can be split appropriately.