A sales representative should be able to Inform a customer before adding a sales order, if the order exceeds their credit limit. Additionally the sales manager wants to be notified when a credit…

Question

Options

• AActivate the credit deviation alert with the sales manager as the recipient.
• BEnable credit limit restrictions on sales orders in the general settings.
• CDefine a user alert with a query to check the sales order value against the credit limit.
• DSet up an approval process for credit deviation with the sales manager as the approver.

• A
  17% (8)
• B
  73% (35)
• D
  10% (5)

Explanation

Enabling credit limit restrictions in general settings (B) activates a built-in warning that alerts the sales representative at the point of order entry when a customer's credit limit would be exceeded, directly satisfying the "inform before adding" requirement. A user-defined alert with a query (C) can independently monitor sales order values against credit limits and automatically send a notification to the sales manager, satisfying the second requirement without blocking the transaction.

Why A is wrong: There is no standard "credit deviation alert" feature with a recipient field - alerts for this scenario must be configured manually as user-defined alerts (which is what C describes). A is essentially a distractor that borrows language from both B and C.

Why D is wrong: An approval process blocks the sales order from being saved until the manager approves it - this is more restrictive than simply notifying the manager. The requirement says "notify," not "require approval before proceeding."

Memory tip: Split the two requirements: "inform the rep" = a system setting that throws a warning at entry (B), and "notify the manager" = a background alert triggered by a query (C). One is a gate, the other is a message - two different tools for two different people.

No community discussion yet for this question.