Free MB-800 practice test: 30 questions with answers

A company in Business Central is a separate set of books within the same environment, with its own chart of accounts and fiscal settings. Dimensions tag transactions, item categories group products, and locations track stock places.

Copying a company or using configuration packages carries the standard setup forward, which reduces errors. Manual typing is slow, a customer list does not include the setup, and sharing a database user is not a configuration method.

Permission sets define what each user can read, create, modify and post in Business Central, which enforces this separation. Dimension values, units of measure and number series do not control access.

Number series generate document numbers automatically in a defined pattern for each document type. Dimensions, location codes and payment terms do not generate numbers.

A sandbox environment lets consultants test configurations and extensions safely before production. Working only in production, printed copies and personal computers do not provide a safe test space.

The change log records changes to selected tables and fields with the user and time, which supports review. Sticky notes, unrecorded calls and undated screenshots do not provide reliable records.

Dimensions add analysis codes such as department and project to transactions, which allows analysis without multiplying accounts or companies. Printed balances and separate companies do not provide that flexible analysis.

General journals support reversing entries, and recurring journals automate periodic postings. Manual daily postings are error-prone, customer ledger entries do not reverse accruals, and quotes do not post to the ledger.

Applying the payment in the cash receipts journal to open customer entries closes the invoice and updates the balance. Archives, item tracking and reminders without payment entries do not settle the invoice.

Cash flow forecasts combine open receivables, payables and planned amounts to project cash over a period. Item pictures, transfer orders and depreciation books do not forecast cash.

Recurring journals automate regular postings, and reviewing open entries and reconciling banks before closing finds gaps early. Last-day manual postings, deleting entries and disabling the audit trail all increase risk.

Bank reconciliation with matching rules pairs bank lines with ledger entries automatically, which reduces manual work. Manual matching is slow, deleting payments loses data, and posting statements as orders is wrong.

The Make Order action converts the quote lines into a sales order, which avoids re-entry. Retyping, creating new customers for each order and posting quotes as invoices are not the intended process.

Price agreements with a date range apply special prices during the chosen period automatically. Permanent changes affect everyone, manual line discounts are error-prone, and invoice numbers are not prices.

Approval workflows route purchase documents above a threshold to approvers before release, which enforces spending control. Print previews, address fields and pick lists do not enforce approvals.

Defaults from cards and templates reduce manual entry, and credit limit checks stop orders that exceed approved credit. Retyping addresses, orders without item numbers and posting without review all increase errors.

Sales price or line discount agreements with dates apply automatically to matching orders during the period. Manual line discounts are error-prone, free items are a different commercial term, and permanent price changes affect all customers.

A sales return order records the receipt of the returned goods and the credit memo that adjusts the receivable. A negative sales order or a purchase order does not correctly adjust both stock and receivables.

Account schedules and financial reports can compare actuals and budgets by period and account. A customer export, item cards and archive lists do not compare budgets.

Extensions add functionality without changing base code, which keeps upgrades manageable. Direct base modifications complicate upgrades, spreadsheets do not change the page, and separate databases are not a page customization method.

Report layouts in Word or RDLC can be changed by business users, which avoids developer work for presentation changes. Screenshots, plain text and handwritten totals do not provide a maintainable standard report.

Entries pages and analysis views allow filtering by date and dimension in a grid, which supports detailed review. Printed journals, manual copies and pictures are slower and less flexible.

Job queue entries can run reports on a schedule, and the results can be sent automatically. Manual runs, printed copies and notes on cards do not send the list automatically.

An API integration with authentication and scoped permissions exposes the needed data securely. Manual copies, shared logins and emailed databases are insecure and error-prone.

Item tracking with lot numbers records which lots were received and shipped, which supports traceability to customers. Location codes, item categories and discounts do not track lots.

Warehouse movements and bin movements record stock transfers between bins within a location. Sales invoices, purchase quotes and vendor entries do not move stock between bins.

The average costing method recalculates unit cost as an average of inventory on hand, which smooths price fluctuations. Last purchase price, fixed typed prices and vendor list prices do not reflect average cost.

The inventory cost and sales analysis report summarizes sales and cost by item for a period, which supports margin review. Address lists, bank account cards and asset registers do not show item cost and sales.

The costing method determines how cost is calculated, and inventory posting setup with posting groups determines the general ledger accounts used. Pictures, phone numbers and job titles do not affect valuation or posting.

Grouping picks with a pick worksheet batches orders and optimizes the picking route. Individual unpicked postings, moving items to customers and single-bin storage do not reduce travel.