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

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

You are working on an on-premises Business Central instance and unable to download symbols for a new AL project. The current configuration in launch.json does not allow you to download symbols, and you need to make corrections.

Key Points in the Scenario:

Instance name is TEST.

Developer services port is 7149.

Windows authentication is being used.

Correct Answers:

A. Change the server Instance parameter to TEST.

The serverInstance parameter must match the name of the Business Central instance, which is TEST in this scenario. You need to modify this to reflect the correct instance name.

B. Add the port: 7149 parameter.

Since the developer services are using port 7149, you need to specify this in the launch.json file by adding the port parameter with the value 7149.

Incorrect Options:

C. Change the name parameter to TEST: The name parameter is just a label and does not affect downloading symbols, so changing this won't help.

D. Change the authentication parameter to UserPassword: The authentication method is already set to Windows, which is valid for this scenario. Changing it to UserPassword is unnecessary unless specified by the system.

E. Check which server the instance is installed on and replace http://localhost with the correct IP address: Since the server is on the same machine as Visual Studio Code (as specified), localhost is correct.

Language table → System layer

Activities Cue table → Base layer

Extension Management codeunit → System layer

Business Unit Card page → Base layer

Application Layers in Business Central:

In Business Central, there are different layers such as Base and System, which represent different levels of the application architecture. Here's a breakdown of where each object is likely to belong based on typical Business Central architecture:

Language Table:This table typically belongs to the System layer, as language and localization features are often part of the foundational aspects of the system.

Activities Cue Table:This would likely be found in the Base layer because it involves business logic that supports user interface elements (like activity cues) specific to the Business Central application.

Extension Management Codeunit:The Extension Management Codeunit likely belongs to the System layer, as it deals with handling extensions, which is closely related to the core system functionality for managing and deploying changes.

Business Unit Card Page:This object would typically be part of the Base layer, as it is a business-specific object that handles the user interface for business unit data, part of the core Business Central application.

Runs when the report is loaded: OnInitReport

Runs when the data item has been iterated for the last time: OnPostDataItem

Use this function to skip the rest of the report: CurrReport.Quit()

1. Requirement: Runs when the report is loaded.

Selection: OnInitReport

Reasoning: The OnInitReport trigger is the very first event that fires when the report object is instantiated (loaded). It runs before the request page is displayed, making it the correct choice for "when the report is loaded."

Contrast: OnPreReport runs after the request page, just before the data processing starts.

2. Requirement: Runs when the data item has been iterated for the last time.

Selection: OnPostDataItem

Reasoning: The OnPostDataItem trigger executes immediately after the report has finished iterating through all records belonging to that specific data item.

Contrast: OnPreDataItem runs before the loop starts, and OnAfterGetRecord runs repeatedly during the loop (for every record).

3. Requirement: Use this function to skip the rest of the report.

Selection: CurrReport.Quit()

Reasoning: The CurrReport.Quit() function completely aborts the execution of the report, effectively "skipping" everything else remaining in the report logic.

Contrast: CurrReport.Skip() only skips the current record processing and moves to the next record. CurrReport.Break() exits the current data item loop but proceeds to the next data item (if any) or finishes the report normally.

To roll back changes to a test method after run time, you should:

Set the TransactionModel attribute to AutoRollback.

To run an approve action on a test page named TestPageA, you should:

Configure TestPageA.Approve.Invoke().

In Business Central's testing framework, the TransactionModel attribute can be set to AutoRollback. This ensures that any changes made during the test are rolled back after the test is complete, leaving the database in its original state.

For running an action on a test page, you would use the 'Invoke' method on the action you wish to perform. In this case, to run an approve action on TestPageA, you would use TestPageA.Approve.Invoke() within your test codeunit. This simulates the user action of approving something on the page.

These actions ensure that the testing environment is properly set up to test specific functionalities without persisting test data and to invoke actions as part of the test scenarios.

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

ï‚· 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.

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