Microsoft MB-820 Exam Dumps

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.

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.

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.

To enable debugging in an extension and allow the source code to be viewed, the allowDebugging property should be specified in the app.json file (C). The app.json file serves as the manifest for an AL project in Microsoft Dynamics 365 Business Central, defining the project's properties, dependencies, and features. By setting the allowDebugging property to true in this file, developers enable the debugging of the extension's source code, facilitating troubleshooting and development. This is essential for analyzing the behavior of the extension and identifying issues during the development process.

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