MB-820 Sample Questions Answers

The task is to identify unwanted incoming web service calls during the last seven days. To do this, we need to look at KQL (Kusto Query Language) queries that would filter out web service calls based on the timestamp (to ensure the calls are within the last seven days) and by certain characteristics that would indicate they are unwanted, such as the wrong type of protocol (SOAP in this case, as Contoso Ltd. plans to dismiss using it).

Looking at the options:

Option A: This query selects all traces where the timestamp is within the last 7 days and where the custom dimension has a value of 'RT0008', and where the category is either 'ODataV4', 'ODataV3', or 'Api'. This query would show all API calls except SOAP, so it does not directly answer the question about unwanted calls.

Option B: This query filters for traces with a timestamp within the last 7 days, where 'RT0008' is present, and specifically looks for the category 'SOAP'. This query is correct because it directly targets SOAP calls, which are the unwanted calls according to Contoso Ltd.'s plans.

Option C: Similar to option B, this query filters for traces within the last 7 days and looks for 'RT0008' but uses the equality operator for the category 'SOAP'. This would also correctly return the unwanted SOAP calls.

Option D: This query also filters for traces within the last 7 days, but it excludes the 'ODataV4' category, which doesn't necessarily target the unwanted SOAP calls.

Option E: This query selects traces where the timestamp is within the last 7 days and the custom dimension has 'RT0008'. However, it filters out categories 'ODataV4' and 'Api', which does not directly help in identifying the unwanted SOAP calls.

Therefore, the queries that should be used to determine if there are unwanted incoming web service calls (SOAP calls) in the tenant during the last seven days are Options B and C. These queries are specific to identifying SOAP protocol usage, which is what Contoso Ltd. considers unwanted.

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).

For the requirements provided, the appropriate page types should be selected as follows:

Display relevant insights in the Housekeeping Role Center: HeadlinePart

Display the additional information for the Room table: FactBox

Configure the first installation: StandardDialog

Comprehensive Detailed ExplanationIn the context of Microsoft Dynamics 365 Business Central, page types are crucial for determining how information is presented to the user.

HeadlinePart: This page type is designed to display key data and insights in a concise and visually appealing manner, often used in Role Centers to highlight important information. It is suitable for the Housekeeping Role Center to display relevant insights.

FactBox: This page type is used to display supplementary information related to a selected record in the main part of the page. It's often used to show additional details about a record in a list, card, or document page. In this scenario, it is suitable for showing additional information about a specific Room when viewing the Room table.

StandardDialog: This is a page type that provides a modal dialog for user interaction, commonly used for setup wizards, confirmations, and input forms that require user action before proceeding. This is appropriate for configuring the first installation, where a step-by-step guided interaction is necessary.

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.

For the Install codeunit required for the extension used for installing or updating the Housekeeping app, you should use the following data type and declaration:

Data type for information: ModuleInfo

Start of the declaration of the method or procedure to perform the tasks: local procedure

In AL language, which is used for developing extensions in Business Central, an Install codeunit is a special type of codeunit that is used to handle installation or upgrade logic for an extension.

ModuleInfo is a data type that contains information about the current extension, such as its version. It is typically used within the OnInstallAppPerCompany or OnUpgradePerCompany triggers of an Install codeunit to determine if the app is being installed for the first time or upgraded.

A local procedure within an Install codeunit is a method that is only accessible within the codeunit itself. It is not visible to other objects or extensions. This is suitable for tasks that are internal to the installation process and should not be exposed globally.

These selections align with the requirements of handling installation and update procedures in a controlled and encapsulated manner within Business Central extensions.

field(3; "Receipt No."; Code[20])

{

DataClassification = CustomerContent;

TableRelation = "Purch. Rcpt. Header"."No." where ("Buy-from Vendor No." = field("Vendor No."));

}

Field Declaration:

The field(3; "Receipt No."; Code[20]) part defines the field in the table with ID 3 and type Code with a length of 20. This field will hold the receipt number.

DataClassification:

CustomerContent is selected for the DataClassification property, which categorizes the data for privacy and compliance management. This aligns with Business Central's recommendations for handling sensitive data in customer-related tables.

TableRelation Property:

