Free Microsoft MB-310 Practice Test Questions MCQs

Question 1 Analysis

Explanation:
This question addresses meal reduction configurations in expense management. When employees stay at hotels offering complimentary breakfast, companies often reduce the per diem amount to avoid duplicate reimbursement. The configuration needs to specifically target breakfast reduction while maintaining proper per diem calculations for other meals.

Correct Option:
Set Reduction in percentage for breakfast to 15.

Incorrect Options:

Set Calculate meal reduction by to Meal type per day: While this setting relates to meal calculations, it doesn't specifically address the 15% breakfast reduction requirement.

Set Meal percent to 15: This field applies to general per diem calculations, not specifically to complimentary breakfast situations.

Set Reduction in percentage for lunch and Reduction in percentage for dinner to 10: These settings affect other meals, not the complimentary breakfast scenario described.

Keep Base per diem calculation on set to Calendar day with time: This setting determines how per diem is calculated (by calendar day or by time), not meal reductions.

Reference:
Microsoft Dynamics 365 documentation on Expense management parameters and meal reduction configurations.

Question 2 Analysis

Explanation:
This question addresses per diem eligibility for partial travel days. The company wants employees to receive per diem when working at least half a day on first and last travel days. In a standard 40-hour work week, half a day equals 4 hours (based on 8-hour workdays). The configuration must specify minimum hours threshold for per diem eligibility.

Correct Option:
Set Minimum hours for per diem to 4.

Incorrect Options:

Keep Base per diem calculation on set to Calendar day with time: This setting controls calculation methodology, not minimum hour requirements for partial days. Change Per diem rounding to Always round up: This affects how per diem amounts are rounded, not eligibility thresholds.

Set Minimum hours for per diem to 4 and Other percent to 50: While the minimum hours setting is correct, adding "Other percent to 50" is unnecessary and unrelated to the half-day requirement.

Reference:
Microsoft Dynamics 365 Expense management documentation on per diem rate tiers and minimum hour configurations for partial travel days.

Question 1: Establish the currency exchange rates needed to report the total value of open Accounts receivable from Company A in Company CON.

Explanation:
This question addresses consolidation requirements where Company A (USD functional currency) needs to report to Company CON (EUR functional currency). For balance sheet accounts like Accounts Receivable, assets and liabilities must be revalued at the current exchange rate as of the reporting date. Therefore, the most recent exchange rate is needed for accurate consolidation.

Correct Option:
An imported exchange rate for EUR to USD dated yesterday

Incorrect Options:
A derived historical exchange rate for USD to EUR dated yesterday: Derived rates are calculated based on triangulation with a third currency. Additionally, the direction is incorrect (USD to EUR instead of EUR to USD for converting USD amounts to EUR).

A manually entered exchange rate for USD to EUR dated last week: Manual entry is possible but not optimal for automation. More importantly, the date is last week, not current, and assets/liabilities require current rates, not historical rates.

An imported historical exchange rate for EUR to USD dated last week: While the currency pair direction is correct (EUR to USD), the date is last week. For current revaluation of open receivables, the most recent rate (yesterday/current) is required, not a historical rate from last week.

Reference:
Microsoft Learn: Currency revaluation in General ledger and Consolidation account groups

Question 2: Create a Ledger elimination rule for intercompany transactions.

Explanation:
When creating elimination rules in Dynamics 365 Finance, the system needs to identify which legal entities participate in intercompany transactions that should be eliminated during consolidation. The "Use for financial elimination process" setting must be enabled for both the source and destination legal entities involved in intercompany transactions.

Correct Option:
Set the Use for financial elimination process to Yes for both legal entities Company A and Company B.

Incorrect Options:
Create a new legal entity and set the Use for financial elimination process to Yes: Creating a new legal entity is unnecessary for elimination processing. Elimination rules work with existing legal entities involved in intercompany transactions.

Set the Use for financial elimination process to Yes for either legal entities Company A or Company B: This is incorrect because elimination requires both entities in an intercompany transaction to be included. Setting only one entity would result in incomplete elimination of intercompany balances during consolidation.

