Valid Sales-Admn-202 Dumps shared by EduDump.com for Helping Passing Sales-Admn-202 Exam! EduDump.com now offer the newest Sales-Admn-202 exam dumps, the EduDump.com Sales-Admn-202 exam questions have been updated and answers have been corrected get the newest EduDump.com Sales-Admn-202 dumps with Test Engine here:
Universal Containers (UC) has a Product family called Software. When a Configuration Attribute in the bundle is set to Perpetual, UC wants to Hide all Products with the Product Family called Software. The Admin has created a Product Rule with a Configuration Rule. Which additional supporting records should the Admin configure so the Product Rule meets this requirement?
Correct Answer: B
Requirement: * Hide products with the Product Family "Software" when a Configuration Attribute is set to "Perpetual." Solution: * Use an Error Condition to evaluate the Product Family value on the Product Option record. * Configure a Product Action to Show all products except those with the Product Family "Software." Mechanism: * The Error Condition evaluates the Configuration Attribute's value against the Product Option. * The Product Action ensures visibility is dynamically controlled based on the evaluated condition. Salesforce CPQ Reference: * Error Conditions and Product Actions are key components of Product Rules in CPQ to implement dynamic product behavior .
Recent Comments (The most recent comments are at the top.)
Emi - May 03, 2026
Answer C. An Error Condition should compare the Perpetual value against the Configuration Attribute. A Product Action using the Filter Field should Hide the Products. Explanation To meet the requirement, the rule must: Trigger condition: Use an Error Condition (despite the name, it’s used in configuration rules too) to check when the Configuration Attribute = Perpetual Apply action dynamically: Use a Product Action with a Filter Field to target all products where Product Family = Software Apply Hide action to those filtered products This avoids manually listing each product and scales properly. Why not the others? A: Would require manually listing each product → not scalable B: Incorrect logic (focuses on showing instead of hiding and wrong condition) D: Missing the Configuration Attribute condition → rule would always apply
Recent Comments (The most recent comments are at the top.)
Answer
C. An Error Condition should compare the Perpetual value against the Configuration Attribute. A Product Action using the Filter Field should Hide the Products.
Explanation
To meet the requirement, the rule must:
Trigger condition:
Use an Error Condition (despite the name, it’s used in configuration rules too) to check when the Configuration Attribute = Perpetual
Apply action dynamically:
Use a Product Action with a Filter Field to target all products where Product Family = Software
Apply Hide action to those filtered products
This avoids manually listing each product and scales properly.
Why not the others?
A: Would require manually listing each product → not scalable
B: Incorrect logic (focuses on showing instead of hiding and wrong condition)
D: Missing the Configuration Attribute condition → rule would always apply