Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft MB-310 Exam - Topic 5 Question 49 Discussion

Actual exam question for Microsoft's MB-310 exam
Question #: 49
Topic #: 5
[All MB-310 Questions]

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 (6999) requires department, division, project and customer dimensions with all transactions.

You need to configure the account structure to meet the requirements.

Solution:

Configure one account structure with department, division, project and customer dimensions.

Configure asterisks in all columns for Expense accounts (6000-6999), Revenue accounts (4000-4999), and Liability accounts (2000-2999).

Does the solution meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: B

As asterisk in all dimension columns would mean that a value must be configured for all dimensions.


https://docs.microsoft.com/en-us/dynamics365/finance/general-ledger/configure-account-structures

Contribute your Thoughts:

0/2000 characters
Jesus
6 months ago
I doubt this will work as intended; it feels too generic.
upvoted 0 times
...
France
6 months ago
Asterisks for everything? That sounds overly complicated.
upvoted 0 times
...
Gretchen
6 months ago
Wait, so all accounts get the same structure? That seems off.
upvoted 0 times
...
Yolando
6 months ago
Totally agree, it misses the mark on liability accounts!
upvoted 0 times
...
Letha
6 months ago
The solution doesn't enforce the specific requirements for each account type.
upvoted 0 times
...
Sanda
7 months ago
From what I studied, each account type has unique dimension requirements, so I feel like this solution oversimplifies it.
upvoted 0 times
...
Mee
7 months ago
I'm a bit uncertain about the asterisks for all columns; it seems like it could lead to incorrect postings for liability accounts.
upvoted 0 times
...
Nohemi
7 months ago
I remember a similar practice question where we had to configure dimensions based on account types, and it was crucial to follow those specific rules.
upvoted 0 times
...
Deeanna
7 months ago
I think the solution might not meet the goal because it doesn't specify the requirement for liability accounts to have no dimensions.
upvoted 0 times
...
Janey
7 months ago
I'm a bit confused by the wording of this question. What exactly do they mean by "foe failures and future mishaps"? I want to make sure I understand the context before I choose an answer.
upvoted 0 times
...
Wilson
7 months ago
I'm leaning towards Demand Forecasting and Purchase Requisitions. Forecasting demand is key, and then using purchase requisitions to initiate the purchasing process seems like it would fit the requirement of "determining when to purchase new inventory."
upvoted 0 times
...

Save Cancel