Reference:
Microsoft Learn: Elimination rules and Intercompany accounting setup

Explanation
In Dynamics 365 Finance, revenue recognition allows you to allocate revenue from a sales order across multiple occurrences or dates. The "recognition basis" determines how the revenue amount is distributed. When allocating revenue across occurrences, you can use various calculation methods. "First of next month" is a valid recognition basis that defers the start of revenue recognition to the beginning of the following month, which is common for subscription-based billing cycles.

Correct Option

D. First of next month
This is a valid recognition basis option in Dynamics 365 Finance for allocating revenue across multiple occurrences. When selected, the revenue recognition schedule will begin on the first day of the month following the transaction date. This is commonly used for subscription services or contracts where the service period aligns with calendar months, ensuring revenue is recognized systematically across the contract term starting from the appropriate month boundary.

Incorrect Options

A. Mid-month split
This is not a standard recognition basis option in Dynamics 365 Finance. While you can configure recognition schedules with specific dates, "Mid-month split" is not a predefined recognition basis available in the system for allocating revenue across occurrences.

B. First of month
This is not a standard recognition basis option. Although "First of next month" is available, "First of month" (referring to the current month) is not a predefined recognition basis in the revenue recognition functionality.

C. Monthly by dates
This is not a valid recognition basis option. While revenue can be recognized monthly based on specific date ranges, "Monthly by dates" is not a predefined recognition basis selection in Dynamics 365 Finance. The system offers specific options like "First of next month" or allows manual date specification.

Reference:
Microsoft Learn documentation on Revenue recognition in Dynamics 365 Finance

Explanation
When creating a fixed asset in Dynamics 365 Finance, certain fields are mandatory for the system to save the record successfully. While many fields can be populated later, the asset cannot be created without specifying its fundamental identity and classification. Based on standard system setup and the question's context, the two essential settings required at the time of creation are the Fixed asset group (B) and the Name (E). The group determines default behaviors like number sequences and posting profiles, while the name identifies the asset.

Correct Option

B. the group
The Fixed asset group is a mandatory selection when creating a new asset. It serves as a template that automatically assigns default values to the asset, such as the number sequence (if group-specific), asset lifecycle model, depreciation profiles, and posting layers. The group is essential for categorizing assets and ensuring they follow the correct accounting and depreciation rules defined for that category.

E. the name
The Name field is a mandatory text field that provides a descriptive identifier for the fixed asset. While the asset number may be system-generated or manually assigned, the name is required to describe what the asset is (e.g., "Delivery Truck - 2025" or "Server Rack"). This is a fundamental data entry requirement for creating the asset record.

Incorrect Options

A. the property type
Property type is an optional classification field used in some specific reporting scenarios (like Italian localization) but is not a mandatory field for creating a fixed asset. It can be left blank or populated later without preventing asset creation.

C. the number sequence
The number sequence itself is not directly selected on the asset. The asset number is either assigned automatically based on the number sequence setup in the Fixed asset group or entered manually if the group allows. You do not select a number sequence as a property of the asset during creation.

D. the type
"Type" typically refers to the Fixed asset group. Since "Group" (B) is already listed as a separate option and is the correct classification, selecting "Type" would be redundant or incorrect as it is not a distinct mandatory field separate from the group in the standard asset creation form.

Reference

Microsoft Learn: Create a fixed asset

Microsoft Learn: Set up fixed asset groups

Explanation
When selling goods across international borders, businesses face risks related to payment security and trade compliance. Dynamics 365 Finance provides specific instruments to facilitate these transactions. Letters of credit are a standard financial instrument in international trade, acting as a guarantee from a bank that a seller will receive payment from a buyer on time and for the correct amount, provided the shipment terms are met.

Correct Option

C. letters of credit
Letters of credit are the appropriate configuration for international sales transactions. They function as a bank guarantee, mitigating risk for both the seller and buyer in cross-border trade. In Dynamics 365 Finance, you can configure letters of credit to track and manage these agreements, ensuring that shipments are only released when the letter of credit terms are satisfied and linking the sales order to the financial guarantee.

Incorrect Options

