Exam Rev-Con-201 Topic 2 Question 156 Discussion

Explanation (150-250 words)
In Salesforce CPQ, Constraint Models define validation, inclusion, and compatibility rules that control product configuration behavior. When a validation or warning depends on an attribute value of a single product, the logic should be defined at the Product Level Constraint Model.
In this scenario, the "Terabyte" attribute belongs to "Product A," and the business rule requires displaying a warning message when the attribute exceeds 100. Implementing this at the Product Level Constraint Model ensures that the rule evaluates only that product's context and triggers the message directly within the configuration page when users input the attribute value.
Quote-level constraint models are used for cross-product validations across multiple quote lines, not for product-specific attribute conditions. Therefore, option C correctly uses the Product Level Constraint Model
.
Exact Extract from Salesforce CPQ Implementation Guide:
"Use Product Level Constraint Models when the validation logic applies to a specific product's attributes or options. Use Quote Level models when the logic involves multiple products or quote lines." References:
Salesforce CPQ Implementation Guide - Constraint Models and Rule Hierarchies Salesforce Revenue Cloud Developer Guide - Product-Level Attribute Validation Salesforce CPQ Best Practices - Warning Messages and Validation Rules in Configuration