Q: 11
Which three documents help a revenue cloud consultant better understand the client’s Revenue Cloud Project requirements before speakingfor the first time in a scopingsession?
Options
Discussion
A. B, D imo. Those three give a good picture of how the client actually does business, what they sell, and their quoting/approval process. C is just system release updates, not about scoping project requirements. Pretty sure this lines up with official guidance.
Nah, not C. It's A, B and D since those show what the client provides, their quoting style, and required approvals. Patch notes (C) are more system-side, that's the trap here if you skim too fast. Saw similar in practice sets. Anyone disagree?
Probably A , B, D. Not 100 percent but that's what aligns with pre-scoping discovery.
Man, Salesforce questions always throw in at least one totally useless doc like C. A, B, D tbh.
Yeah, it's gotta be A, B, D for this one.
A/B/D. Those cover what the client sells, how they present it, and their internal approval process. C and E don't really help with scoping requirements for Revenue Cloud. Seems like the obvious pick here, but open to pushback.
A B, D tbh. Patch notes in C are tempting but not focused on requirement discovery for scoping sessions.
I don’t think it’s C. A, B, D make more sense since they show what the client sells and how they run approvals before quoting. Patch notes are confusing here but not really about client requirements for scoping. Pretty sure on this set.
E
A/B/D? If the client's Revenue Cloud requirements were all about system updates or Salesforce config, C could maybe bump D out. But since it's focused on understanding the client's own business and approval processes before scoping, D fits better. Unless 'requirements' here secretly means something technical, pretty sure A, B, D are what they want. Anyone seen a version where C was right?
Be respectful. No spam.