The TableRelation property links the "Receipt No." field to another table, which in this case is the "Purch. Rcpt. Header" table. This ensures that only valid receipt numbers from the Purchase Receipt Header table can be selected or entered in this field.

Relation Filter:

The filter condition is applied using the where clause. It ensures that the Receipt No. is only from the Purchase Receipt Header records where the "Buy-from Vendor No." matches the "Vendor No." of the current record.

The condition field("Vendor No.") is selected from the drop-down as shown in the image. This links the vendor information in the non-conformity table to the receipt in the Purchase Receipt Header table.

By linking the "Vendor No." fields, you ensure that only receipt numbers from the correct vendor are available, which improves data consistency and reduces errors during data entry.

References to AL Language:

The TableRelation property is frequently used to create references between tables in Business Central. In this case, the correct relationship between the "Purch. Rcpt. Header" and the Non-conformity table is established using the TableRelation and filter.

Reference Documentation:

AL TableRelation Property

AL Field Syntax

 Design pattern for the setup table:

The correct selection here is Adapter. The Adapter design pattern is commonly used when you need to handle integration points or create a setup table that acts as an intermediary for data manipulation, which fits the requirement for the configuration of the non-conformity functionality.

 Data type of the primary key field:

The correct data type is Code. In Business Central, when creating a table with a primary key field, the Code data type is typically used for fields such as document numbers, codes, and identifiers. For a setup table, a Code field is appropriate for keys like "No." series or setup identifiers.

 Property required to prevent users from adding records:

The correct property is InitValue. This property is used to set initial values for fields and can be configured in such a way that users are prevented from adding records directly, typically enforcing control over record creation and editing in configuration scenarios.

codeunit 52102 "POS API Management"

{

Access = Public;

Permissions = TableData "POS Information" = rwdx;

trigger OnRun()

begin

readAPI();

end;

procedure readAPI()

begin

// Your code here to read from the POS API

end;

}

Table Structure in Business Central: When creating entities such as "non-conformity" entities in Business Central, you use document tables to represent entities that have a header and line structure. In this case, the non-conformity entity has:

A header with common information (Non-conformity Number, Date, Vendor No., etc.).

One or more lines representing the detailed information for each non-conforming item.

Document Table Usage:

Document Table: A document table is the correct table type for scenarios where you have a header (with general information like vendor details) and lines (with detailed, item-specific information).

Document tables are typically used for entities such as Sales Orders, Purchase Orders, or any other transactional data where you have both header and line information.

Supplemental Table (Option C):

Supplemental tables are usually used to add supplementary information to existing data in Business Central. In this case, we need to store detailed line information, which is a core part of the entity rather than supplementary data, so a supplemental table would not be appropriate here.

Document History Table (Option A):

Document history tables are used to track changes and historical data for entities but are not suitable for the main introduction of the entity and its lines. This option is also not appropriate.

Reference Documentation:

Introduction to Business Central Tables

Document Tables in Business Central

Read Scale-Out:

Read scale-out is a feature in Business Central that allows you to improve performance by distributing read-only queries (such as the ones from the ticketAPI) across multiple read replicas in the cloud database. This reduces the load on the primary database and helps improve the response time for read-intensive operations, like analyzing POS data through the ticketAPI.

Data Access Intent - ReadOnly:

When enabling read scale-out, you can configure the DataAccessIntent property of APIs to be ReadOnly. This directs the system to use read replicas to handle read-only queries, which enhances performance by offloading such queries from the primary database.

Why Not Other Options?

Option A (ODataReadonlyGetEnabled): This parameter is unrelated to read scale-out and primarily affects OData services behavior, not API performance tuning.

Option B (AccessByPermission): Setting the permission to Read does not directly affect the performance. It only controls access based on user permissions.

Option D (DataAccessIntent ReadOnly): While setting this property to ReadOnly helps in read-only operations, enabling read scale-out (option C) ensures the underlying infrastructure is optimized to handle such read operations, which is the fundamental action required.

Reference Documentation:

Read Scale-Out in Business Central

Data Access Intent in AL

API Publishing for Extensions:

In Business Central, when creating custom APIs like RoomsAPI, it is important to ensure that they are automatically published during the installation or upgrade of the extension.

