Microsoft Certified - Dynamics 365 Business Central Developer Associate Certification MB-820 Updated Exam

1. Requirement: Specify that page 21 (or 27) must be opened after publishing.

Solution: Option A.

Reasoning: The launch.json file controls the behavior of the debugger and the deployment process in Visual Studio Code. To determine which page opens automatically when you press F5 (publish and run), you configure the "startupObjectId" property within launch.json.

Note: While the question mentions page 21 and the option lists 27, this is the only valid option for controlling the startup object. Option C is incorrect because app.json is the manifest file and does not control launch behavior.

2. Requirement: Enable debugging & Disable source code download.

Solution: Option E.

Reasoning: These settings relate to the Intellectual Property (IP) protection of your extension. This configuration belongs in the app.json file (the manifest), specifically under the "resourceExposurePolicy" property.

To enable debugging, you set "allowDebugging": true.

To disable downloading source, you set "allowDownloadingSource": false.

Option B is incorrect because this policy does not belong in launch.json.

Option D is incorrect because it sets allowDownloadingSource to true, which contradicts the requirement to disable it.

Enclose line 08 into BEGIN .. END = NO

Add TopCustomerOverview.Open(); before = YES

TopCustomerOverview.SetFilter(Sales_LCY, '>10000'); in line 06.

Add TopCustomerOverview.Open(); after TopCustomerOverview.SetFilter(Sales_LCY, '>10000'); in line 06. = YES

Replace SetFilter in line 06 with SetRange. = NO

The code provided has a runtime error because the query TopCustomerOverview must be opened before it can be read from. Therefore, TopCustomerOverview.Open(); should be added before trying to read from the query, which is not present in the code.

Enclosing line 08 into a BEGIN .. END block is unnecessary because it is a single statement, and AL does not require a BEGIN .. END block for single statements within trigger or procedure bodies.

TopCustomerOverview.SetFilter(Sales_LCY, '>10000'); is a correct method to set a filter for the query, and using SetRange instead is not necessary unless the requirement is specifically to set a range of values, which is not indicated in the procedure's description.

In summary, for the procedure to run correctly, the query must be opened after setting the filter and before attempting to read from it. The SetFilter method is correct for the intended operation, and there's no requirement to use SetRange or to enclose the Message call in a BEGIN .. END block.

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.