MB-820 Practice Questions

The goal is to log a failure in a business process that includes specific error reasons ("critical error in code").

1. Verbosity: Since the process has failed due to a critical error, the Verbosity::Critical level is the most appropriate to ensure it is prioritized in monitoring tools.
2. DataClassification: The CustDimension dictionary contains the value "Process failed," which is a result of a user-initiated business process. Under Business Central's data privacy standards, data generated by the customer's use of the system is classified as CustomerContent.
3. TelemetryScope: Setting the scope to All ensures the signal is sent to both the environment telemetry (monitored by the partner/customer) and the Microsoft telemetry pipeline.

Microsoft Learn: LogMessage Method (Session). Link.

Microsoft Learn: Instrumenting an Extension for Telemetry. Link.

Microsoft Learn: Classifying Data in Business Central. Link. Section: "Data Classification types".

Microsoft Dynamics 365 Business Central Documentation: Telemetry Scope and Verbosity Levels (v24.0+).

The code segment is designed to sample and then shape telemetry data from the traces table.

1. Box 1: The keyword take (or its alias limit) is used to return up to the specified number of rows (100) to provide a quick sample of the data. While top requires a sort order and extend/project manipulate columns, take is the standard KQL operator for simple row limitation.
2. Box 2: The keyword project is used to select specific columns (timestamp, jobQueueObjectId, etc.) to include in the result set. extend would add new columns to the existing set, whereas the subsequent comma-separated list indicates a selection of specific fields, which is the primary function of project.

Microsoft Learn (Azure Monitor): "Kusto Query Language (KQL) overview - take operator." Microsoft Documentation

Microsoft Learn (Azure Monitor): "Kusto Query Language (KQL) overview - project operator." Microsoft Documentation

Microsoft Learn (Business Central): "Analyzing Job Queue Telemetry in Application Insights." Business Central Developer Documentation

Microsoft Learn (Azure Monitor): "Best practices for Kusto Query Language - Sampling data." KQL Best Practices

To create an API in Business Central:

1. Object Definition: An API is defined using the page object type. query objects can also be used for APIs, but the snippet includes layout and area(Content) blocks, which are specific to Page objects.
2. PageType: For an object to be exposed as an OData v4 web service endpoint, the PageType property must be explicitly set to API.
3. DataAccessIntent: The snippet includes properties Editable = false;, InsertAllowed = false;, and ModifyAllowed = false;. This indicates a read-only requirement. Setting DataAccessIntent to ReadOnly optimizes performance by routing the request to a read-only database replica.

Microsoft Learn: API Page Type. Describes the structure of API pages in AL. [Section: API Page Properties]

Microsoft Learn: DataAccessIntent Property. Explains using ReadOnly to improve performance for non-transformative data requests. [Property: DataAccessIntent]

Microsoft Dynamics 365 Business Central Documentation: Developing Connect Apps for Dynamics 365 Business Central. [Developing APIs]

To prevent breaking dependent extensions, Microsoft mandates a phased approach. In the first version (2.0.0.0), the field and procedure must be marked as ObsoleteState = Pending. This issues a compilation warning to other developers, allowing them time to refactor their code without the extension failing to load. Only in a subsequent version (2.0.0.1) can the objects be fully removed or set to Removed. Using ObsoleteState = Removed or physical removal in the initial version would cause immediate "breaking changes," violating the requirement to handle removal "without breaking other extensions."

Microsoft Learn (Official Documentation): Deprecated Features in AL - Section: "Best practices for deprecating code". URL: Microsoft Docs - Deprecating AL Code

Microsoft Learn (Official Documentation): ObsoleteState Property - Details on Pending vs Removed states. URL: Microsoft Docs - ObsoleteState Property

Business Central Developer Guide: AppSourceCop Breaking Changes - Rule AS0001 and AS0002 regarding the removal of fields and procedures across versions.

OnPreXmlItem: This trigger executes just before an XMLport data item (table) is processed. It is the standard location to programmatically apply filters or set the DataItemLink property via code to establish a relationship between a child table (e.g., Item Unit of Measure) and its parent (e.g., Item).

OnPostXmlPort: This trigger fires after the entire XMLport has finished its execution and closed the file. It is the appropriate place to use a Message() function to notify the user that the process has completed successfully.

Microsoft Learn: XMLport Triggers. This documentation outlines the execution order, specifically identifying OnPostXmlPort as the final trigger after the import/export is complete.

Source: XMLport Triggers - Business Central | Microsoft Learn

Microsoft Learn: OnPreXmlItem (XMLport) Trigger. Defines this trigger as the point to set filters and links before records are fetched.

Source: OnPreXmlItem Trigger - Business Central | Microsoft Learn

Microsoft Learn: OnPostXmlPort (XMLport) Trigger. Confirms usage for post-processing tasks like user notifications.

Source: OnPostXmlPort Trigger - Business Central | Microsoft Learn

The goal is to create a codeunit to manage POS terminal APIs efficiently within an extension.

1. Access Property: Setting Access = Internal is the best practice for codeunits that provide logic meant to be used only within the current extension. It prevents other extensions from calling these procedures, maintaining encapsulation. Public would expose it globally, which is often unnecessary for internal API management.
2. Procedure Declaration: The OnRun trigger calls readAPI(); without passing any arguments. Therefore, the procedure must be defined as procedure readAPI() to match the signature of the call. The var prefix is used for parameter definitions, not the procedure name itself, and providing an integer parameter would cause a compilation error due to a signature mismatch.

Microsoft Learn: Codeunit Object - Documentation on properties and triggers. Access Property in AL

