MB-820 Exam Dumps - Microsoft Dynamics 365 Business Central Developer

The telemetry trace sends custom signals to an Application Insights resource specified in the extension's app.json file and on the tenant. = YES

Dictionary keys for the extension name and version must be specified to identify the extension during analysis. = YES

The telemetry trace sends events to Application Insights resources set up on the tenant. = YES

Telemetry in Business Central allows developers to collect custom telemetry for extensions using Application Insights. The telemetry trace is used to send custom signals to an Application Insights resource. This resource is typically specified in the app.json file of the extension and must be configured on the tenant where the extension is installed.

The use of dictionary keys for the extension name and version is a best practice to identify the extension during analysis in Application Insights. These keys can be added to the telemetry trace to ensure that when the data is collected, it's clear which extension the data is associated with.

Finally, it is correct that the telemetry trace sends events to Application Insights resources that are set up on the tenant, enabling the collection and analysis of telemetry at the tenant level.

In a single-tenant deployment architecture of Business Central on-premises, the following characteristics describe how the data is stored and how the Business Central Server is configured:

The application and the business data are stored in the same database (B): In a single-tenant architecture, each tenant (which typically corresponds to a single customer) has its own dedicated database. This database contains both the application objects (such as pages, reports, codeunits, etc.) and the business data (such as customer, vendor, and transaction records). This setup ensures that each tenant's data is isolated and can be managed independently.

The application and business data are stored in separate databases (D): While (B) is a characteristic of a single-tenant deployment, it's important to clarify that in some configurations, the application objects can be stored in a separate database from the business data. This approach can be used for easier maintenance and upgrades of the application code without affecting the business data. However, each tenant still has its own set of databases, maintaining the single-tenancy model.

The other options provided do not accurately describe a single-tenant architecture:

Each customer has their own Business Central Server (A): This statement might be misleading. In a single-tenant deployment, while each customer has their own database, they do not necessarily have their own Business Central Server instance. Multiple databases (tenants) can be hosted on a single server instance, although they are not shared across customers.

Multiple customers share a single Business Central Server (C) and Multiple customers share multiple Business Central Server instances (E): These options describe a multi-tenant architecture rather than a single-tenant one. In a multi-tenant setup, multiple customers (tenants) can share the same server instance and even the same application database, with data isolation ensured at the application level.

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.

To ensure the most recent Business Central artifact URL is selected for setting up a local Business Central Development Docker container, the command to use is Get-BcArtifactUrl -type sandbox -select Current (A). This PowerShell command retrieves the URL for the latest available Business Central artifact for a sandbox environment, ensuring that the Docker container is set up with the most up-to-date version for testing new project ideas. The -select Current parameter is crucial as it specifies that the current, or latest, version of the artifact is to be retrieved, as opposed to selecting a version based on other criteria such as Closest, NextMinor, or NextMajor.

A. Codeunit

Codeunits can be extended in AL to add or modify functionality in Business Central.

B. Report

Reports can also be extended to customize the format or data presented in the reports without modifying the base report.

Incorrect Options:

C. Query: Queries cannot be extended. You would need to create new queries or modify the existing ones directly.

D. API page: You cannot extend API pages, but you can create new API pages.

E. Enum: You cannot extend Enums because they are predefined sets of values.