A. purchase agreement
A purchase agreement is a contract between a buyer and seller covering long-term purchasing commitments, typically for specific quantities or amounts over time. While useful for domestic and international trade, it does not provide the bank-mediated payment guarantee specifically needed for securing cross-border sales.

B. bank statements
Bank statements are used in cash and bank management to import and reconcile transactions from a company's bank accounts. They are a tool for reconciliation after payments occur, not a proactive mechanism to secure payment for international sales before shipment.

D. promissory note
A promissory note is a financial instrument where one party promises in writing to pay a sum of money to another party at a specified future date. While used in some commercial transactions, it is not the primary instrument for guaranteeing payment in international goods sales, where letters of credit are the standard.

Reference
Microsoft Learn: Letters of credit and import collections

Explanation
Budget control in Dynamics 365 Finance allows organizations to manage spending by enforcing budget limits at various levels. The configuration includes setting "Over budget permissions" (how strictly budget is enforced), "Message levels" (what type of warning users receive), and "Budget funds available" (which calculation determines available budget). Each department's settings must align with their specific business rules.

Operations

Correct Option:
Over budget permissions - Set to Warn only

Explanation:
Operations must be allowed to exceed budget, which requires the most permissive setting. "Warn only" allows users to proceed with transactions that exceed available budget while receiving a warning message. This satisfies the requirement that Operations can exceed budget without being blocked.

Incorrect Options:

Message levels: This setting controls the verbosity of messages, not whether exceeding budget is permitted.

Budget funds available: This determines the calculation method for available funds, not whether overspending is allowed.

Budget reservations for encumbrances/pre-encumbrances: These settings control budget tracking for purchase orders and requisitions, not overspending permissions.

Marketing

Correct Option:
Message levels - Set to Warning

Explanation:
Marketing must receive warnings when approaching or exceeding budget. "Warning" message level ensures users are notified when budget thresholds are reached or exceeded, meeting the requirement that Marketing receives appropriate budget warnings.

Incorrect Options:

Over budget permissions: This setting would either block or allow overspending, not specifically provide warnings as required.

Budget funds available: This determines the calculation method, not the warning mechanism.

Budget reservations: These settings control encumbrance tracking, not warning messages.

Sales

Correct Option:
Over budget permissions - Set to Block

Explanation:
Sales must not exceed its budget, which requires the most restrictive setting. "Block" prevents users from posting transactions that would exceed available budget, ensuring Sales stays within allocated amounts.

Incorrect Options:

Message levels: This only controls notifications but would still allow overspending.

Budget funds available: This determines the calculation method, not enforcement.

Budget reservations: These settings control tracking, not spending limits.

All Departments

Correct Option:
Budget funds available - Set to Actual expenditures only

Explanation:
All departments need a calculation in place to determine what they can spend. Since budget funds do not need to be recorded in the general ledger, "Actual expenditures only" calculates available budget based on actual spending without requiring encumbrance or pre-encumbrance tracking in the general ledger.

Incorrect Options:

Over budget permissions: This setting controls enforcement, not the calculation method.

Message levels: This controls notifications, not fund availability calculation.

Budget reservations for encumbrances/pre-encumbrances: These would require recording budget reservations in the general ledger, which contradicts the requirement that budget funds do not need to be recorded there.

Reference

Microsoft Learn: Budget control overview and configuration

Microsoft Learn: Set up budget control

Explanation
This question tests the understanding of account structure configuration in Dynamics 365 Finance, specifically how to enforce dimension requirements using asterisks (*) and quotes ("") in the account structure designer. Asterisks indicate a required segment, while quotes indicate a blank/allowed segment. The requirements specify different dimension rules for different account ranges, which must be precisely configured.

Correct Option

B. No
The solution does not meet the goals for several reasons. First, the requirements state that Expense accounts (6000-6998) require department, division, and project with all transactions, with customer dimension optional. However, the solution configures "asterisks in all dimension columns" for these accounts, which would make customer dimension required, not optional. Second, for Revenue accounts (4000-4999), project and customer dimensions should be allowed but not required, yet asterisks would make them required. Third, for Expense account (6999), customer dimension should be required, but the solution incorrectly applies quotes to customer dimension, making it optional.

