Online Access Free MB-820 Exam Questions

A company plans to optimize its permission sets.
The company has the following permission sets:

You need to provide the following implementation for a third permission set:
* Create a new Permission Set C that is a composite of Permission Set A and Permission Set B.
* Assign Permission Set C to a user.
You need to ensure that the user has only read access to the Job table.
Solution: Set the IncludedPermissionSets property to Permission Set B and the ExcludedPermissionSets property to Permission Set A.
Does the solution meet the goal?

• A.No
• B.Yes

You need to improve performance when ticketAPI is used to analyze the POS data. What should you do?

• A.Enable read scale-out on the Business Central database.
• B.Set the DataAccesslntent property to Readonly on the ticketAPI API page.
• C.Set the ODataReadonlyGetEnabled parameter to True in the Business Central admin center.
• D.Set the AceesByPermission property to Read on the ticketAPI API page.

You are customizing Business Central by using Visual Studio Code. You create a project that will extend Business Central. The AL extension contains JSON files, which are automatically generated and are used to store configuration data For testing purposes, you plan to add the following changes to the files:
* Specify that page 21 must be opened after publishing.
* Enable debugging
* Disable the capability to download the source code
You need to add the configurations to the JSON files.
Which two configurations should you add? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.

• A.In the " resourceExposurePolicy " tag, set " allowDebugging " : true and " allowDownloadingSource " :
  false on appjson.
• B.Set " startupObjectld " : 27 on launchjson.
• C.In the " resourceExposurePolicy " tag, set " at low Debugging " . true and allowDownloadingSource " :
  false on launchjson.
• D.Set " start upObjectld " : 27 on appjson.
• E.In the " resourceExposurePolicy " tag, set " allowDebugging " : true and " allowDown loading Source ":
  true on appjson.

You need to define the properties of the comments field of the Non-conformity page.
How should you complete the code segment? To answer, select the appropriate options in the answer area.
NOTE; Each correct selection is worth one point.

Correct Answer:

Explanation:

You need to handle the removal of the Description field and the Clone procedure without breaking other extensions.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.

Correct Answer:

Explanation:
In Business Central, when you need to handle the removal of fields and procedures to ensure that other extensions are not affected by these changes, you typically follow a two-step deprecation process. This allows other developers and users to adapt to the changes before they are fully enforced. Here are the steps to handle the removal:
* Mark as Obsolete : In the first version where the decision to remove the field or procedure is made, you set the ObsoleteState to Pending and provide an ObsoleteReason . This doesn ' t remove the feature but indicates to users and developers that it will be removed in the future. This step is crucial for backward compatibility.
* Removal : In a subsequent version, after users have had time to adapt to the deprecation warning, you can then remove the field or procedure or set the ObsoleteState to Removed .
Based on these guidelines, here are the three actions you should perform in sequence:
* Set the Description field as ObsoleteState = Pending and ObsoleteReason = ' Not in use ' in version
2.0.0.0.
* Set the Clone procedure as ObsoleteState = Pending and ObsoleteReason = ' Not in use ' in version
2.0.0.0.
* Remove the Description field from the Issue table in version 2.0.0.1.
These steps will ensure that anyone using the Description field or Clone procedure will receive a warning about the pending deprecation before it is actually removed, thereby minimizing the impact on other extensions and providing a clear path for migration.
When handling the removal of fields and procedures in Microsoft Dynamics 365 Business Central, the process should be carried out in a way that allows other extensions or dependent features to adapt to the changes without causing immediate failures.
* Set Obsolete State and Reason for Description Field (Version 2.0.0.0): The first step involves marking the Description field as obsolete by setting the ObsoleteState to ' Pending ' . This is a non-breaking change, signaling to other developers and users that the field is planned for removal in a future version.
An ObsoleteReason should also be provided to explain why the field is being deprecated.
* Set Obsolete State and Reason for Clone Procedure (Version 2.0.0.0): Similarly, the Clone procedure should be marked as obsolete with the ObsoleteState set to ' Pending ' . This indicates that the procedure is no longer in use and will be removed in the future. Providing an ObsoleteReason is best practice as it explains the rationale behind the decision.
* Remove the Description Field (Version 2.0.0.1): In the subsequent version, after the developers and users have been given time to adapt to the deprecation notice, the Description field can be safely removed from the Issue table. This is considered a breaking change, hence it is done after the field has been marked as obsolete in a previous version.
The reason for not removing the Description field and Clone procedure immediately in version 2.0.0.0 is to avoid causing runtime errors for any extensions or integrations that may depend on these components. By following this sequence, you provide a clear deprecation path that helps maintain the stability of the overall system while evolving the schema.