Microsoft Learn: AL Simple Statements - Explaining procedure calls and parameter matching. Procedures in AL

Microsoft Dynamics 365 Business Central Development: Best Practices for Extension Development - Guidance on encapsulation and access modifiers.

In Business Central AL development:

• launch.json is used to configure the debugging and publishing settings. It specifically contains the startupObjectType and startupObjectId properties, which define which page or report opens automatically when you publish the extension.
• app.json is the manifest file for the extension. It defines the extension's core metadata, including the runtime version (which specifies the platform version the extension targets) and the dependencies array (which lists other extensions that this app relies upon).
• rad.json (Rapid Application Development) is used for incremental metadata updates and does not store these specific configuration properties.

Microsoft Learn (Official Vendor Documentation): JSON Files - app.json and launch.json. This section details that app.json contains information about the extension such as runtime and dependencies.

Microsoft Learn: Launch.json file. Explains that this file contains settings for debugging, including startupObjectType and startupObjectId.

Microsoft AL Language Reference: App.json File Reference. Explicitly lists runtime and dependencies as valid properties within the app.json schema.

Microsoft AL Language Reference: Launch.json File Reference. Confirms the placement of startup object configurations within the launch settings.

The debugger fails to start because the system cannot uniquely identify the user session to attach to. Dynamics 365 Finance and Operations authenticates users against Azure Active Directory (AAD). In AAD, the primary and globally unique identifier for any user object is its Object ID, which is a GUID. When initiating a debugging session for a specific user via a URL parameter such as userId, providing the user's alias (username) can be ambiguous. The system requires the immutable GUID to reliably and uniquely resolve the user principal and attach the debugger to the correct session. Using the wrong identifier format is a fundamental error that prevents the process from starting.

B: The breakOnNext parameter is a trigger, typically set to 1, to break on the next request. A specific value like -WebServiceClient is for specialized scenarios (e.g., debugging web services) and is not a general requirement for starting a user session debugger.

C: This option describes a sequence of events rather than a cause for failure. Furthermore, it incorrectly suggests that the breakOnNext parameter specifies a user session, which is the role of the userId or user parameter.

D: The executionContext is not a standard or documented URL parameter for controlling debugger behavior in Dynamics 365 Finance and Operations. The primary parameter to enable debugging is debug=vs.

1. User Identity and Azure AD: Official Microsoft documentation states that Finance and Operations apps use Azure Active Directory for authentication. Each user in AAD has a unique, immutable identifier called the Object ID (a GUID), which is the authoritative identifier for the user principal.

Source: Microsoft Learn. "Security architecture". Finance and Operations apps documentation. Section: "Authentication".

2. Debugging Specific User Sessions: While documentation often shows using the SysUserSessionDebug class runner (which prompts for the string User ID) or the snapshot debugger (&user=), the underlying principle of uniquely identifying the AAD principal remains. For a direct parameter-based approach like the one implied in the question, using the most precise identifier (GUID) is a logical requirement to avoid ambiguity.

Source: Microsoft Learn. "Debug X++ code by using the debugger in Visual Studio". Finance and Operations apps documentation. Section: "Debug a specific user's session".

3. Azure AD User Object Properties: The core Azure AD documentation specifies that the objectId is the unique identifier for a directory object. This reinforces the concept that the GUID is the primary key for a user.

Source: Microsoft Graph REST API v1.0 reference. "user resource type". Microsoft Graph documentation. Property: id (The unique identifier for the user. This is the user's objectId).

In Business Central Query objects, the SqlJoinType determines how data items are combined:

1. LeftOuterJoin: This type is used when you need to include every record from the "left" (starting/upper) table, regardless of whether a matching record exists in the "right" (linked/lower) table. This satisfies the requirement to keep all records from TableA Header even if TableA Line is empty.
2. InnerJoin: This type returns records only when there is a match in both the primary and the linked tables. This satisfies the requirement to return records from TableB Header only where a matching TableB Line exists.

Microsoft Learn (Official Documentation): SqlJoinType Property. This section defines LeftOuterJoin as a "left outer join" where the result contains all records from the starting table and matching records from the linked table. It defines InnerJoin as a join where a record is only included if there is a match between the data items.

Reference: MS Learn - SqlJoinType Property

Microsoft Learn (Official Documentation): Query Object. Details how the dataset is built using T-SQL equivalents in the AL Language.

Reference: MS Learn - Query Object

Dynamics 365 Business Central Development Standards: Document tables (Header/Line) typically utilize LeftOuterJoin for reporting to ensure headers are not lost if lines haven't been created, whereas history audits often use InnerJoin to verify transaction completion.

The target dataset shows a strict intersection: it excludes Vendor V0003 (who has no items) and Item 1004 (whose vendor V0004 does not exist in the Vendor table).

1. dataitem(Vendor; Vendor): Establishes the primary table.
2. dataitem(Item; Item): Establishes the child table to be joined.
3. SqlJoinType = InnerJoin;: This is the critical block. An Inner Join ensures that only records appearing in both tables are included in the output. If LeftOuterJoin were used, "Relecloud" would appear with blank item details; if RightOuterJoin were used, the "Bed" would appear with blank vendor details.

Microsoft Learn (Dynamics 365 Business Central): Query Object - Specifies that a query must contain at least one dataitem and explains the hierarchy of nested data items.

Microsoft Learn (AL Language Reference): SqlJoinType Property - "InnerJoin" returns a row only if there is a match between the fields in the DataItemLink.

Microsoft Docs: Developing Queries in AL - Outlines the structure of query objects where properties like SqlJoinType are defined within the scope of the child dataitem.