To achieve this, you can include a codeunit of type Install in the extension that explicitly publishes the custom API (RoomsAPI) as a web service. This ensures that it is available for use immediately after the extension is deployed without requiring manual intervention.

Codeunit Type:

A codeunit of type Install runs when the extension is installed or upgraded. This type of codeunit can be used to perform setup tasks such as publishing web services or APIs like RoomsAPI.

Why Not Other Options?

Option A (default API configuration): This would not automatically publish the RoomsAPI. Default APIs do not cover custom APIs.

Option B (enable APIs for the environment): Enabling APIs in Business Central allows the standard APIs to be used, but custom APIs still need to be manually published.

Option C (publish via Web Services page): This would work but requires manual intervention to publish RoomsAPI, which does not fulfill the requirement of automatic publishing during installation.

Reference Documentation:

Publishing APIs in Extensions

Codeunit Types in Business Central

var

TempBlob: Codeunit "Temp Blob";

IncidentOutStream: OutStream;

IncidentInStream: InStream;

ImageFilter, FileName: Text;

begin

// Initialize the TempBlob and streams

TempBlob.CreateOutStream(IncidentOutStream);

Rec.Image.ExportStream(IncidentOutStream); // 'Rec' refers to the current Room Incident record

TempBlob.CreateInStream(IncidentInStream);

// Set the filters and filename for the image

ImageFilter := 'Image Files (*.bmp,*.jpg,*.jpeg,*.gif)|*.bmp;*.jpg;*.jpeg;*.gif';

FileName := 'Customer Picture';

// Prompt the user to download the image

if not DownloadFromStream(IncidentInStream, '', 'Download Incident Picture', '', ImageFilter, FileName) then

Error('Unable to download the image.');

end;

https://api.businesscentral.dynamics.com/v2.6/myTenant/myEnvironment/api/alpine/integration/rooms

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;

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.

 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.

Here is the most logical sequence of actions for implementing the Issue Management module in Business Central and exposing the PostIssue method:

Correct Order:

Create a codeunit named "Issue Management Impl." and set the value of Access property to Internal.

This is the first step because Issue Management Impl. is the implementation layer where the actual business logic resides, and setting it to Internal ensures that it is only accessible from within the module, following best practices in encapsulation.

Create a local procedure named PostIssueImpl in the "Issue Management Impl." codeunit.

This step adds the actual PostIssueImpl method, which contains the core logic of posting an issue.

Create a codeunit named "Issue Management" and set the value of Access property to Public.

After defining the implementation logic, you need to create a public-facing Issue Management codeunit to expose the service externally.

Create a PostIssue procedure in the "Issue Management" codeunit, and in it call the PostIssueImpl method.

Lastly, expose the PostIssue method in the Issue Management codeunit, which will internally call the PostIssueImpl method, completing the chain.

Load the report for users in a specific location: OnInitReport

Validate data before processing: OnPreReport

Define filter based on Department field: OnPreDataItem

The requirements for the report are:

The report must be loaded for users in a specific location only.

Data entered in the request page must be validated before any further processing.

A filter must be defined for users based on the Department field defined in user setup.

Trigger Matching:

The report must be loaded for users in a specific location only.The correct trigger for loading the report is OnInitReport.

This trigger runs when the report is initialized, and you can use it to define user-specific loading conditions, like location-based filtering.

Data entered in the request page must be validated before any further processing.The correct trigger for validation before processing is OnPreReport.

This trigger occurs before the report is run and can be used for data validation before further processing begins.

A filter must be defined for users based on the Department field defined in user setup.The correct trigger to define filters is OnPreDataItem.

This trigger occurs before data item processing begins and is used to apply filters such as those based on the Department field in the user setup.

KQL Code Segment:

First command (traces):

The query begins with traces to analyze telemetry data logs. The next command determines how the results are filtered or displayed.

take 100: This is the correct option to retrieve the top 100 rows from the traces table.

Command for selecting fields:

project: This command is used to select specific fields from the telemetry data, allowing you to retrieve and display only the fields relevant to the job queue telemetry.

