I feel pretty confident about this one. Based on the wording of the question and the options, it seems like the "Custom" value is needed when the Price Conditions involve more advanced functionality, like custom formulas or lookups. I'll mark that as my answer.
This one's got me a bit stumped. The options all sound plausible, but I'm not sure which one is the right answer. I'll have to re-read the question and options a few times to try and figure it out.
Okay, let me see if I can break this down. The "Custom" value is required when the Price Conditions are more complex, like using formulas, lookups, or a mix of AND/OR logic. I think I've got a handle on it now.
Hmm, I'm a little unsure about this one. The options all seem to be describing different scenarios, but I'm not totally clear on when the "Custom" value would be needed. I'll have to think this through carefully.
This one seems pretty straightforward. I think the key is to focus on the "Custom" value for the Condition Met field, which implies there's some special scenario where that's required.
Option C seems like the correct answer here. Combining AND/OR logic for multiple conditions would require the Custom value to handle the complex evaluation.
Blair
2 months agoShenika
2 months agoSusy
2 months agoLetha
2 months agoLili
3 months agoBobbye
3 months agoLennie
3 months agoPortia
4 months agoPura
4 months agoTwana
4 months agoJenifer
4 months agoCarma
4 months agoMariko
5 months agoLezlie
5 months agoNathan
5 months agoGolda
5 months agoKanisha
5 months agoMarge
1 month agoSusana
2 months agoPaulene
3 months agoMarvel
3 months ago