Free Microsoft MB-800 Practice Exam with Questions & Answers

In Dynamics 365 Business Central, deletion of general ledger (G/L) accounts is restricted if the Check G/L Account Usage field is enabled in General Ledger Setup. This setting ensures data integrity by preventing the removal of accounts that are actively referenced in posting groups, posting setups, or transactions.

Requirements for deletion:

The G/L account must not be used in posting groups (such as customer, vendor, bank, or inventory posting groups).

The G/L account must not be used in posting setup tables (like VAT posting setup or general posting setup).

The account must not have existing ledger entries.

Why not the others:

B. The fiscal year needs to be closed: Not a requirement for deleting an account.

C. The G/L account must be Balance Sheet type: Deletions are not restricted by account type.

D. Allowing deletion is not a field option on the account card.

Comprehensive Detailed Explanation

In Business Central, financial reporting is built from several components:

Row definition

Used to define which accounts or statistical accounts appear as rows in the financial report.

Since Headcount and Square Footage are statistical accounts (non-financial data tracked for reporting), they must be added via Row definition.

G/L account categories

Used to structure the income statement and balance sheet into financial categories such as Income, COGS, Assets, Liabilities.

The requirement states: “The financial report structure must map to account categories.”

Therefore, Income, Retail must be configured using G/L account categories.

Financial Report page

Used to assemble and present the report, combining row definitions, column definitions, and filters.

Accounts Receivables, Wholesale is a financial reporting output that must be displayed using the Financial Report page where the actual data is gathered.

Why not Column definition?

Column definitions control time periods (month, quarter, year, variance, etc.) but are not needed for these particular requirements.

Microsoft Learn references

Financial Reporting in Business Central

Set Up Row and Column Definitions

G/L Account Categories

Comprehensive Detailed Explanation

The Copy Company function in Business Central duplicates all data (setup, master data, historical entries, transactions) from one company to another within the same environment.

It is used for creating a sandbox/test company or making a copy of a live company, not for importing opening balances.

Since the requirement is to transfer only opening balances, this method does not meet the goal.

Comprehensive Detailed Explanation

When posting a partial shipment in Microsoft Dynamics 365 Business Central, you must adjust the "Qty. to Ship" field on the sales order line before posting. Here’s why the sequence is correct:

Select the sales order

You must open the correct sales order that you want to process.

Set the Qty. To Ship to 50

Since the sales order originally has a quantity of 100, and only 50 should be shipped now, you must update the "Qty. to Ship" field to 50. This allows partial shipment.

Choose the Ship option

This tells the system that you are performing a shipment action (not invoicing yet).

Select the Post action

Finally, post the shipment so the 50 units are shipped, and the remaining 50 stay open on the sales order for future fulfillment.

Why not the other actions:

Set the Quantity to 50 → Incorrect field; must use Qty. to Ship for partial shipment.

Select the Post Batch option → Used for batch posting, not relevant for a single manual shipment.

Select Ship and Invoice → Would post both shipment and invoice at the same time; requirement was to post shipment only.

Microsoft Learn References

Post Sales Shipments

Partial Shipments and Invoicing

You are setting up a G/L account for a bank checking account in the chart of accounts. Let’s break down each field:

Income/Balance → Must be Balance Sheet

Bank accounts represent assets (cash) and always belong to the Balance Sheet.

If you select Income Statement, it would be treated as a P&L account, which is incorrect.

Account Category → Must be Assets

Within the Balance Sheet, checking accounts are part of current assets.

Choosing Assets ensures correct financial reporting under Assets.

Account Type → No Code

Account Type is typically used for special accounts like Begin-Total, End-Total, or Heading.

A checking account is a posting account, so you should leave No Code, meaning it's a normal posting account.

Direct Posting → Enabled

For bank accounts, direct posting must be enabled so that you can post transactions (like payments, deposits) directly against this G/L account.

If it were disabled, only system processes could post to it, which is not desired here.

Microsoft Learn References:

Design Details - Chart of Accounts

Set Up General Ledger Accounts

Account Categories

In Business Central, when you want to import master data (like customers, vendors, items, etc.) using configuration packages, you follow a structured sequence:

Create a configuration package – First, you define the configuration package and select the related tables to be imported.

Export an Excel template and populate the data – Once the package is created, you export the template to Excel. This gives you the correct structure (fields, columns) that match Business Central. Then you (or the customer) fill in the Excel file with the master data.

