Free Microsoft Dynamics MB-800 Actual Exam Questions

I think the key is to first apply the filter that narrows down to "My Customers" so you’re not dealing with unnecessary data. Then you should set the date filter for year-to-date sales to target the right timeframe, which lets your calculation be accurate. After both filters are set, you can safely add the calculated column or measure for YTD sales. Doing it in this order makes sure your calculation doesn’t include extra data or dates outside the range. So, filter customers first, then filter dates, then calculate.

I’d start by adding the filter for “My Customers” to make sure you’re only looking at that group right away. Next, set the date filter specifically for this year to get the year-to-date data before doing any calculations. Once those filters are in place, add the total sales field and then apply the sum aggregation so you get the YTD sales total. That way, you’re working with the right subset and timeframe before pulling numbers. It seems cleaner than trying to calculate before filtering properly.

I think option B makes sense, since posting the discounts to a separate purchase line could help isolate the discount amounts from item costs. That way, discounts aren’t mixed into the standard item cost.

I’d rule out option A because standard item costing usually includes discounts, so it won’t separate them cleanly. Choosing the right G/L account (C) to track discounts separately makes more sense here.

I’d go with starting by validating the sales orders to make sure all info is correct and complete. Next, updating the order status is key so the system reflects the current state of each order. Wrapping up by generating reports makes sense to keep track of what’s been processed and spot any trends or issues. This sequence covers accuracy, process tracking, and review, which are all important steps.

I’d start by reviewing each sales order for accuracy, then process them to update inventory and billing, and finish by generating invoices to complete the transaction. This flow keeps things in order and covers all bases.

B. Enabling Direct Posting on the G/L Account Card allows AR users to post transactions directly, which might fix posting issues without blocking customers or accounts. It addresses the problem from the G/L side instead.

It’s A, blocking the customer card stops bad AR entries without affecting G/L accounts.

I think for scenarios involving wrong amounts or products, credit notes plus new invoices fit best since you can’t change a posted invoice directly. For address errors, just correcting the invoice should work fine without extra docs.

For wrong amounts, credit note plus new invoice is safest.

D imo, bank account posting groups usually handle cash flow, not revenue posting. So, focusing on customer (B) and product (C) groups makes more sense for invoicing revenue setup.

Option A could be crucial too since general business posting groups help define overall revenue accounts. Without them, the system might not know where to post the revenue at a company level.

I get why people are picking D, but I’d go with A here. Payment Service sounds like it covers the actual processing of payments at the point of sale, which is crucial for cash and carry desks. Setting terms to zero days (D) ensures no delay, but it doesn’t handle the payment itself. So, for sales setup that includes payment handling, A feels like the better fit.

Not B, since Direct Debit usually means pulling funds later, which isn’t ideal for cash and carry where payment should be immediate. A or C seem more direct for instant payments.

I think setting up the budget control first makes sense to catch issues early, then define approval workflows before creating the order. That way, all approvals happen with budget checks in place.

I’d switch it up by starting with setting policies, then doing the budget check early to avoid wasting time on approvals if funds aren’t there. After that, assign approvals and finally create the order.

Option B makes sense since you need to classify customers as wholesale, and E ties those groups to accounts, which is key for posting to the right receivables account. Without these two, you can’t control where the transactions post.

B, E. The customer posting groups (B) let you classify customers like wholesale vs retail, while the general business posting groups (E) link those classifications to specific accounts. Together, they control how transactions post to receivables accounts. The actual account numbers (A and D) are assigned within the posting groups, so picking those alone isn’t enough without setting up the groups. General Posting Setup (C) is more about overall ledger integration but doesn’t handle customer-specific posting rules directly.

B sets the default bank account, D clearly covers automatic archiving, fits best.

B locks in the default bank account, and D handles archiving post-payment automatically.

I think the key is to first create that permission set that explicitly denies reading G/L info, so the agents can’t see balances but still pick G/L codes when posting. Then you assign this new deny-read permission set to the purchasing agents, which restricts their access properly. Lastly, verifying or testing confirms everything works as intended with those restrictions. This approach ensures they keep posting capabilities without viewing sensitive G/L data. Skipping the deny-read permission set step wouldn't restrict access properly, so that’s a must-do first.

Agree with creating a new deny read G/L permission set first, then assign and verify.

I think General Journal suits Bank balances since it’s more about financial entries, while RapidStart works better for Items and Customers as it handles master data imports cleanly. The other options seem off for these.

I’d pick RapidStart for Item and Customer since it handles master data well, but for Bank, General Journal seems more fitting because it deals with ledger entries directly. The other tools don’t fit as nicely here.

D for reports, B for automation tasks, and C for scanning fits best here.

I think Power BI fits financial reporting best since it’s built for real-time dashboards. Power Automate feels right for both onboarding and invoice workflows since it handles processes well. Scanning definitely needs Power Apps for device support.

Start by creating number series, then assign them to item categories, finally enable auto numbering.

Start by creating number series, then assign to item categories, finally enable auto numbering.

A/D? Resource items (A) seem made for ongoing use stuff like utilities, while Non-Inventory (D) is more for things you charge or bill but don’t track as inventory. Since these are infinite items like water and electricity, you probably want something that handles consumption and cost tracking better, which points more toward Resource. But if the goal is just to bill without detailed usage records, Non-Inventory might also work. The question isn’t crystal clear on usage tracking needs, so either could fit depending on what’s prioritized.

C/D? I’m thinking Service (C) could also make sense since utilities like water or electricity might be treated as a service you consume, not a physical inventory. Non-Inventory (D) feels too generic and might not capture the ongoing usage nature properly, but it’s definitely better than Inventory (B). Resource (A) is good for labor or machine time, but utilities feel more like services you’re consuming continuously rather than a resource you schedule or allocate.