Microsoft MB-820 시험

Question No : 1

You need to add a property to the Description and Comments fields with corresponding values for the control department manager.
Which property should you add?

• A.Description
• B.Caption
• C.ToolTip
• D.InstructionalText

답을 확인하기

정답:

Question No : 2

HOTSPOT
You need to assist the development department with setting up Visual Studio Code to design the purchase department extension, meeting the quality department requirements.
How should you complete the app.json file? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:

Question No : 3

Topic 3, Fabrikam Inc

Company background and technical environment
Current environment
Fabrikam Inc. is a medium-sized company that plans to implement Dynamics 365 Business Central as an ERP system. The company has a development department that will help with the ERP implementation.
Most employees work remotely from different countries or regions and speak different languages.
The various locations and languages cause issues with the current on-premises software.

Planned improvements
Fabrikam Inc. plans to implement new and modern software to manage the company. The company wants to use Business Central because it is cloud-based and meets all company requirements.
The company intends to improve reporting and integration functionality by using modern tools such as Power BI and APIs. To reduce the amount of information sent by email, the company plans to expose vendor information to be consumed from external users.

Technical specifications
The development department installed Visual Studio Code to create Business Central extensions so the ERP system could be customized according to company needs. All extensions must be developed for the Business Central 2024 wave 1 online version.
The development department plans to use telemetry to control the appropriate use of each new development and works directly in licensed sandbox environments supplied by Microsoft.

The following departments at Fabrikam Inc. have multiple requirements:
• Development
• Control
• Accounting
• Quality

Development department
The development department designed an extension for the purchase department. Because the developers plan to work with telemetry for monitoring operations, they need the Application Insights information. To accomplish this, the department must add a setting in the corresponding file. The quality department does not want to receive any warning about the Application Insights setting when the extension is compiled.

Control department
The control department requires customization to Business Central by using a per-tenant extension (PTE) named Subcontract Docs. The PTE includes a table named Subcontract Documents.

The table has the following fields:
• ID: A unique identifier
• Subcontract No.: Related to the standard Vendors table
• Description: A short description of a received document
• Document: A media type that has the document
• Comments: Comments about the document
• Date: When the document was imported
• Amount: Amount related with the imported document
• Posted Indicates if the document is managed

The extension must be in English - United States (ENU) and Spanish Traditional Sort (ESP) so the application can be used in both languages. The translations must be on the table, not on the page, to avoid repeating them. The control department does not want to use translation files.
The control department manager requires a brief guide for the Description and Comments fields when employees create a new record so users know what to include in the fields. The guide must disappear as soon as users add a value in the fields.
The Subcontract Documents table must be displayed on a new page named Subcontract Document List through an action from the standard Vendor page.
The Amount field, included in the Subcontract Document List, must be formatted in bold format when the record is posted (field Posted = true).
The control department also requires a report to display a list of subcontract documents named Subcontract Documents Excel List.

The report must meet the following requirements:
• Downloads a file only in Microsoft Excel.
• Includes a predefined format with two worksheets; one with the posted subcontract documents and another with the unposted subcontract documents.

Accounting department
The accounting department plans to use Power Bl to analyze information generated by the control department. The accounting department plans to expose an API named API Customer Lines. To improve the performance, the API must use read-only information and work with a Query object to summarize the data.



The accounting department must expose data such as the following.



The qty column must be the sum of the Outstanding quantity field of Sales Order Lines. It must be in descending order by quantity.
The department also exposes a page named Fabrikam Vendor API that includes vendor information from the Vendor table, such as number and name. The API must use the replica database to improve performance.
Because Fabrikam Inc. is based in multiple countries and regions, the company periodically must send accounting movements between two dates to the local tax offices named Fabrikam Accounting. The format for this file must be an XML file generated by an XMLport object. For security reasons, it is not possible to receive data from this XMLport.
The department has a version 1.0.0.1 installed for an extension named Quality Control. The department develops a new version 1.0.0.2 and uses a codeunit with the subtype Upgrade to update it. The department requires the values for AppVersion and DataVeision on the tnaaer OnUoaradePerCompany after using NavAocGetCurrentModulelnformation.

The generated XML file must have a schema like this:




Quality department
The quality department requires that every new app or extension is designed to meet standard company guidelines. The quality department plans to follow the standard Business Central data model. The quality development must be able to use triggers correctly.
The department must ensure that when a vendor is deleted, the system also removes each record in the Subcontract Documents table related to the vendor. If the subcontract document record has the field Posted = false, it must not be possible to delete the record.

