Microsoft Updated MB-820 Exam Questions and Answers by mario

SharedLayout = true allows for the layout to be shared across views, and it is often used when defining a custom layout that should follow specific filtering conditions.

The Filters property specifies the exact filter criteria for the view, in this case, filtering on Balance > 500 and the Currency Code = LCY (local currency).

A uses incorrect filter syntax and shareLayout = false, which doesn't allow the layout to be shared, so it’s not ideal for this use case.

C and D both have issues with the filter syntax and do not use proper Currency Code filtering or share layout settings.

For more details, check Creating Views in Business Central.

A user observes error messages such as:

"Unhandled UI: Message"

"Unhandled UI: Confirm"

These messages indicate that the test code is not handling system prompts like Message and Confirm dialogs, which can appear during test execution.

Options Explanation:

Message Handler and Confirm Handler methods are used to intercept and handle these UI prompts during automated testing.

These methods should be added to the test runner codeunit, which is responsible for running the tests and handling these system-level interactions.

For a task that is performed infrequently and requires users to follow a sequence of steps, a wizard-like interface is ideal. In Microsoft Dynamics 365 Business Central, the NavigatePage page type (A) is best suited for this purpose. NavigatePage is designed to guide users through a series of steps or pages, allowing them to complete a task by making choices or entering data in a structured manner. This page type is often used for setup wizards, data migration tasks, or any other process that benefits from a step-by-step approach. Unlike the other page types like Card (B), RoleCenter (C), or List (D), NavigatePage specifically supports the navigation and decision-making flow required for wizard creation, making it the optimal choice for this requirement.