The correct answer is project, as it allows you to choose fields like jobQueueObjectId, jobQueueObjectType, etc., from the customDimensions table.

Permission sets control access to objects (such as pages, tables, reports) in Business Central. By creating a new permission set that specifically excludes the critical table (or page) and assigning this permission set to the users in Department A, you can prevent them from accessing the page.

Option A (creating a different role center page) is incorrect because role centers control the user interface, but do not directly restrict access to specific pages or tables.

Option B and Option C (extending the base application permission set) are not the best options because extending permission sets typically involves adding permissions, not removing access. The question requires restricting access to a critical page, so simply including or excluding permission sets won’t solve the issue at the table or page level.

Option D (creating an entitlement object) is not relevant here, as entitlements are used in more complex licensing scenarios or environments.

Summary:

Creating a permission set object that specifically excludes access to the critical table or page and assigning it to the users will solve the problem effectively.

Using InherentPermissions in an event subscriber with the specified syntax could potentially resolve the permission issues related to MyTable, provided that the permissions specified (in this case, 'R' for Read) align with the minimum necessary for the users to perform their tasks. This approach allows the app to grant permissions dynamically based on the context of the event subscriber, which in this case is involved with inserting data into MyTable. By granting Read permission at the event level, it ensures that users have the necessary permissions to interact with MyTable in the context of the operations facilitated by the event subscriber, without needing to alter existing permission sets or grant broader permissions than necessary. This solution adheres to the principle of least privilege by ensuring that permissions are granted only within the narrow scope needed for specific operations, thereby potentially resolving the reported user issues in a secure and controlled manner.

When exporting data from Business Central and the requirement is for the data to be in a non-fixed length and width CSV format, the Format property of the XMLport should be set to VariableText (B). The VariableText format is designed for handling data exports where the fields are separated by a delimiter, such as a comma or tab, which is typical of CSV (Comma-Separated Values) files. This format allows for the flexibility needed when dealing with varying field lengths, as it does not enforce a fixed width for each field, making it ideal for CSV data exports. Setting the Format property to FixedText (C) would enforce a fixed width for each field, which is not suitable for CSV files, while the XML format (A) is used for exporting data in an XML structure, which is different from the CSV format requirements.

You are customizing Business Central using Visual Studio Code and JSON files for configuration.

You plan to:

Open page 21 after publishing.

Enable debugging.

Disable the capability to download the source code.

Which configurations should you add?

The options involve two primary JSON files: launch.json and app.json, and configuration tags like startupObjectId and resourceExposurePolicy.

To prevent a caption from being translated in an extension for Microsoft Dynamics 365 Business Central, you should add the Locked = true parameter to the Caption (C). This parameter explicitly marks the caption as locked for translation, ensuring that it remains unchanged across different language versions of the extension. This approach is useful for specific terms, brand names, or other elements within the application that should remain consistent regardless of the user's language settings. Unlike the other options, which involve manual manipulation of the translation file or properties, setting Locked = true directly in the AL code provides a clear, maintainable, and error-proof method to exclude specific captions from the translation process.

When developing an app for Microsoft AppSource, it is crucial to adhere to specific guidelines and standards to ensure compatibility and compliance. The three code analyzers you should activate are:

CodeCop (A): This is the default analyzer for AL language extensions. It enforces the AL Coding Guidelines, ensuring that the code follows best practices for readability, maintainability, and performance. It checks for a wide range of issues, from syntax errors to best practice violations, making it essential for any AL development.

PerTenantExtensionCop (D): This analyzer is specifically designed for extensions that are intended to be installed for individual tenants. It includes rules that ensure the extension does not interfere with the per-tenant customizations and adheres to the guidelines for extensions that can be safely installed and uninstalled without affecting the underlying application.

AppSourceCop (E): This analyzer is tailored for extensions that are intended for publication on Microsoft AppSource. It enforces additional rules that are specific to AppSource submissions, such as checking for the use of reserved object ranges and ensuring that all prerequisite dependencies are correctly declared. This is crucial for ensuring that your app meets all the requirements for listing on AppSource.

By activating these three analyzers, developers can ensure their app adheres to the standards required for AppSource, as well as maintain high code quality and compatibility with Business Central.