Q: 1
Universal Containers has recently implemented and released CPQ to users in their production
environment. After an extensive testing Cycle in a sandboxed environment.
One of the automations implemented was to set every new quote created as "primary" at
the time of creation in order to save clicks. Users immediately began to report errors when
trying to create quotes in the production environment for the first time. What could have
caused this issue?
Options
Discussion
D . If users don't have Quote object access, any automation on quote creation will fail right away. Pretty standard permissions thing.
D it's about quote creation itself not quote lines. Open if anyone sees a case for C here.
Option D but if automation touches related child records right at creation and fails on those, it actually could be C. Depends how granular the error is or if it's failing the transaction entirely.
If users only see errors during quote creation and not after, wouldn't D be the most likely cause? Lack of Quote object access blocks creation right away, while C would be an issue after the quote is made. Am I missing something?
D imo, had something like this in a mock exam and it pointed straight to Quote object permission missing causing errors.
Its D, pretty sure. If users don’t have access to the Quote object, they’d get errors right away trying to create a quote, especially if automation is triggering on creation. I saw a similar scenario in another sandbox and wrong object permissions were always the cause. Anyone else run into this?
D , I've seen similar questions in practice sets and it always points to missing permissions on the Quote object causing this kind of issue.
D
Pretty clear it's D since if users can't create any quotes, they're lacking Quote object access. I remember seeing a similar issue flagged on another practice exam too. Correct me if I'm missing some nuance, but D seems right.
D , C is a distractor since lack of Quote object access blocks the whole creation step.
Be respectful. No spam.