In Salesforce CPQ, importing data for products and bundles requires a specific order to ensure referential integrity, as certain objects depend on others being present. The correct sequence starts with the Product (the parent record), followed by Product Features (defining sections or categories within the bundle), Product Options (specific selectable items under features), Option Constraints (rules governing option selections), and finally Configuration Attributes (additional settings for dynamic configuration). Option A reflects this hierarchical dependency accurately.

To update Product Option B's quantity in real time when Product Option A is selected, a Price Rule must trigger dynamically in the configurator. Option A sets the Evaluation Scope to "Configurator" (for real-time updates during configuration), the Configurator Evaluation Event to "Edit" (triggering when edits occur), and
"Apply Immediately" on Product Option B (ensuring its quantity updates instantly). Option B (Calculator scope) applies during price calculation, not real-time configuration. Option C targets Product Option A's immediacy, but the rule must affect B's quantity. Option D combines Calculator scope with A's immediacy, missing the real-time configurator need. Salesforce CPQ documentation supports Configurator scope for real- time updates.
References: Salesforce CPQ Documentation - "Price Rules" and "Configurator Events".

Requirement:
* A unique license number needs to be stored on the Asset record for each unit of a downloadable product sold.
Solution:
* Setting the Asset Conversion field to One per Unit ensures that an individual Asset record is created for each unit of the product. This allows each Asset to store a unique license number.
Why Other Options Are Incorrect:
* A & B: Null or custom values do not enforce one Asset per unit, making it impossible to assign unique license numbers.
* D: One per Quote Line creates only one Asset for the entire Quote Line, which is not suitable for unit- level licensing.
Salesforce CPQ Reference:
* The behavior of Asset Conversion is detailed in CPQ Asset Configuration documentation .

Requirement:
* Allow users to choose options and define quantities during bundle configuration.
Configuration Types:
* None (A): Users can freely choose options and set quantities.
* Allowed (C): Users can choose options and optionally set quantities.
* Required (E): Users must configure the options and define quantities.
Why Other Options Are Incorrect:
* B: Configurable is not a valid value for the Configuration Type field.
* D: Disabled prevents any configuration, which contradicts the requirement.
Salesforce CPQ Reference:
* Configuration Types are documented under Bundle Configuration Guidelines .

Potential Causes:
Component Checkbox: Products marked as Components are typically excluded from being directly selectable in the Product Selection screen unless part of a bundle . Search Filter: Custom Search Filters on the Add Products button limit the display of products based on criteria such as product attributes or field values.
Excluded Reasons:
Hidden Checkbox: This is generally used to hide products from the Quote Line Editor, not the Product Selection screen.
Custom Action Condition: While these can limit the Add Products button's visibility, they do not directly affect individual product visibility.