HOTSPOT
You need to define the XML file properties for the accounting department.
How should you complete the code segment? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:

Question No : 4

HOTSPOT
You need to write an Upgrade codeunit and use the DataTransfer object to handle the data upgrade.
Which solution should you use for each requirement? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:


Explanation:
Upgrade codeunit trigger: OnValidateUpgradePerDatabase
Since the question specifies that you are handling data upgrades, and you need to use validation before upgrading at the database level, the correct choice is OnValidateUpgradePerDatabase. This method ensures that the upgrade process is validated before applying to the entire database, making it more efficient when data affects multiple companies or structures.
DataTransfer method to use: CopyRows
CopyRows is the appropriate method when you are handling large data transfers between tables, especially in an upgrade scenario where you are migrating or transferring data from one table to another. It copies entire rows of data and is optimal for bulk data operations during upgrades.

Question No : 5

HOTSPOT
You need to parse the API JSON response and retrieve each order no. in the response body.
How should you complete the code segment? To answer select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:


Explanation:
Code Segment Analysis:
The AL code is trying to read JSON data from a response and process it to extract subcontracting order numbers. It uses JsonToken, JsonObject, and JsonArray to work with the JSON data. JToken.ReadFrom(Data): This line reads the incoming JSON data and converts it into a token. It processes the full JSON body so you can start working with it.
JToken.SelectToken("results"): This line selects the part of the JSON containing the results array. The key "results" is where the JSON response data is expected to be found.
JsonArray: Once the results are extracted, they are stored as an array, and each element in the array (which is expected to contain subcontracting order numbers) is processed. SubcontractingOrderNo: The extracted order_no from the JSON is stored in this variable.
Breakdown of Steps:
JToken.ReadFrom(Data): This step reads the entire JSON response.
JToken.SelectToken("results"): This step selects the results array from the JSON response. JArray.AsArray(): This step converts the selected results token into a JSON array that can be iterated over.
GetValueAsText(JToken, 'order_no'): This step retrieves the order_no from each element in the array.
Correct Code Completion:
JToken.ReadFrom(Data): This is the correct method to read the incoming JSON response, as it will convert the string into a JsonToken that can be further processed.
JToken.SelectToken("results"): This is the correct method to extract the results array from the token.
This method looks for the key "results" in the JSON and retrieves the relevant array.
Final Code Segment:
al
Copy code
procedure ReadJsonData(Data: text)
var
JToken: JsonToken;
JObject: JsonObject;
JArray: JsonArray;
SubcontractingOrderNo: Code[20];
begin
if Data = '' then
exit;
JToken := JToken.ReadFrom(Data); // Step 1: Read the JSON response data.
JToken := JToken.SelectToken('results'); // Step 2: Select the "results" array.
JArray := JToken.AsArray(); // Convert the token into a JSON array.
foreach JToken in JArray do begin
SubcontractingOrderNo := GetValueAsText(JToken, 'order_no'); // Retrieve the order number. end;
end;
Explanation=
JToken.ReadFrom(Data): This reads the raw JSON data string and converts it into a JSON token that can be processed.
JToken.SelectToken("results"): This extracts the results array from the JSON data.
JArray.AsArray(): Converts the token into an array so we can iterate over it.
GetValueAsText(JToken, 'order_no'): Extracts the order_no value from each item in the array.

Question No : 6

HOTSPOT
You need to log an error in telemetry when the business process defined in the custom application developed for Contoso, Ltd fails.
How should you complete the code segment? To answer, select the appropriate options in the
answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:


Explanation:
LogMessage('PT001', 'Business Process is failed.', Verbosity::Critical, DataClassification::SystemMetadata, TelemetryScope::ExtensionPublisher, CustDimension);

Question No : 7

DRAG DROP
You need to implement the Issue Management module and expose the Postlssue method.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. NOTE: Note than one order of answer choices is correct. You will receive credit for any of the correct orders you select.

답을 확인하기

정답:


Explanation:

Question No : 8

You need to create the access modifier for IssueTotal.
Which variable declaration should you use?

• A.Protected vat IssueTotal: Decimal
• B.Internal var IssueTotal: Decimal
• C.Public var IssueTotal: Decimal
• D.Local var IssueTotal: Decimal
• E.Var IssueTotal; Decimal

답을 확인하기

정답:
Explanation:
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 extensions 【 source: 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 extension 【 source: Microsoft Learn on AL development guidelines 】 .

Question No : 9

HOTSPOT
You need to write the code to call the subcontractor's REST API.
How should you complete the code segment? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:

Question No : 10

