Practice Free MB-310 Exam Online Questions
An organization uses Dynamics 365 for Finance and Operations.
Several posted journal entries contain invalid main account and dimension combinations. This leads to incorrect financial reporting.
You need to prevent these invalid combinations.
What should you do?
- A . Associate the correct main accounts to that financial dimension on the financial dimension setup form.
- B . Configure financial dimension sets to limit which financial dimensions are valid for which main accounts.
- C . Train users to select the Validate button in the current journal configuration so that the correct account and dimension combination is used.
- D . Configure the account structure to specify which financial dimensions are valid for which main accounts.
D
Explanation:
Reference: https://docs.microsoft.com/en-us/dynamics365/unified-operations/financials/general-ledger/configure-account-structures
A company provides employee life insurance to all full-time employees. Employee life insurance policies are paid twice a year to the insurance company. Transactions for current employees must be recognized in the general ledger twice a month with an employee’s pay. Transactions for new employees must be recognized in the general ledger based upon the employee’s first pay date.
You need to configure accrual schemes for the new fiscal year.
Which two configurations should you use? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
- A . For new employees, use a Credit accrual scheme. In the ledger accrual, set the offset to the first day of the fiscal year.
- B . For current employees, use a Credit accrual scheme. In the ledger accrual, set the offset to the employee’s first pay date.
- C . For new employees, use a Debit accrual scheme. In the ledger accrual, set the offset to the employee’s first pay date.
- D . For current employees, use a Debit accrual scheme. In the ledger accrual, set the offset to the first day of the fiscal year.
HOTSPOT
A company uses Dynamics 365 Finance.
The company requires two-way, net unit price matching for all vendors. The company also requires three-way matching for new vendors during observation periods.
You need to configure invoice matching and validation.
How should you complete the configuration? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A customer uses Dynamics 365 Finance.
The controller notices incorrect postings to the ledger entered via journal.
The system must enforce the following:
✑ Expense accounts (6000-6998) require department, division, and project with all transactions. Customer dimension is optional.
✑ Revenue accounts (4000-4999) require department and division and allow project and customer dimensions.
✑ Liability accounts (2000-2999) should not have any dimensions posted.
✑ Expense account (69 Configure an advanced rule for Expense account (6999) to require customer.
99) requires department, division, project and customer dimensions with all transactions.
You need to configure the account structure to meet the requirements.
Solution:
✑ Configure two account structures: one for liability accounts listing the (2000-2999) range with no following dimensions and one for Expense and Revenue accounts.
✑ For Expense accounts (6000-6998) and Revenue accounts (4000-4999), configure asterisks in all dimension columns.
✑ For Expense account (6999), configure asterisks in all dimensions. Co nfigure an asterisk and quotes in the customer dimension.
Does the solution meet the goal?
- A . Yes
- B . No
B
Explanation:
As asterisk in all dimension columns would mean that a value must be configured for all dimensions.
Reference: https://docs.microsoft.com/en-us/dynamics365/finance/general-ledger/configure-account-structures