Incorrect Logic in the Solution

Account Structure Design
The solution correctly identifies the need for two separate account structures: one for liability accounts with no dimensions, and one combining Expense and Revenue accounts. This part is appropriate.

Dimension Configuration for Expense (6000-6998) and Revenue (4000-4999)
The solution fails by using asterisks for all dimensions on these accounts. Asterisks make a dimension mandatory. The requirements specify:

Expense accounts (6000-6998): Department, division, project required; customer optional → Requires a mix of asterisks and quotes

Revenue accounts (4000-4999): Department, division required; project and customer optional → Requires asterisks for department/division, quotes for project/customer

Dimension Configuration for Expense Account (6999)
The solution incorrectly applies quotes to the customer dimension. The requirement specifies that Expense account 6999 requires department, division, project, AND customer dimensions with all transactions. Therefore, customer dimension should have an asterisk, not quotes.

Reference

Microsoft Learn: Create and maintain account structures

Microsoft Learn: Define advanced rules for account structures

Microsoft Learn: Configure required and allowed dimensions in account structures

Explanation
This question addresses credit limit enforcement in Dynamics 365 Finance. When managing credit and collections, companies need to ensure that credit limits are enforced consistently across all customer transactions. The solution involves configuring individual customer records with specific credit limits and enabling mandatory checking to prevent transactions that would exceed approved credit amounts.

Correct Option

B. Yes
The solution meets the goal. Defining a credit limit for each customer establishes the maximum credit amount they are authorized to use. Selecting the "Mandatory credit limit" check box on the Customers form activates the system's credit limit enforcement, which will then block or warn users when transactions would cause the customer to exceed their established credit limit. These two settings together create the required mandatory credit limit control across all customer documents.

How the Solution Works

Define a credit limit for each customer
This establishes the specific maximum credit amount for each customer. Without a defined limit, there would be no basis for enforcement. The credit limit can be set in the customer record under credit and collections parameters.

Select Mandatory credit limit check box
This global setting activates credit limit enforcement across the system. When enabled, Dynamics 365 Finance will check every transaction against the customer's credit limit and take action (block or warn) based on additional configuration settings. This ensures all customer documents are subject to credit limit validation.

Reference
Microsoft Learn: Set up credit and collections parameters

Microsoft Learn: Credit limit enforcement in Accounts receivable

Explanation
This question addresses revenue recognition for a manufacturing company that has both performance obligations (manufacturing, shipping, installation) and a separate three-year warranty. The payment schedule (25% at sale, 50% at shipment, 25% at installation) represents milestone billing, not necessarily revenue recognition timing. Revenue must be recognized based on when performance obligations are satisfied, not when payments are received.

Correct Option

C. Create the revenue schedule so that it uses the contract terms
This is the correct approach. The revenue schedule should be based on the underlying contract terms that define when revenue is earned, not simply when payments are received. For the air filtering units, revenue should be recognized as each performance obligation is satisfied (manufacturing/shipment and installation). The three-year warranty represents a separate performance obligation whose revenue should be recognized ratably over the warranty period. Creating a schedule based on contract terms ensures proper alignment with accounting standards.

Incorrect Options

A. Create a reallocation posting for the warranty revenue.
Reallocation posting is not the primary mechanism for setting up revenue recognition. While revenue may need to be allocated between the unit and the warranty, creating a proper revenue schedule is the first step. Reallocation would occur after the initial setup, not as the solution itself.

B. Create a new revenue schedule for each unit.
While each unit might have its own schedule, this option misses the key requirement of aligning with contract terms. The question asks what you should do generally, and the correct principle is to base schedules on contract terms, not simply create individual schedules without guidance on their structure.

D. Create one revenue schedule with milestones.
Milestone-based revenue recognition might apply to the installation phase, but this option doesn't address the warranty component or ensure alignment with contract terms. A single milestone schedule would not properly account for the three-year warranty that requires recognition over time.

Reference

Microsoft Learn: Revenue recognition overview

Microsoft Learn: Create revenue schedules