You need to determine why the debugger does not start correctly.
What is the cause of the problem?

• A.The "userld" parameter must have the GUID of the user specified, not the username.
• B.The "breakOnNext" parameter is not set to -WebServiceClient".
• C.The "userld" parameter is specified, and the next user session that is specified in the 'breakOnNext" parameter is snapshot debugged.
• D.The "executionContext* parameter is not set to "Debug".

답을 확인하기

정답:
Explanation:
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.

Question No : 11

HOTSPOT
You need to create the API page according to the requirements.
How should you complete the code segment? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

답을 확인하기

정답:


Explanation:
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-dataaccessintent-property

Question No : 12

DRAG DROP
You need to configure telemetry for the SaaS tenant and test whether the ingested signals are displayed.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

답을 확인하기

정답:


Explanation:
The correct sequence of actions to configure telemetry for the SaaS tenant and test whether the ingested signals are displayed would be:
Create an Azure Application Insights instance by using the Azure Portal in the Customer's subscription.
Select the environment in the Admin Center and place the connection string in the Application Insights Connection String field.
Select the Application Insights instance, select Logs and then inspect the Traces table.
To set up telemetry for a SaaS tenant using Azure Application Insights, you need to follow these steps:
Create an Azure Application Insights instance: This is the first step where you create an instance in Azure that will collect the telemetry data. This should be done in the customer's Azure subscription because it's their data that you're monitoring.
Configure the SaaS tenant to use the created Application Insights instance: This involves entering the correct connection string in the Business Central Admin Center so that telemetry data from the tenant is sent to the Application Insights instance.
Verify that telemetry is being collected: After configuring, you would check if the telemetry is arriving as expected by inspecting the Traces table in the Azure Application Insights instance. The 'Traces' table holds the telemetry data, which you can query to verify that the correct signals are being ingested.

Question No : 13

You need to determine why the extension does not appear in the tenant.
What are two possible reasons for the disappearance? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

• A.The extension was published as a DEV extension.
• B.The extension was not compatible with the new version within 60 days of the first notification.
• C.The extension was published as PT
• D.and the Platform parameter was not updated in the application file.
• E.The extension was published as PT
• F.and the Platform and Runtime parameters were not updated in the application file.
• G.The extension was not compatible with the new version within 90 days of the first notification.

답을 확인하기

정답:
Explanation:
In the context of Microsoft Dynamics 365 Business Central, an extension may not appear in the tenant for several reasons, particularly after an upgrade to a new major version.
Option A suggests that the extension was published as a DEV extension, which typically would not cause it to disappear after an upgrade because DEV extensions are intended for development and testing within sandbox environments.
Option B indicates that the extension was not compatible with the new version within 60 days of the first notification. This is a likely reason because Microsoft enforces compatibility rules, and extensions that are not made compatible within the specified timeframe might be removed or disabled.
Option C refers to the extension being published as a PTE (Per-Tenant Extension) and mentions the Platform parameter not being updated. This could cause issues, but not specifically the disappearance of the extension after an upgrade.
Option D expands on Option C by adding that both the Platform and Runtime parameters were not updated in the application file. This is a critical aspect because if these parameters are not correctly set to indicate compatibility with the new version of Business Central, the extension could be disabled or removed.
Option E is similar to Option B but mentions a 90-day period. This option does not align with standard Business Central practices for version compatibility requirements.
Therefore, the two possible reasons for the disappearance of the extension in the tenant after an upgrade are that the extension was not compatible with the new version within the required timeframe (Option B) and that the extension was published as a PTE without the Platform and Runtime parameters being updated (Option D).

Question No : 14

You need to call the Issue API action from the mobile application.
Which action should you use?

• A.POST/issues (88122e0e-5796-ec11-bb87-000d3a392eb5yMicrosoit.NA
• B.copy
• C.PATCH /issues {88122 eOe-5796-ed 1 -bb87-000d3a392eb5)/Mkrosotl.NA
• D.Copy
• E.POST /issues (88122e0e-5796-ec11 -bb87-000d3a392eb5)/Copy
• F.POST /issues (88122e0e-5796-ec11 -bb87-000d3a392eb5)/copy
• G.POST/issues(88122e0e-5796-ec11-bb87-000d3a392eb5)/MicrosoftNA
• H.Copy

답을 확인하기

정답:

Question No : 15

You need to determine If you have unwanted incoming web service calls in your tenant during the last seven days.
Which two KQL queries should you use? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

• A.Option A
• B.Option B
• C.Option C
• D.Option D
• E.Option E

답을 확인하기

정답: