A company uses Revenue Cloud to sell complex product bundles that include subscriptions, add-ons, and...

Product compatibility is a configuration-time concern and should therefore be implemented within Product Configurator using configuration rules or constraint models. Salesforce ' s Constraint Rules Engine is designed for large and complex product configurations and supports rules such as require, exclude, conditional logic, message, and hide/disable rules.

This allows invalid configurations to be prevented or corrected while the sales rep is actively configuring the bundle. For example, an exclusion constraint can prevent two incompatible options from appearing together, while a require rule can automatically enforce a dependency. This produces immediate feedback and avoids introducing invalid configurations into downstream pricing, contracting, ordering, or fulfillment processes.

Option A operates too late. A Quote validation rule evaluates record-level persistence rather than providing a rich, configuration-aware dependency engine across product components. Option C is even later because quote approval occurs after the product-selection process and turns configuration errors into downstream rework.

The Revenue Management Consultant preparation trail explicitly includes Product Configuration as a core CPQ competency, emphasizing validation of products during selection.

Study Guide Reference:Configure, Price, Quote — Product Configuration with Agentforce Revenue Management; Constraint Rules Engine; product compatibility.

===============