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

Requirement:

Prevent users from reconfiguring a bundle after its initial configuration.

Solution:

Set Configuration Type to Allowed to permit configuration during initial setup.

Set Configuration Event to Add to allow configuration only when the product is added, blocking reconfiguration later.

Why Other Options Are Incorrect:

A: Disabled blocks all configuration, including initial setup.

B: Configuration Event = Always allows continuous reconfiguration.

D: Reconfigure Line Custom Action is unrelated to this requirement.

Salesforce CPQ Reference:

Configuration Type and Event settings are documented in Bundle Configuration ​.

ï‚· Scenario:

The Create Order button generates an Order with half the Quote Lines, and the Ordered checkbox is selected.

ï‚· Outcome:

When the Ordered checkbox is checked, remaining Quote Lines are eligible for a new Order. A second Order will be generated for the remaining lines.

ï‚· Why Other Options Are Incorrect:

A: An Order without Order Products is invalid in this scenario.

C: No error is thrown because multiple Orders are allowed from the Quote.

D: Existing Orders are not updated with new Quote Lines.

ï‚· Salesforce CPQ Reference:

The behavior of the Create Order button is detailed in CPQ Order Management documentation ​.

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

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

ï‚· Smart Approvals Overview:

Salesforce CPQ's Smart Approvals streamline the approval process by re-evaluating previously approved records to avoid redundant approvals.

ï‚· Rejected Quotes Resubmission:

If a quote is rejected, and the user resubmits it without exceeding previously approved values, it bypasses the full approval chain and is sent directly to the person who rejected it.

This functionality minimizes unnecessary delays and ensures efficient quote handling.

ï‚· Documentation Alignment:

Smart Approvals Configuration and behavior as outlined in CPQ guidelines ensure approval efficiency ​.

ï‚· Requirement:

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

ï‚· Solution:

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

ï‚· Why Other Options Are Incorrect:

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

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

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

ï‚· Salesforce CPQ Reference:

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

ï‚· Requirement:

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

ï‚· Requirement:

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

ï‚· Solution:

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

ï‚· Why Other Options Are Incorrect:

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

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

ï‚· Salesforce CPQ Reference:

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