Import a populated Excel template into the package data – You then import the filled-in Excel file back into the configuration package in Business Central.

Apply the data – Finally, after validation, you apply the data so it is committed to the database tables of the new company.

Why not the others?

Export a configuration package is used to share configuration setups with another environment, not part of this workflow.

Import a populated Excel template into the sales header and lines is only for document data (transactions), not master data imports via configuration packages.

Explanation

The Report Selection - Purchase page is used to define which report layout to use when printing purchase documents (orders, invoices, credit memos).

It does not affect the document line defaults such as automatically setting the Type field.

Thus, this solution also does not meet the requirement.

Comprehensive Detailed Explanation

In Microsoft Dynamics 365 Business Central, when a user mistakenly applies multiple payments incorrectly, you need to correct the customer payment application using the Unapply Entries functionality.

Step 1: Navigate to Unapply Entries from the relevant customer ledger entry.This is the starting point. You open the customer ledger entries for the specific transaction and select the entry where the wrong payment application was done.

Step 2: Unapply the first payment.Since the requirement is to remove the first cash receipt, you must unapply that specific payment. Business Central will then restore both the invoice and payment as open.

Step 3: Apply the second payment to the customer ledger entry.Because the second payment was still partly applied, you reapply it to ensure the invoice is still matched with the correct payment. This keeps your receivables accurate.

Step 4: Post a reversing cash receipt and select the customer and relevant payment entry.After unapplying and reapplying correctly, you may need to post a reversing cash receipt to completely clear the incorrect transaction from the customer account if an additional entry was created by mistake. This ensures that the general ledger and customer ledger entries remain aligned.

Thus, this sequence ensures the mistake is corrected without leaving residual incorrect entries in the ledger.

Microsoft Documentation References

Unapply Customer Ledger Entries in Business Central

Correct or Cancel Customer Payments

Apply and Unapply Customer Payments

Business Central Functional Consultant at end of each question below

The requirement is:

Purchasing agents must create and post purchase documents (which requires permissions to vendors, purchase headers/lines, posting routines).

They must be restricted from viewing General Ledger (G/L) balances and amounts.

They must still be able to select G/L accounts when coding purchase lines.

In Business Central, this scenario is solved by using Permission Sets with Security Filters:

Assign a Permission Set to the User

The purchasing agent must first be assigned a permission set (e.g., PURCHASER, or a custom one cloned from SUPER with reduced rights).

This ensures they have access to vendors, purchases, and posting processes.

Select the Permission Set to Modify

You then open the permission set (or copy/create a new one for Purchasing Agents).

Modify it to apply restrictions specifically for the G/L Account table.

Apply Security Filters on the G/L Account Table

Locate the G/L Account table within the permission set.

In the Security Filter column, choose the field Income/Balance.

Set the Filter Value to Income only (or exclude Balance).

Alternatively, set the filter on Direct Posting = Yes, ensuring they can pick accounts but not see balances.

This filter prevents access to balance-related fields, effectively hiding financial values from the user while allowing them to still select G/L codes for posting.

Thus, the correct sequence to meet the requirements is:

Assign a permission set to a user

Select the permissions set you want to modify

In the row for G/L account table, select the Security Filter column

In the Field Filter column, set the value to hide balances

Microsoft Learn References

Security Filters (how to restrict data visibility by table fields):https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/security/security-filters

Assign Permission Sets to Users:https://learn.microsoft.com/en-us/dynamics365/business-central/ui-define-granular-permissions

Create and Modify Permission Sets:https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/security/how-to-create-permission-sets

In Dynamics 365 Business Central, every item must have a Base Unit of Measure. This is typically the smallest unit in which you transact or track inventory.

The requirement states the company “refers to the items as pieces,” so Pieces must be the base unit of measure.

A Box = 12 pieces, a Pallet = 144 pieces.

When creating item units of measure, you set Quantity per Unit of Measure relative to the base unit.

Base Unit: Piece (Qty. per Unit = 1)

Box: Qty. per Unit = 12

Pallet: Qty. per Unit = 144

This way, Business Central can automatically convert quantities when selling in boxes, pallets, or pieces.

Why not others?

A: Incorrect → Box cannot be the base if pieces are the standard reference.

B: Incorrect → Pallet as base unit with pieces as 0.0069 is not practical and makes transactions confusing.

D: Incorrect → Pallet as base unit with Box as fraction (0.08333) again introduces complexity.