Explanation:

In Salesforce CPQ, Discount Schedules can be used either to apply a discount as:

a percentage off the list price, or

a specific price (amount) that replaces the list price for each quantity tier.

When the question states:

“allow users to define Discount Tiers and use those values as the Regular Price instead of an Amount deducted from the List Price.”

…it means the customer wants the price in each tier to be treated as the regular price, not a discount off the list price.

This functionality is achieved via the Use Price for Amount checkbox in the Discount Schedule. When you:

Set Discount Unit = Amount

Enable Use Price for Amount

…it tells CPQ:

“Treat my tier values as the final price, not a discount amount.”

Choosing Override Behavior = All ensures that the defined tiers replace the price completely.

Hence, Option A is correct.

Why other options are incorrect

B: Percent discounts do not allow you to define regular prices directly; they only reduce the price by a percentage.

C: There’s no standard field called Override_Amount__c on tiers. Also, creating a custom field isn’t required for this use case.

D: Again, percent discounts cannot define fixed regular prices, and the User Defined option relates to allowing sales reps to enter tier thresholds, not the price.

Explanation:

The Business Requirement
UC wants to detect any discount applied on options in bundles. If any option is discounted, mark a custom field on the Quote (Is_Discounted__c) = TRUE.

The logic to achieve this:
1. Identify only the options inside bundles.
2. Check whether any of those lines have a discount greater than 0.

So, the price rule should target the Quote object, use a Summary Variable to scan Quote Lines, and apply Price Conditions on the summary variable to detect a discount.

✅ B. A Price Condition where the Tested Variable must equal 0. The Summary Variable should have these values: Aggregate Function — Max Target Object — Quote Line Aggregate Field — SBQQ__Discount__c

This is correct.

You need a Summary Variable on Discount across Quote Lines. You’d set it up as:
- Aggregate Function = MAX
- Aggregate Field = SBQQ__Discount__c
- Target Object = Quote Line

If any line has a discount > 0, the MAX value is greater than zero. In the Price Condition, you’d check:
Tested Variable = Summary Variable
Operator = Greater Than
Filter Type = Value
Filter Value = 0
This detects if any quote line is discounted.

✅ D. A Price Condition with: Object — Quote Line Field — SBQQ__ProductOption__c Operator — Not Equals Filter Type — Value Filter Value — (Null)
This is also correct.

SBQQ__ProductOption__c is populated on option lines (child products in bundles). If SBQQ__ProductOption__c is NOT null, it’s an option. So, this condition limits the summary variable only to options. This ensures the summary variable considers only bundle options, not the parent bundles themselves.

Why not the other options?

A. A Price Condition Tested Formula of SBQQ__RequiredBy__r.SBQQ__Bundled__c = TRUE
This is incorrect. The RequiredBy relationship points to the parent product option. However, SBQQ__Bundled__c doesn’t exist in that way. This condition would not reliably filter just option lines. Instead, SBQQ__ProductOption__c is the reliable indicator for identifying options.

C. A Price Condition with: Object = Quote Line Field = SBQQ__Discount__c Operator = Greater Than Filter Type = Value Filter Value = 0
This is incorrect on its own. This condition only tests individual quote lines for discount. It’s not appropriate for a Price Rule on the Quote level. Without summarizing across lines, it cannot flag the Quote itself if any option is discounted.

Hence, B and D are the correct combination.

✅ Recommended Setup

You’d configure:
- Summary Variable:
- Aggregate Function = MAX
- Aggregate Field = SBQQ__Discount__c
- Target Object = Quote Line
- Filter = SBQQ__ProductOption__c ≠ NULL

- Price Condition on Summary Variable:
- Tested Variable = [Summary Variable]
- Operator = Greater Than
- Filter Value = 0

- Price Action:
- Target = Quote.Is_Discounted__c
- Value = TRUE

That perfectly meets UC’s requirement.

Explanation:

1. Evaluation Priority Rules:

- Price Rules evaluate first by Calculator Evaluation Event in this order:
   On Initialization → Before Calculate → On Calculate → After Calculate
- Within the same event phase, lower Evaluation Order numbers run first

2. Why Rule B Runs First:

- On Initialization phase executes before all other phases
- Evaluation Order 20 doesn't matter here because no other rules are in this phase
- Rule B is the only one in the earliest phase

Why Other Options Are Wrong:

- A (On Calculate): Runs much later in the process
- C (Before Calculate): Runs after On Initialization phase
- A (Before Calculate, Order 10): Would run before Rule C but still after On Initialization

Key Point: Always check the Calculator Evaluation Event first - earlier phases always win regardless of Evaluation Order.

Explanation:

Scenario:
The Quote contains multiple bundles. Each bundle has options from 3 Product Families: Hardware, Licenses, Maintenance. On the output document, you want different sections for each Product Family, and within each section, products should be grouped by bundle.

✅ Grouping by Bundle
You want products grouped under each bundle. CPQ quote templates allow you to group lines using the Group Field on the Line Item section. But Quote Lines don’t natively store the Bundle Name or Number.

Therefore, you’d create a formula field on Quote Line that looks up the parent bundle’s Product Name or Bundle Number. For example:
BundleName & " - " & BundleNumber
You then set this formula field as the Group Field on the line item section. That way, each Product Family section groups lines by bundle. Hence, B is correct.

✅ Filtering by Product Family
Next, you need to separate products by Product Family into different sections. The correct way to restrict products shown in each Line Item section is the Filter Field.

You’d create:
- A Line Item Section for Hardware → Filter = Product Family = “Hardware”
- A Line Item Section for Licenses → Filter = Product Family = “Licenses”
- A Line Item Section for Maintenance → Filter = Product Family = “Maintenance”

Thus, D is correct because the Filter Field ensures each section only displays its relevant products.

Why not the other options?

A. Populate the Sort Order field on each Product record to properly sort the Quote Lines within each section.
Sorting only affects cosmetic order. It doesn’t handle filtering or grouping logic. It won’t create separate sections or ensure bundles appear distinctly.

C. Create a different Line Item section for each Product Family and leverage the Conditional Print field to show the correct products.
Conditional Print hides or shows the entire section based on quote-level logic. It’s not for filtering individual quote lines inside a section. Filtering individual lines requires the Filter Field.

Hence B and D are correct.

Explanation:

UC’s scenario:

Product should only be sold as part of a bundle.
Product should not appear on the Product search screen when reps add products manually.

This is exactly the purpose of the Hidden checkbox on a Product record in Salesforce CPQ:

“When you select the Hidden checkbox on a product, that product does not appear in product search results or on the Add Products page. However, you can still add it as a feature option in a bundle.”

So:

✅ Product can still be used as a bundle component.
✅ Users cannot select it directly when quoting standalone products.

This is the recommended best practice for bundle-only components.

Why not the other options?

A. Set the Configuration Type field to Allowed.
The Configuration Type controls how bundles behave during configuration (Allowed, Required, Disabled). It does NOT hide a product from product searches.

B. Select the Component checkbox on the Product.
The Component checkbox indicates the product is used as a sub-product in a bundle, but it does not hide it from product search results.

D. Set the Asset Conversion field to One per unit.
Asset Conversion controls how CPQ converts quote lines into assets during contracting. It’s irrelevant to product search visibility.