MB-310 Practice Question: Implement and Manage Accounts Payable and Expenses
Exhibit
{
"policy_name": "VendorInvoicePolicy",
"rule_type": "InvoiceTotal",
"threshold": "100.00",
"action": "Warn",
"enforce_on": "PO_Invoices"
}Refer to the exhibit. An accountant reports that they are still able to post invoices exceeding $100.00 without being blocked. Based on the provided policy JSON, why is this occurring?
⚠ Common exam trap
Candidates often assume that any policy violation automatically stops a process, failing to realize that 'Warn' is a notification-only status that allows users to proceed despite the system warning.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The action is set to 'Warn', which allows users to bypass the validation.
The policy action is configured as 'Warn' rather than 'Reject' or 'Block'. In Dynamics 365 Finance, a 'Warn' action displays a notification to the user but does not prevent the document from being saved or posted. To stop the transaction entirely, the policy action must be updated to a restrictive level, ensuring strict adherence to the defined financial threshold and preventing manual overrides.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The rule_type is set to InvoiceTotal instead of LineItem.
Why it's wrong here
The rule type InvoiceTotal is valid for controlling the total document value. Changing this to LineItem would change the scope of the rule, but it would not address the fact that the current action is merely a warning, allowing users to proceed regardless of the total amount.
- ✗
The enforce_on field is missing the 'Journal_Invoices' parameter.
Why it's wrong here
Enforcing the rule on journal invoices is separate from PO invoices. Even if the parameter were added, the underlying issue is the 'Warn' action, which allows the post to proceed. Adding more enforcement targets will not change the behavior of the warning mechanism already in place.
- ✓
The action is set to 'Warn', which allows users to bypass the validation.
Why this is correct
The 'Warn' action generates a soft validation that does not stop the posting process. For strict compliance, the system requires a hard-block configuration. This distinction is vital for functional consultants, as it allows for flexible business operations while still providing visibility into potential deviations from standard purchasing policies.
- ✗
The threshold value is a string, which causes the rule to be ignored.
Why it's wrong here
In many configuration contexts, numeric strings are parsed as decimals. The failure to block is not due to the data type, but rather the logical configuration of the action. Even if the threshold were parsed correctly as 100.00, the 'Warn' status remains the primary reason for the behavior.
About these practice questions
Courseiva writes every MB-310 question from scratch — 211 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This MB-310 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-310 exam.