Q: 7
A product administrator creates a product by associating it with a product class that has three
attributes assigned. Two of these attributes are to be used for attribute-based pricing only for this
product.
How should the product administrator ensure that these two attributes can be used for attribute-
based pricing?
Options
Discussion
Makes sense to go with C for this. The question wants the price impacting attributes to work only for one product, not for all products in the class. If you edited at the attribute or class level (A or B), every product using that class would get the change, which might mess up other pricing scenarios. Unless there’s some custom logic overriding this, C matches what the platform supports. Always worth checking if attribute inheritance is customized though!
C . Editing the inherited attributes at the product level means you can mark those two as price impacting just for this product, not all products in the class. A and B would change things for every product using that class, which isn't needed here.
Probably C. That's the only way to flag price-impacting for just this product without changing all products in the class.
Probably C for this since it's about just one product, not the whole class.
I don’t think B is right here. C matches since you only want the price impact for this one product, not all products tied to the class. B would trigger it everywhere, that’s the trap.
B for me. Setting 'Is Price Impacting' at the attribute definition should work, since that controls its impact overall. Maybe I'm missing something about inheritance levels-someone correct me if that's off.
C vs B for me. Had something like this in a mock and it wanted you to set 'Is Price Impacting' just at the product level, not globally via attribute or class. So I'm picking C, but if the question was about all products, B would fit.
C tbh. You want the attribute-based pricing to affect just this single product, not all products inheriting from the class. If you use A or B, the 'Is Price Impacting' flag would apply to every product linked to that class, which could mess up other pricing. Pretty sure C isolates it like the scenario wants. Let me know if I’m missing something.
Be respectful. No spam.
