Explanation:

Configuration Type determines whether the user can or must enter the configuration page when adding the bundle to the quote.
✅ Disabled → user cannot access the configurator for this bundle at all.
✅ Allowed → user can access the configurator optionally.
✅ Required → user must go through the configurator to add the bundle.

Configuration Event determines when the configurator launches. For example:

✅ Always → configurator launches whenever you add or edit the bundle.
✅ Add → configurator launches only when adding the bundle, not editing.
However, if the Configuration Type is Disabled, the configurator will never launch, regardless of the Configuration Event setting.

In this scenario:

Universal Containers has a fixed bundle with selected Product Options. After selecting the bundle, the user should bypass the configuration process.

Hence, we need to disable the configurator completely for this bundle. The proper setup is:
✅ Configuration Type → Disabled
✅ Configuration Event → technically irrelevant if Disabled, but Salesforce best practice is to set it to Always for consistency.

So A is the correct choice.

Explanation:

The requirement is to ensure that quotes have the latest information before submission without requiring the sales rep to reopen the Quote Line Editor (QLE).

Why Option C is Correct (Add Calculate Button to Quote Layout):

The Calculate button allows users to manually trigger a recalculation without reopening the QLE.
This ensures pricing, discounts, and other fields are updated before submission.

Why Option D is Correct (Create a Flow to Trigger Recalculation on Save):

An automatic Flow can be configured to recalculate the quote whenever the record is saved.
This eliminates manual effort and ensures accuracy before approval.

Why Other Options Are Incorrect:

A (Changing Calculating Fields Field Set): This defines which fields are recalculated, but does not trigger recalculation itself.

B (New Lightning Button): While possible, this requires custom development (Apex/JS) and is less efficient than built-in options (Calculate button or Flow).

Explanation:

Let’s start with the scenario:

“Universal Containers licenses shipping software that is sold for a fixed price based on each quantity tier… For example, buying eight licenses costs a total of $1,800 rather than multiplying unit price by quantity. Further discounts are unavailable.”

This describes block pricing in Salesforce CPQ:
Instead of unit price × quantity, you define blocks:
e.g. 1–5 = $1,000
6–10 = $1,800
etc.

A single price applies to the entire quantity range rather than per unit.

Hence, the correct configuration steps are:

✅ D. Set Pricing Method to Block

On the Product record, set:
Pricing Method = Block

This tells CPQ to look at the Block Pricing records rather than standard unit pricing.

✅ E. Create Block Pricing records on the Product for each quantity tier

You’ll create Block Price records:
Range = 1–5 → $1,000
Range = 6–10 → $1,800
etc.

No discounts are involved in block pricing in this scenario; you’re defining fixed prices per block.

✅ B. Set Non-Discountable to True

The question says:
“Further discounts on this product are unavailable.”

So you must:
Non-Discountable = TRUE

This prevents any additional discounts (e.g. Partner discounts, manual adjustments) from reducing the block price.

Explanation:

This question focuses on controlling the visibility and behavior of the "Reconfigure" button, which is a CPQ Custom Action. The best way to show or hide a Custom Action based on a condition (like the quote's type) is to use Custom Action Conditions.

C. Create a Custom Action Condition on the Reconfigure Line custom action where SBQQ__Type__c is not equal to "Renewal".

The Reconfigure button is a Custom Action:
The "Reconfigure Line" button (represented by a wrench icon) that appears in the Quote Line Editor is actually a CPQ Custom Action.
Conditional Visibility: Custom Actions can have conditions defined that control when they are displayed to the user.
Quote Type Field: The SBQQ__Type__c field on the Quote object holds the value for the quote's type, such as "New", "Amendment", or "Renewal".
Solution: By setting a condition on the "Reconfigure Line" Custom Action that checks if the Quote. SBQQ__Type__c field is not equal to "Renewal", the button will appear on New and Amendment quotes but will be hidden on Renewal quotes, perfectly matching the requirements.

Why other options are incorrect
A. Ensure SBQQ__ReconfigurationDisabled__c is set to TRUE on the Bundle product:
This checkbox completely disables reconfiguration for the bundle on all quote types, including New and Amendment quotes. The requirement is to allow reconfiguration on those quote types, so this option is incorrect.
B. Create a Custom Action Condition on the Reconfigure Line custom action where SBQQ__Type__c is equal to "Renewal":
This would have the opposite effect of what is required. This condition would only display the "Reconfigure" button on Renewal quotes and hide it on New and Amendment quotes.
D. Ensure SBQQ__ReconfigurationDisabled__c is set to "Disabled" on the Bundle product:
This refers to the Configuration Type field on the product, which disables the configuration at all times. This is similar to option A and does not meet the requirement to allow reconfiguration on new and amendment quotes.

Reference
For more information, see the Salesforce CPQ documentation on Custom Actions and their conditions, or review the resources mentioned in the search results.

Explanation:

To set up the Option Constraint in Salesforce CPQ where selecting Product B requires Product A to also be selected (a dependency), the Admin must take the following two steps:
C. type should be dependency
This is the core of establishing the dependency relationship. By setting the "Type" field on the Option Constraint record to 'Dependency', you ensure that the Constrained Option (Product B in this case) becomes available for selection only when the Constraining Option (Product A) has been chosen.
D. The Active checkbox should be set to True
For any Option Constraint to be enforced and actively control the product bundle configuration, it must be activated. The "Active" checkbox on the Option Constraint record enables the rule to take effect within the Salesforce CPQ environment.

Why other options are not the primary answers:
A and B. Option Constraint Group should be populated:
While Option Constraint Groups are used in Salesforce CPQ, they are specifically for scenarios where multiple constraining options collectively enable or disable a single constrained option (e.g., Product C requires both Product A and Product B). For a simple one-to-one dependency as described, populating the Option Constraint Group is not a mandatory or primary step.