Microsoft Dynamics 365 Finance and Operations Apps Developer (MB-500) — Free Practice Questions
10 free sample questions from a bank of 296, 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 create a new form in a project.
You need to display tabs in a vertical alignment.
Solution: Apply the Operational Workspaces pattern.
Does the solution meet the goal?
Yes
No
Answer: A
The short version
A — Yes, Operational Workspaces pattern provides vertical tabs. The pattern defines a navigating workspace layout with vertically aligned tabs for module sections, satisfying the form requirement.
Key concepts in this question
Operational Workspaces pattern: a Dynamics 365 form style organizing tasks and lists around a workspace with vertical navigation tabs.
Vertical tab alignment: tabs stacked along the side to switch between sections while preserving context and filters.
Form patterns in Finance and Operations: named guidance such as Simple List, Table of Contents and Operational Workspaces with distinct layouts.
Yes-or-No series format: each proposed pattern must be judged alone against the vertical-tab goal.
Pattern selection impact: choosing the documented pattern avoids custom layout work and passes design review.
Why A is correct
A is correct because Microsoft form-pattern guidance assigns vertical tab navigation to Operational Workspaces. Applying that pattern renders the expected side-aligned tabs for the new form without customization. The solution therefore meets the goal directly, confirming the settled Yes key for this row.
Why the others are wrong
B. No is wrong because Operational Workspaces is documented to display vertical tabs, so rejecting the solution contradicts pattern guidance.
MB-500 exam tip
For MB-500 forms, link vertical tabs to Operational Workspaces and Table of Contents, never to Simple List.
2A company has a cloud-based installation of Dynamics 365 Finance.
A user reports slow response times in the application when accessing the production environment.
You need to diagnose the performance issue by using the Environment monitoring tool.
Which two features of the Environment monitoring tool should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
System diagnostics
Customization analysis
Health metrics
Availability monitoring
SQL insights
Answer: C, E
The short version
CE — Health metrics plus SQL insights diagnose slow Finance response. One shows environment health, the other exposes database performance detail.
Key concepts in this question
Environment monitoring tool: Lifecycle Services dashboard for live activity and diagnostics of Finance and Operations environments.
Health metrics: surface service health, failed jobs, and platform signals reported to engineering with mitigation.
SQL insights: expose long queries, blocking, and index needs from LCS performance tooling for a specific environment.
System diagnostics and customization analysis: cover other traces or code health, not the core live-plus-database pair.
Availability monitoring: tracks uptime probes rather than deep query or health diagnostics.
Why CE is correct
Slow production response needs both platform health context and database proof. Health metrics reveal whether the environment itself reports concerns, while SQL insights drill into expensive statements and waits. Vendor prose describes Environment Monitoring plus SQL insights as the user-friendly health dashboard and cites references for both. That CE pairing directly matches diagnose-by-monitoring, with consensus on the health-plus-SQL combination.
Why the others are wrong
A. System diagnostics assist general tracing but are not the paired health-plus-SQL monitoring features.
B. Customization analysis reviews code quality, not live production slow-response signals.
D. Availability monitoring checks reachability, without query-level database diagnostics.
MB-500 exam tip
Slow Finance cloud response equals Health metrics plus SQL insights in Environment monitoring.
3Note: 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 create a new form in a project.
You need to display tabs in a vertical alignment.
Solution: Apply the Details Master pattern.
Does the solution meet the goal?
Yes
No
Answer: A
The short version
A — Yes, Details Master provides vertical tabs for the new form. Its details panel arranges tabs vertically by design.
Key concepts in this question
Form patterns: Finance and Operations UX templates that prescribe layout, navigation, and interaction.
Details Master pattern: master list plus details area where detail tabs stack vertically for focused editing.
Vertical alignment need: requires tabs listed down the side rather than across the top.
Alternative patterns contrast: other patterns use horizontal or hub layouts unsuited to the stated tab orientation.
Yes-No series: proposal must match documented pattern capability to earn Yes.
Why A is correct
Applying Details Master delivers the vertically arranged tab strip that is part of its details panel definition. Vendor reference to the pattern docs confirms vertical tabs are included. Consensus is unanimous for Yes because no custom layout is needed. The solution therefore meets the display-tabs-vertically goal exactly as worded.
Why the others are wrong
B. No is wrong because Details Master is documented to include vertical tabs in the details panel.
MB-500 exam tip
Vertical tabs on a new form equals Details Master, memorize its details-panel tab orientation.
4You are a Dynamics 365 Finance developer. You have two tables as shown in the following exhibit: You need to configure Table1 to ensure that records cannot be deleted from Table1 if Table2 contains related records.
Which value should you use for the OnDelete property?
None
Cascade
Cascade + Restricted
Restricted
Answer: D
The short version
D — Restricted blocks deletion of Table1 when related Table2 rows exist. It enforces referential protection at the kernel level without cascading deletes.
Key concepts in this question
OnDelete property: table-relation behavior controlling what happens when a parent record is deleted.
Restricted: prevents parent deletion if child records reference it, raising an error instead of removing data.
None: permits deletion without checks, leaving orphans or relying on custom code for protection.
Cascade: deletes child records automatically with the parent, the opposite of preservation.
Cascade plus Restricted: a hybrid variant tied to specific relation types, not the plain protective block required here.
Why D is correct
D is correct because the requirement is strict prevention: records cannot be deleted from Table1 if Table2 holds related records. Restricted implements that guard natively in Finance and Operations, aborting the delete with a referential message. It preserves child history while requiring deliberate cleanup before parent removal.
Why the others are wrong
A. None performs no referential check, so Table1 deletion would succeed despite related Table2 rows.
B. Cascade would delete related Table2 records along with Table1, violating the preservation mandate.
C. Cascade plus Restricted applies a different conditional cascade behavior, not the straightforward block specified.
5Note: 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 create a new form in a project.
You need to display tabs in a vertical alignment.
Solution: Apply the Simple List pattern.
Does the solution meet the goal?
Yes
No
Answer: B
The short version
B — No, Simple List pattern does not create vertical tabs. It renders a flat list plus details layout without side-aligned tab navigation.
Key concepts in this question
Simple List pattern: a master-detail form with a grid or list on top and fields below, optimized for quick browsing.
Vertical tabs requirement: side-stacked navigation between sections, characteristic of workspace and contents patterns.
Operational Workspaces contrast: the workspace pattern that does supply vertical tabs for task-oriented work.
Table of Contents contrast: another pattern explicitly providing navigable sections with vertical orientation.
Series evaluation: this row tests whether Simple List alone can satisfy the same vertical-tab goal.
Why B is correct
B is correct because Simple List lacks the tab-strip navigation element the stem demands. Applying it would produce list-driven browsing rather than vertically aligned tabs, leaving the requirement unmet. The settled No therefore reflects documented pattern capabilities rather than implementation quality.
Why the others are wrong
A. Yes is wrong because Simple List has no vertical-tab construct, so it cannot meet the stated form goal.
MB-500 exam tip
When MB-500 asks vertical tabs plus Simple List, answer No; reserve Yes for Workspaces and Table of Contents.
6A company uses Dynamics 365 Supply Chain Management. You create a customization in a development environment.
You need to create a software deployable package so that you can deploy the customization to a test environment.
What are two possible ways to achieve the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
In Visual Studio, export the project and upload the project to the asset library.
In Azure DevOps, queue a build from the corresponding branch and upload the package to the asset library.
In Azure DevOps, extract the model from a package and upload the model to the asset library.
In Visual Studio, create a Dynamics 365 deployment package and upload the package to the asset library.
Answer: B, D
The short version
BD — Azure DevOps build plus Visual Studio package create deployable software. Both paths yield an LCS asset-library package for test promotion.
Key concepts in this question
Software deployable package: versioned bundle of models and binaries that LCS deploys to non-dev environments.
Azure DevOps path: queue a build from the branch to compile and emit the package, then upload to asset library.
Visual Studio path: Dynamics 365 Deploy Create Deployment Package on a dev box for the same artifact.
Asset library role: LCS store where packages wait for deployment to test or production.
Model-only traps: exporting projects or extracting models without packaging does not produce a deployable unit.
Why BD is correct
Customization promotion requires a deployable package in LCS, creatable either by pipeline build or by Visual Studio packaging. Option B uses Azure Pipelines to build from source and upload, while option D uses Visual Studio Create Deployment Package then upload. Vendor docs confirm both routes with unanimous consensus for BD. Project export or model extract alone skips package creation and fails the goal.
Why the others are wrong
A. Exporting the project uploads source, not a compiled deployable package.
C. Extracting the model uploads a fragment without the deployment wrapper LCS requires.
MB-500 exam tip
Deployable package equals DevOps build plus upload or VS Create Deployment Package plus upload.
7Note: 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 create a new form in a project.
You need to display tabs in a vertical alignment.
Solution: Apply the Table of Contents pattern.
Does the solution meet the goal?
Yes
No
Answer: A
The short version
A — Yes, Table of Contents pattern delivers vertical tab navigation. Its contents pane stacks section links vertically while the main pane shows the selected group.
Key concepts in this question
Table of Contents pattern: a form layout with a navigable contents tree plus detail area for complex records.
Vertical alignment: section links arranged along the side for fast switching without scrolling long pages.
Simple List contrast: a flat browsing layout with no side tabs, correctly judged as non-meeting in the sibling item.
Operational Workspaces similarity: another vertical-tab pattern, confirming that multiple patterns can share navigation traits.
Goal satisfaction: the stem needs only vertical tabs, which this pattern provides natively.
Why A is correct
A is correct because Microsoft documents Table of Contents as a vertically navigated form with a contents control. Applying it to the new form produces the required side-aligned tabs for its sections. That direct pattern-to-requirement match justifies the settled Yes without custom controls.
Why the others are wrong
B. No is wrong because Table of Contents explicitly includes vertical navigation, so the goal is satisfied.
MB-500 exam tip
For MB-500, treat Table of Contents as the classic vertical navigation answer alongside Operational Workspaces.
8A company uses Dynamics 365 Finance.
You create a new form that must have the ability to open from the menu.
You need to set up the form for the menu.
What should you add to the menu?
display menu item
menu reference
output menu item
action menu item
Answer: A
The short version
A — Display menu item exposes the new form from the menu. Display items launch forms for viewing and editing records.
Key concepts in this question
Menu architecture: Finance and Operations navigation launches objects through typed menu items.
Display menu item: opens a form, the correct launcher for interactive data entry and lists.
Menu reference: nests an existing menu node, not a direct form opener.
Output item: targets reports or batch outputs rather than interactive forms.
Action item: runs a class or action, not a full form surface.
Why A is correct
A new form that must open from the menu needs a launcher bound to form display. Display menu item is defined to start forms, as vendor prose states. Consensus is unanimous for A because only that type carries form reference semantics for navigation. References organize menus, output items print, and action items run code, so none satisfies form-opening.
Why the others are wrong
B. Menu reference points to another menu, without binding the new form itself.
C. Output menu item serves printable or export artifacts, not interactive forms.
D. Action menu item invokes runnable logic, not form display.
MB-500 exam tip
Form on menu equals display menu item, report equals output, code equals action.
9You are implementing Dynamics 365 Supply Chain Management for a customer.
The complete solution involves an ISV product that was obtained from Microsoft AppSource.
You notice that there is a significant slowdown in certain screens once the ISV product is installed.
You need to determine the cause of the issue.
Which Lifecycle Services (LCS) tool or functionality should you use?
SQL Server Runtime
SQL Insights
Regression suite automation tool (RSAT)
Impact analysis report
Issue search
Answer: B
The short version
B — SQL Insights in Lifecycle Services pinpoints slow ISV queries. It surfaces long-running SQL, blocking and missing-index insight tied to the AppSource customization.
Key concepts in this question
SQL Insights: an LCS diagnostics lens aggregating query performance, blocking chains and database pressure over time.
ISV slowdown scenario: AppSource product code adding unindexed queries or locks that degrade specific Finance screens.
SQL Server Runtime: an execution detail rather than a diagnostic tool for attributing slow screens.
RSAT and impact analysis: functional regression and upgrade-impact tools, not live SQL performance triage.
Issue search: a knowledge-base lookup for known fixes, useful after the bottleneck is already identified.
Why B is correct
B is correct because SQL Insights collects top queries, wait stats and blocking contributors linked to recent changes. Filtering by time and screen flow lets the developer show that ISV queries dominate duration or cause locks. That evidence isolates the AppSource customization as the slowdown cause far faster than generic testing.
Why the others are wrong
A. SQL Server Runtime describes engine execution, it provides no LCS dashboard for slow-screen attribution.
C. RSAT automates business-process regression, it does not profile SQL causing screen latency.
D. Impact analysis reports upgrade conflicts from customization, not live query performance after install.
E. Issue search finds published fixes but cannot measure which queries slow the affected screens.
MB-500 exam tip
On MB-500 slow screens after ISV install, choose SQL Insights first to prove query-level cause.
10You are training a new Dynamics 365 Finance developer.
You need to recommend where asynchronous integrations should be used instead of synchronous integrations.
For which scenario should you recommend asynchronous integration?
A retailer requires all new customer data captured at point of sale (POS) terminals through the day sent back to the system.
A retailer wants to ensure gift card balances are communicated back to the system from point of sale (POS) terminals in near real-time.
A manufacturer wants to move production data from an on-premises deployment Dynamics 365 Finance in near real-time.
A warehouse wants to track movement of all inventory from scanners to the system.
Answer: A
The short version
A — Bulk daily POS customer sync suits asynchronous integration. High-volume, delay-tolerant uploads should queue and process in the background rather than block registers.
Key concepts in this question
Asynchronous integration: message- or batch-based transfer where senders continue working while the system processes later.
Synchronous integration: real-time request and reply needed when the next step depends on an immediate answer.
Daily customer-data upload: many POS terminals sending new records through the day, consolidatable into scheduled batches.
Gift-card balance check: a payment-time lookup requiring near-real-time authorization, unsuitable for deferral.
Near-real-time production and scanner tracking: operational flows needing fast feedback, favoring synchronous paths.
Why A is correct
A is correct because end-of-activity customer-data delivery tolerates latency and benefits from batching, retry and throttling. Queuing POS payloads asynchronously keeps registers responsive and smooths Finance ingestion overnight or on schedule. The pattern matches Microsoft guidance to use async for bulk, non-urgent transfers.
Why the others are wrong
B. Gift-card balances affect whether a sale completes, so they need synchronous near-real-time confirmation.
C. Moving production data in near real time demands immediate propagation, pointing to synchronous integration.
D. Warehouse scanner movements drive inventory decisions continuously, requiring fast synchronous updates.
MB-500 exam tip
For MB-500 integration, choose async for bulk daily syncs and sync for balance, production or scanner immediacy.