Free Preparation Discussions
MENU
Microsoft MB-820 Exam Questions
- Microsoft Dynamics 365 Certifications
- Microsoft Dynamics 365 Business Central Developer Associate Certifications
Free Microsoft MB-820 Exam Actual Questions
Note: Premium Questions for MB-820 were last updated On Jun. 19, 2026 (see below)
You ate creating a test codeumt for a company that uses Business Central. The company requites the following list of choices while posting a sales order:
* Ship
* Invoice
* Ship & Invoice
You must create a test codeunit that automatically selects one of these options. You need to create the test codeunit Which handler should you use?
StrMenuHandler is used to simulate the selection of an option from a string-based menu, such as the 'Ship,' 'Invoice,' or 'Ship & Invoice' options when posting a sales order. This handler allows you to programmatically select an option during automated testing.
Other handlers, such as SessionSettingsHandler or SendNotificationHandler, do not simulate the selection of menu choices, which is specifically required in this scenario.
For more details on StrMenuHandler and how it simulates user interaction with menu choices, refer to the Test Handlers in Business Central.
You need to call the Issue API action from the mobile application.
Which action should you use?
You are developing an app that will be published to Microsoft AppSource.
The app requires code analyzers to enforce some rules. You plan to add the analyzers to the settings.json file.
You need to activate the analyzers for the project.
Which three code analyzers should you activate to develop the app for AppSource? Each correct answer presents part of the solution
NOTE: Each correct selection is worth one point.
You need to determine why the debugger does not start correctly.
What is the cause of the problem?
In Microsoft Dynamics 365 Business Central, when configuring snapshot debugging, it is crucial that the parameters in the configuration file are correctly set. From the options provided, the issue with the debugger not starting correctly is most likely due to an incorrect 'userId' parameter.
Option A is the cause of the problem. The 'userId' parameter must be the GUID of the user, not the username. The snapshot debugger needs the exact GUID to attach to the right session for debugging.
Option B is incorrect because 'breakOnNext' set to 'WebClient' is a valid setting. This tells the debugger to break on the next client action in the web client, which is a typical scenario.
Option C is not the cause of the problem. The 'userId' parameter is meant to specify which user session to debug, and this works in conjunction with the 'breakOnNext' parameter.
Option D is incorrect as the 'executionContext' parameter does not need to be set to 'Debug' for snapshot debugging to work. 'DebugAndProfile' is a valid value for the 'executionContext' parameter, as it allows for debugging and collecting performance information.
Therefore, the reason why the debugger does not start correctly is due to Option A: The 'userId' parameter must have the GUID of the user specified, not the username.
You need to create the access modifier for IssueTotal.
Which variable declaration should you use?
In Business Central development using AL (the language for Business Central extensions), the use of access modifiers defines how variables and procedures are accessed within and outside of an object or codeunit.
Access Modifiers in AL:
Public: A public variable can be accessed from any object or codeunit within the same module or extension.
Protected: This restricts access to the current object and objects that inherit from the current object. However, in AL (at least in versions used for Business Central), the Protected access modifier is used with methods but not variables.
Internal: This modifier restricts the visibility to the current extension. This means that variables or methods declared as internal can only be accessed from within the same extension. This is appropriate when you want to provide functionality that is shared within the extension but not exposed externally.
Local: This restricts the variable or method to the current object or method where it is declared. It cannot be accessed from anywhere else, even within the same extension.
Scenario Justification:
In the scenario for Contoso, Ltd., IssueTotal is a global variable in the ISSUE BASE extension, and the ISSUE EXT extension needs to access it. Therefore, the variable cannot be declared as Local, because this would restrict access to just the current object (or method).
Using Public would expose the variable outside of the extension, which is unnecessary because you only want other parts of the extension (specifically the ISSUE EXT extension) to have access.
The best choice in this case is Internal because it restricts access to the variable to within the same extension, which includes the base extension and any dependent extensions like ISSUE EXT. It strikes the right balance between visibility and encapsulation.
Microsoft Dynamics 365 Business Central Developer Reference:
Access Modifiers in AL: Microsoft's documentation on AL provides the details on access modifiers, where it is specified that internal variables can be accessed within the extension, and the public variable is accessible across all extensionssource: Microsoft Learn on AL Programming.
Best Practices for AL Development: Business Central development best practices suggest keeping variables internal unless they need to be accessed outside of the current extensionsource: Microsoft Learn on AL development guidelines.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Steven Morris
10 days agoJeffrey Williams
21 days agoAmy Green
1 month agoWilliam Morgan
2 months agoStephanie Flores
2 months agoEmily Peterson
2 months agoRonald Gonzalez
2 months agoPaul Flores
2 months agoJennifer Smith
1 month agoKimberly Collins
2 months agoEttie
3 months agoLamonica
3 months agoLeah
3 months agoCorazon
4 months agoJacqueline
4 months agoAsuncion
4 months agoAshlyn
4 months agoCarole
5 months agoEulah
5 months agoWilda
5 months agoTerrilyn
5 months agoRosann
6 months agoAlease
6 months agoGertude
6 months agoShanda
6 months agoKiley
7 months agoPaulina
7 months agoCora
7 months agoMammie
7 months agoKanisha
8 months agoBrandon
8 months agoAnnalee
8 months agoDierdre
9 months agoLaurel
9 months agoJaclyn
9 months agoSamira
9 months agoCasie
10 months agoHerminia
10 months agoMarg
1 year agoRodolfo
1 year agoAnnelle
1 year agoGayla
1 year agoRosita
1 year agoLacey
1 year agoHan
1 year agoCarry
2 years agoShenika
2 years agoClaudia
2 years agoLavonne
2 years agoDaren
2 years agoLashawnda
2 years agoStaci
2 years agoJacquelyne
2 years agoMinna
2 years agoJohnetta
2 years agoKenneth
2 years agoDell
2 years agoAaron
2 years agoKimbery
2 years agoGlenn
2 years agoPaz
2 years agoTashia
2 years agoJenelle
2 years agoCory
2 years agoJade
2 years agoStephaine
2 years agoRuthann
2 years agoCortney
2 years agoMurray
2 years agoElvera
2 years agoLawrence
2 years ago