A consultant is extending the Sales Order Agent for a distributor whose policy requires any order with a line-item discount greater than 15% to be approved by a sales manager before the order is created in Dynamics 365 Sales. The Sales Order Agent currently creates orders directly from parsed purchase orders without any approval step. What should the consultant configure?
Select an answer to reveal the explanation.
Short Explanation
Whenever a business rule says this needs a human's sign-off before it goes through, the fix is to build an actual approval step into the process — check the condition that matters, then route it to the right person and wait for their decision before letting the record get created. That is the only option here that pauses for a real yes or no from a manager. Refusing the order outright and bouncing it back to the customer goes way further than the policy asks for. A rule that simply blocks saving anything over the threshold does not pause for approval at all — it just permanently stops the record, even ones a manager would have happily approved. And leaning on a setting meant to flag messy, hard-to-read documents has nothing to do with how big a discount is, so it would miss the exact orders that actually need review.
Full Explanation
The correct answer is B. The distributor's policy requires manager approval before any order with a discount above 15% is created in Dynamics 365, so the order-processing flow behind the Sales Order Agent needs a condition that checks the discount and an approval action that routes qualifying orders to a manager, holding creation until that approval is granted. Option A is incorrect because outright rejecting high-discount purchase orders and asking the customer to resubmit contradicts the policy, which calls for manager review and approval, not automatic refusal of legitimate orders. Option C is incorrect because a business rule that blocks saving records above the threshold prevents the order from being created at all rather than pausing it for approval, so it does not implement an approval workflow and would cause valid, later-approved orders to fail. Option D is incorrect because the agent's confidence threshold setting reflects how accurately it parsed the purchase order document, which is unrelated to the discount percentage; assuming high-discount orders naturally produce low parsing confidence is an unfounded assumption that would leave most high-discount orders unflagged.