Microsoft Dynamics 365 Finance Functional Consultant (MB-310) — Free Practice Questions
10 free sample questions from a bank of 377, with the correct answers and explanations. No signup required — start practising right now.
1Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet 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.
You are configuring the year-end setup in Dynamics 365 Finance.
You need to configure the year-end setup to meet the following requirements:
✑ The accounting adjustments that are received in the first quarter must be able to be posted into the previous year's Period 13.
✑ The fiscal year closing can be run again, but only the most recent closing entry will remain in the transactions.
✑ All dimensions from profit and loss must carry over into the retained earnings.
✑ All future and previous periods must have an On Hold status.
Solution:
✑ Configure General ledger parameters.
- Set the Delete close of year transactions option to Yes.
- Set the Create closing transactions during transfer option to Yes.
- Set the Fiscal year status to permanently closed option to No.
✑ Define the Year-end close template.
- Designate a retained earnings main account for each legal entity.
- Set the Financial dimensions will be used on the Opening transactions option to No.
- Set the Transfer profit and loss dimensions option to Close All.
✑ Set all prior and future Ledger periods to a status of On Hold.
Does the solution meet the goal?
Yes
No
Answer: A
The short version
A — Yes, prior-year posting stays possible with setup. Year-end config can leave the previous period open for first-quarter adjustments while current posting continues.
Key concepts in this question
Year-end setup: defines closing periods and windows for adjustment entries into the prior year
Prior-period adjustments: audit and tax corrections received early in Q1 that belong to last fiscal year
Period control: allows posting to previous period without reopening the entire closed ledger broadly
Yes and No pattern: tests whether the proposed solution meets the stated goal under Dynamics rules
Why A is correct
Dynamics 365 Finance supports posting adjustments to the prior year when year-end parameters keep that period accessible for defined users. That directly satisfies receiving Q1 adjustments into last year. Hence the solution meets the goal and Yes is settled. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
B. would deny a capability that year-end setup explicitly enables for adjustments
MB-310 exam tip
Q1 adjustments into prior year equals year-end setup allows it: answer Yes when prior period stays open for corrections. Protect closed periods and default dimensions to keep journals compliant.
2A company has implemented Dynamics 365 Finance.
The company pays taxes quarterly to the states of Florida, Nebraska, and Washington. These states have been set up as tax authorities within Dynamics 365 Finance.
You need to configure the system to remit tax payments.
What should you do?
Associate the vendor record to the tax authority.
Set up a customer record for the tax authority.
Associate the vendor record to the settlement period.
Set up the jurisdiction and associate the jurisdiction to the tax authority.
Answer: A
The short version
A — Associating the vendor to the tax authority enables remittance. Finance settles sales tax through accounts payable journals, so each tax authority must resolve to a vendor account. Linking the vendor to the authority creates that payable identity for quarterly payments to the three states. Customer records model receivables, periods control timing, and jurisdictions refine rates, but none creates the payee.
Key concepts in this question
Authority: Master record for the collector with posting groups and settlement behaviour.
Vendor link: Supplies the payables account where settlement posts and from which payment disburses.
Period: Quarterly window defines when tax is due and how it aggregates, not whom to pay.
Jurisdiction: Refines rate areas within an authority, still needing a vendor for disbursement.
Why A is correct
Remittance must know whom to pay when quarterly settlement runs. The vendor link supplies that payee, so settlement creates vendor payments in the correct amount per authority. Without it, calculated balances have no disbursement target and the process cannot complete. That dependency makes the settled step the gating action.
Why the others are wrong
B. customer models receivables collection, never a tax disbursement payee.
C. vendor to period confuses payee identity with timing and creates no authority payee.
D. jurisdiction mapping refines calculation geography without creating the vendor.
MB-310 exam tip
Tax paid out equals vendor linked to authority, tax collected equals customer logic.
3You are implementing Dynamics 365 Finance.
Subledger entries must transfer automatically to the general ledger.
You need to configure a batch transfer rule.
Which two options should you select? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point
Asynchronous
Scheduled batch
Batch jobs
Scheduler job
Answer: A, B
The short version
AB — Use Asynchronous plus Scheduled batch for auto transfer. That pairing posts subledger entries to the ledger automatically on a schedule.
Key concepts in this question
Batch transfer rules: govern how subledger journals move to general ledger without manual posting
Asynchronous mode: processes transfers in the background, freeing users during high volume
Scheduled batch: triggers recurrence so entries flow automatically at defined times
Batch jobs versus scheduler job: generic or misnamed options that do not form the transfer rule pair
Why AB is correct
Automatic GL update needs both non-blocking processing and a recurrence trigger. Asynchronous handles execution style while Scheduled batch provides timing, together meeting the automatically requirement. Other labels do not constitute the configured transfer rule. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
C. names background jobs generally but not the transfer-rule mode for auto posting
D. is not the transfer-rule scheduling construct for subledger to ledger flow
MB-310 exam tip
Auto transfer subledger to ledger equals Asynchronous plus Scheduled batch: mode plus timing, nothing else.
4A customer uses bank reconciliation functionality in Dynamics 365 Finance.
The customer finds a transaction in a closed fiscal period that must be corrected.
You need to correct the transaction.
How should you make this correction?
Use the Correction amount field.
Open the fiscal pend.
Create a new line for the transaction in the closed period.
Create a new line for the transaction in an open period.
Answer: D
The short version
D — Correct a closed-period bank line in an open period. Closed fiscal periods lock, so the fix belongs to the next open period with proper dating.
Key concepts in this question
Closed periods: prevent backdated posting to preserve audited balances
Bank reconciliation corrections: adjust via new lines rather than editing locked history
Correction amount field: useful in open contexts but cannot override period close
Reopening the period: risks audit integrity and is not the standard bank correction path
Why D is correct
Dynamics blocks new postings into closed fiscal periods to protect financial truth. Creating a correcting line in an open period with reference to the original maintains traceability while respecting close. That is the settled compliant correction method. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
A. cannot bypass period-close validation for locked dates
B. reopens history and undermines close controls unnecessarily
C. attempts to post into the closed period itself, which the system rejects
MB-310 exam tip
Closed period error equals fix in open period: never edit locked history, post a new correcting line forward.
5You are implementing Dynamics 365 Finance.
You commonly complete the sale of goods across international borders.
You need to configure the system.
What should you use?
bank statements
purchase agreement
letters of credit
promissory note
Answer: C
The short version
C — Configure letters of credit for cross-border sales. They guarantee payment via banks when goods cross international borders.
Key concepts in this question
Letters of credit: bank-issued payment undertakings triggered by compliant shipping documents
Cross-border risk: distance, customs, and currency raise nonpayment exposure for sellers
Bank statements: reconcile cash but do not secure international trade payment
Agreements and notes: define terms or promise payment without bank guarantee strength
Why C is correct
Selling across borders commonly needs a bank intermediary that pays on document compliance. Letters of credit provide that secure settlement mechanism in Dynamics trade flows. Other artifacts track cash or terms but do not mitigate international collection risk similarly. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
A. reports cash movement after the fact without guaranteeing receipt
B. sets purchase terms between parties lacking bank payment assurance
D. is an IOU without the documentary bank undertaking for trade
MB-310 exam tip
International sale plus need system setup equals letters of credit: bank-guaranteed trade payment, not statements or notes.
6The controller at a company has multiple employees who enter standard General ledger journals. The controller wants to review these journal entries before they are posted. Currently, journals entries are posted without review.
You need to configure Dynamics 365 Finance to help set up a system led review process to meet the controller s needs.
Which functionality should you configure?
an Advanced ledger entry workflow that uses the organizational hierarchy for journal posting, associated with the Advanced ledger journal name
an alert that is sent to the controller when a journal name is created
a manual journal approval with the journal assigned to the controller’s user group
the controller’s security role so that he has approval privileges for General ledger journals
Answer: A
The short version
A — Set an Advanced ledger workflow for review before posting. Hierarchy-based approval holds standard journals until the controller approves.
Key concepts in this question
Ledger workflows: route journal batches for approval based on hierarchy and policy
Organizational hierarchy: directs approvals to the right manager level automatically
Journal names: scope which journals require workflow versus direct posting
Alerts and roles: notify or permit actions but do not enforce pre-posting holds
Why A is correct
The controller needs systematic review before posting across many preparers. An Advanced ledger entry workflow tied to the journal name and hierarchy blocks posting until approval. That enforces the control without relying on manual assignment or after-the-fact alerts. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
B. only notifies on creation without preventing unreviewed posting
C. assigns manually and scales poorly compared with hierarchy workflow
D. grants privilege but does not require its use before posting
MB-310 exam tip
Review before posting for many preparers equals ledger workflow by hierarchy on the journal name.
7You are implementing Dynamics 365 Finance.
Sales tax should be calculated when the sales orders are entered. During testing, you find the sales tax is not calculating as expected.
You need to validate sales tax has been set up correctly.
Which two actions should you do? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one pint.
Validate the default item sales tax group setup for the item being sold.
Associate the sales tax jurisdiction to the item sales tax group associated to the item being sold.
Validate a default sales tax code has been set up on the customer from the sales order.
Validate the sales tax group setting on the customer from the sales order.
Validate a default item sales tax code has been set up on the item being sold.
Answer: A, D
The short version
AD — Validate item tax group and customer tax group. Sales tax calculation needs correct groups on both sides of the order line.
Key concepts in this question
Item sales tax group: links items to applicable tax codes for what is taxable
Customer sales tax group: links customers to where and how they are taxed
Intersection: Dynamics derives actual codes from the combination of both groups
Jurisdictions and default codes: support details but the primary miss is wrong group pairing
Why AD is correct
When tax fails to calculate on entry, the most common setup gap is mismatched or missing groups on item and customer. Validating the default item group plus the customer group setting confirms the intersection can resolve codes. Other checks matter later but do not establish the core calculation basis. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
B. associates jurisdiction to group incorrectly as the first validation step
C. checks a default code on customer that derives from groups rather than defining them
E. checks a default code on item instead of the governing group setup
MB-310 exam tip
No tax on sales order equals check both groups: item group plus customer group intersection decides the code.
8A company uses Dynamics 365 Finance to include multiple business units as a financial dimension.
All customer payment journals must be posted to the headquarters’ business unit financial dimension.
You need to configure the accounts receivable journal name.
What should you configure?
Journal control
Posting restriction
Default financial dimension
Journal approval
Answer: C
The short version
C — Set Default financial dimension on the journal name. That stamps every customer payment line to headquarters business unit automatically.
Key concepts in this question
Financial dimensions: business unit, cost center, and department tags for reporting
Default dimension on journal name: inherits to all lines using that journal without manual entry
Journal control and restrictions: limit accounts or amounts, not auto-populate dimensions
Approval: governs authorization, not dimension defaulting
Why C is correct
Requiring all payment journals to post to headquarters is a defaulting need, not a restriction or approval. Configuring the default dimension on the receivables journal name ensures consistent headquarters tagging. That single setup removes user error across many entries. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
A. constrains which accounts can be used, without setting business-unit values
B. blocks disallowed combinations rather than supplying the required value
D. adds authorization steps while dimensions remain manual and error-prone
MB-310 exam tip
All lines must carry same dimension equals default dimension on journal name: auto-stamp, not restrict or approve.
9A company has implemented Dynamics 365 Finance.
The company has three different banks where they hold funds. Each bank holds three separate accounts, totaling nine accounts for the company. The system must use default the bank information when a new account is created. All bank balances for a single bank account must be updated simultaneously.
You need to configure the system.
Which two entities should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
bank account
bank reasons
bank reconciliation
bank group
Answer: A, D
The short version
AD — Use bank account plus bank group entities. Accounts hold the nine balances while groups default shared bank data and update together.
Key concepts in this question
Bank account entity: master for each account with balances and setup per account
Bank group: groups accounts by bank to default information and process together
Simultaneous update: group-level handling keeps all accounts of one bank in sync
Reasons and reconciliation: explain adjustments or match statements, not defaulting structures
Why AD is correct
Nine accounts across three banks need both granular balances and shared defaults per bank. Bank account provides the per-account record while bank group supplies common bank info defaulted to new accounts and joint updating. That pair meets defaulting plus simultaneous balance logic. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
B. codes adjustment motives without creating accounts or defaults
C. matches statements to ledger but does not default bank data on creation
MB-310 exam tip
Many accounts plus default bank info plus joint update equals account plus group: detail plus shared defaults. Protect closed periods and default dimensions to keep journals compliant.
10A company uses Microsoft Dynamics 365 Finance. You are evaluating delinquent customers. You examine aging balances and determine that a customer's balance must be written off.
You need to use journal lines to perform the write-off process.
Which two journal line types will be created? Each correct answer presents part of the solution.
NOTE: Each correct selectin is worth one point.
General ledger entry
Not sufficient funds (NSF) payment entry
Customer entry
Item transaction entry
Answer: A, C
The short version
AC — Write-off creates General ledger plus Customer entries. AR settlement needs a ledger offset and a customer balance reduction together.
Key concepts in this question
Bad-debt write-off: removes uncollectible AR while recognizing expense or allowance in GL
Customer entry: reduces the customer subledger balance for the aged invoice
GL entry: posts the offset so financials balance and report correctly
NSF and item entries: handle bounced payments or inventory moves, not aging write-offs
Why AC is correct
Journal lines for customer write-off must affect both the subledger and the ledger. Customer entry clears the receivable while General ledger entry records the loss. That dual posting keeps AR aging and GL in agreement. Other line types serve different business events. This follows Microsoft Dynamics lifecycle controls that protect audited balances while allowing compliant corrections forward.
Why the others are wrong
B. reverses failed payments rather than writing off aged delinquency
D. moves inventory cost, irrelevant to AR balance relief
MB-310 exam tip
Customer balance write-off equals two lines: customer to clear AR plus GL to book the loss, always as a pair. Protect closed periods and default dimensions to keep journals compliant.