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:

To allow a user to view all available and selected options by scrolling on a single page in Salesforce CPQ, the Admin should set the Option Layout field on the parent Product record to Sections. This setting displays all Product Features and their associated Product Options as sections on a single page, enabling users to scroll through and view everything without navigating multiple tabs or steps.

Option A:
Update Option Layout to Wizard is incorrect because the Wizard layout presents Features as sequential steps with Next/Previous navigation, not a single scrollable page.
Option B:
Assign Option Selection Method Dynamic is incorrect because the Dynamic method uses a pre-filtered Add Options button for product selection, which doesn’t ensure all options are visible on one page.
Option C:
Assign all Options to one Feature is incorrect because, while it groups options, it doesn’t guarantee a single scrollable page unless paired with the Sections layout. It also limits organization if multiple Features are needed.
Option D:
Update Option Layout to Sections is correct as it meets the requirement by displaying all Features and Options in a single, scrollable page, which is the default behavior when Option Layout is set to Sections or left blank.

Reference:
Salesforce Trailhead, “Enhance User Experience with Feature Configuration”: “The Option Layout field on the lead product determines the layout and user experience of configuration pages for bundles… Sections: Features are listed in boxes, one after the other. Sections are the default layout when the Option Layout field is blank.”

Explanation:

The requirement has two parts:
Separate by Product Family:
Products from Hardware, Licenses, and Maintenance must be rendered in different columns/sections on the document.
Separate by Bundle:
The products from each family must be grouped together by the bundle they belong to. A user should easily see all the Hardware from Bundle A, then all the Hardware from Bundle B, etc.

Here's how the correct answers work together:

B. Use Filter Field in Line Item Sections:
In Quote Document Templates, a Line Item Section is used to define how a group of quote lines is displayed. The Filter field on a Line Item Section uses a SOQL-like WHERE clause to determine which quote lines belong in that section.
The admin would create three different Line Item Sections:

One with the filter Product.Family = 'Hardware'
One with the filter Product.Family = 'Licenses'
One with the filter Product.Family = 'Maintenance'

This satisfies the first requirement of rendering products from each family in different sections.

C. Use a Custom Grouping Field:
The Group field in a Line Item Section determines the order in which records are grouped together. To group lines first by their parent bundle, you need a field that identifies which bundle a line belongs to.
A standard field like ParentQuoteLine.Name or ParentQuoteLine.Number could be used, but these might not be unique if the same bundle type is added multiple times. A more robust approach is to create a custom formula field on the Quote Line object that concatenates the parent bundle's name and line number (e.g., ParentQuoteLine.Name & '-' & ParentQuoteLine.Number).
By placing this new formula field in the Group field of each of the three Line Item Sections, the output will first group all lines by their parent bundle and then, within that bundle, by the product family (because they are in different sections). This satisfies the second requirement of keeping each bundle's products together in their family groups.

Why the other options are incorrect:
A. Leverage the Conditional Print field:
The {!ConditionalPrint} merge field is used to hide a section or block of text if a condition is not met (e.g., "only print this disclaimer if the quote total is over $10,000"). It is not designed for the complex filtering and grouping of individual line items required here. The Filter field is the correct tool for selecting which lines go into a section.
D. Populate the Sort Order field:
The Sort Order field on the Product object controls the default order in which products appear in picklists (like in the QLE). It does not control the sorting of quote lines on an output document. Sorting on the document is controlled by the Group and Sort fields within the Line Item Section of the template. This approach would not achieve the required grouping by bundle.

Reference:
Salesforce CPQ documentation on "Creating Quote Document Templates" covers the use of the Filter, Group, and Sort fields in Line Item Sections to organize quote lines for output.

Explanation:

Why This Works:

Evaluation Scope = Configurator
Ensures the Price Rule runs during product configuration (when Option A is selected), not just during quote calculation.

Configurator Evaluation Event = Edit
Triggers the rule in real time (as the user edits Option A), updating Option B’s Quantity immediately.

Why Other Options Fail:

A & C (Calculator Scope):
Rules run only during quote calculation (e.g., on Save), not in real-time configuration.

D (Configurator + Save):
"Save" delays the update until the user saves the bundle, breaking the real-time requirement.

Key Takeaway:
For real-time updates between Product Options, use:
✅ Configurator Scope + Edit Event.

Explanation:

The setting you’re looking for is:

Calculate Immediately

This is a managed package setting under:
Salesforce CPQ Package Settings → Pricing and Calculation tab

When enabled:
CPQ triggers calculations immediately after each change in the QLE.
Reps don’t have to manually click the Calculate button each time.

It improves speed and convenience but may slightly slow performance if you have large quotes, because each change recalculates prices instantly.

This is exactly what the question describes.

✅ Correct answer: C. Calculate Immediately

❌ Why the Others Are Incorrect

A. Use Legacy Calculator

That’s an older calculation engine used before Salesforce CPQ’s newer advanced calculator.
Has nothing to do with auto-calculation after each change.
❌ Incorrect.

B. Enable Quick Calculate

This option controls whether the Quick Save feature triggers full price calculations.
It does not automatically calculate after every field change in the QLE.
Useful for faster saves but not the same as instant recalculation.
❌ Incorrect.