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 May. 21, 2026 (see below)
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.
A company has an on-premises Business Central instance named TEST The instance uses Windows authorization and a developer services port of 7149 Visual Studio Code is installed on the same server.
You create a new AL project but cannot download the symbols.
The launch json file contains the following code:
You need to download the symbols.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
You are working on an on-premises Business Central instance and unable to download symbols for a new AL project. The current configuration in launch.json does not allow you to download symbols, and you need to make corrections.
Key Points in the Scenario:
Instance name is TEST.
Developer services port is 7149.
Windows authentication is being used.
Correct Answers:
A . Change the server Instance parameter to TEST.
The serverInstance parameter must match the name of the Business Central instance, which is TEST in this scenario. You need to modify this to reflect the correct instance name.
B . Add the port: 7149 parameter.
Since the developer services are using port 7149, you need to specify this in the launch.json file by adding the port parameter with the value 7149.
Incorrect Options:
C . Change the name parameter to TEST: The name parameter is just a label and does not affect downloading symbols, so changing this won't help.
D . Change the authentication parameter to UserPassword: The authentication method is already set to Windows, which is valid for this scenario. Changing it to UserPassword is unnecessary unless specified by the system.
E . Check which server the instance is installed on and replace http://localhost with the correct IP address: Since the server is on the same machine as Visual Studio Code (as specified), localhost is correct.
You plan to write unit test functions to test newly developed functionality in an app.
You must create a test codeunit to write the functions.
You need to select the property to use for the test codeunit.
Which property should you use to ensure that the requirements are fulfilled?
When creating a test codeunit in Microsoft Dynamics 365 Business Central to write unit test functions, the SubType property (A) of the codeunit should be set to Test. This property is crucial for defining the codeunit's purpose and behavior within the application. By setting the SubType property to Test, you are indicating that the codeunit contains test functions intended to validate the functionality of other parts of the application, such as customizations or new developments. This distinction ensures that the testing framework within Business Central recognizes the codeunit as a container for test functions, allowing it to execute these functions in a testing context, which can include setting up test data, running the tests, and cleaning up after the tests have completed.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Amy Green
11 days agoWilliam Morgan
18 days agoStephanie Flores
1 month agoEmily Peterson
29 days agoRonald Gonzalez
22 days agoPaul Flores
16 days agoJennifer Smith
14 days agoKimberly Collins
1 month agoEttie
2 months agoLamonica
2 months agoLeah
2 months agoCorazon
3 months agoJacqueline
3 months agoAsuncion
3 months agoAshlyn
3 months agoCarole
4 months agoEulah
4 months agoWilda
4 months agoTerrilyn
4 months agoRosann
5 months agoAlease
5 months agoGertude
5 months agoShanda
5 months agoKiley
6 months agoPaulina
6 months agoCora
6 months agoMammie
6 months agoKanisha
7 months agoBrandon
7 months agoAnnalee
7 months agoDierdre
8 months agoLaurel
8 months agoJaclyn
8 months agoSamira
8 months agoCasie
9 months agoHerminia
9 months agoMarg
11 months agoRodolfo
1 year agoAnnelle
1 year agoGayla
1 year agoRosita
1 year agoLacey
1 year agoHan
1 year agoCarry
1 year agoShenika
1 year agoClaudia
1 year 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