A Revenue Cloud Consultant needs to create a dynamic product bundle where the available options...

Acontext-aware Constraint Modelis appropriate because the configuration behavior depends on data outside the product itself—the Industry field on the parent Opportunity. Revenue Management Context Service can make transactional and related-record information available to configuration logic, allowing constraints to evaluate external context while users configure the bundle.

The consultant can therefore define rules that use Opportunity Industry to control eligible components, require or exclude products, determine default selections, or set supported attribute values. This keeps configuration logic within Product Configurator and ensures the correct behavior is evaluated at configuration time.

Option A executes too late. A before-save Quote flow can detect an invalid transaction when Salesforce attempts to save it, but it cannot provide the same dynamic configuration experience while the sales rep chooses bundle components. Option B describes Product Configuration Rules too broadly and assumes direct Opportunity-field processing in a way that does not reflect the context-aware constraint architecture required by the scenario.

The critical concept is that Context Service supplies external transaction context and the Constraint Model consumes that context to influence product configuration.

Study Guide Reference:Configure, Price, Quote — Product Configurator; Context Service; context-aware constraint models; dynamic bundle configuration.

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