Requirement Overview:
Each sales team needs access to a specific subset of products without requiring separate Price Books.
Solution:
Use multiple bundles with validation Product Rules to restrict access to specific products based on user criteria (e.g., Profile or custom field).
This avoids the need to create and manage separate Price Books for each team.
Steps to Configure:
Create a bundle for each subset of products.
Use Product Rules to validate and restrict access based on sales team criteria.
Validation:
Test the Product Selection page to ensure that each sales team can access only their specific subset of products.

CPQ Price Calculation Sequence:
* The Regular Price is calculated as part of the price waterfall, and several factors influence it.
Key Contributors:
* Prorate Multiplier: Adjusts prices for subscription products based on term alignment.
* Contracted Price: Overrides the List Price for specific customers.
* Discount Schedules: Apply volume or tiered discounts during price calculation.
Why Other Options Are Incorrect:
* A: Additional Discount Fields apply after Regular Price is calculated.
* D: Target Customer Amount is used in quoting, not directly in Regular Price calculation.
Salesforce CPQ Reference:
* Price waterfall and Regular Price contributors are detailed in CPQ Pricing Configuration .

Requirement:
Deploy Price Rules with Lookup Queries that reference a new Rental Rates object.
Best Practices for Deployment Order:
Step 1: Rental Rates: Deploy the object and data it references first to ensure lookup data is available.
Step 2: Price Rules: Deploy Price Rules to establish the logic governing pricing calculations.
Step 3: Price Conditions: These evaluate criteria for the rules to execute.
Step 4: Lookup Queries: Queries must reference both the object and conditions, so deploy them after both.
Step 5: Price Actions: Set last to ensure that the actions triggered by the rules execute correctly.

Requirement:
* Restrict the products visible during the configuration of a dynamic bundle.
Solution:
* Use a Default Filter in a Product Rule. This ensures only the specified set of products is displayed in the configurator for the dynamic bundle.
Why Other Options Are Incorrect:
* A: Optional filter is not a valid Product Action.
* B: The Show action determines visibility but does not enforce restrictions on selections dynamically.
* D: Enable action is used to activate a previously disabled product but does not filter selections.
Salesforce CPQ Reference:
* Dynamic bundles and filtering actions are detailed in CPQ Product Rule Configuration Guidelines .

Requirement Overview:
When renewing Contracts with Premier Support, it must automatically be replaced with Premier Pro.
Solution:
The Renewal Product field on the Product record allows admins to specify a replacement Product for renewals.
Steps to Configure:
Navigate to the Premier Support Product record.
Populate the Renewal Product field with Premier Pro.
Save and test the renewal process to confirm Premier Pro replaces Premier Support on the Quote.
Validation:
Ensure all renewal Quotes replace Premier Support with Premier Pro automatically.