Free Preparation Discussions
MENU
Microsoft MB-820 Exam
- Topic 1: Describe Business Central: Describing the components and capabilities of Business Central, describing the core solution and extensions approach for Business Central are focal points of this topic. It also explains the difference between Business Central Online and Business Central on-premises features.
- Topic 2: Install, develop, and deploy for Business Central: It delves into installation and configuration of a Business Central development environment. Moreover, it discusses creating, debugging, and deploying an extension in Business Central.
- Topic 3: Develop by using AL objects: Building and extending tables and reports is discussed in this topic. It also explains Designing and creating an XMLport. Lastly it discusses how to work with entitlement and permission set objects.
- Topic 4: Develop by using AL: How to Customize the UI experience and Use AL for business central extension is discussed here. It also delves into explaining the essential development standards.
- Topic 5: Work with development tools: Implementing semi-automated test processes and managing and assessing telemetry are its sub-topics.
- Topic 6: Integrate Business Central with other applications: Accessing Representational State Transfer (REST) services is discussed in this topic. It also explains implementation of APIs.
Free Microsoft MB-820 Exam Actual Questions
The questions for MB-820 were last updated On Apr. 29, 2024
You create a page with the PageType property set to RoleCenter.
You navigate through the different sections of the page.
You need to add functionalities to the page.
What should you do?
When creating a page with the PageType property set to RoleCenter in Microsoft Dynamics 365 Business Central, it's essential to organize the functionalities and actions in a manner that enhances user experience and efficiency. The best practice is to define actions in the area (reporting) before actions in the area (creation) (A). This organization allows users to access reporting and analytical features quickly, which are commonly used in Role Centers for overview and insight purposes, before moving on to creation or transactional tasks. This logical flow aligns with typical user workflows, where analysis and review precede the creation of new records or transactions. The other options, such as defining the navigation menu in the area(processing) (B), defining the navigation bar in the area (embedding) (C), or adding a source table on the Role Center page (D), do not directly address the need to add functionalities to the Role Center page in a user-friendly manner.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question set might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company creates a Business Central app and a table named MyTable to store records when sales orders are posted.
Users report the following issues:
* The users receive permission errors related to MyTable.
* Users are no longer able to post sales orders since installing the new app.
* The users cannot access the list page created in MyTable.
You need to resolve the user issues without creating new permission sets. You must use the principle of least privilege.
Solution: Decorate the event subscriber used for inserting data in MyTable by entering (lnherentPermissions(PermissionOb]ectType:TableDat
a. Database:MyTable. 'R')]
Does the solution meet the goal?
Using InherentPermissions in an event subscriber with the specified syntax could potentially resolve the permission issues related to MyTable, provided that the permissions specified (in this case, 'R' for Read) align with the minimum necessary for the users to perform their tasks. This approach allows the app to grant permissions dynamically based on the context of the event subscriber, which in this case is involved with inserting data into MyTable. By granting Read permission at the event level, it ensures that users have the necessary permissions to interact with MyTable in the context of the operations facilitated by the event subscriber, without needing to alter existing permission sets or grant broader permissions than necessary. This solution adheres to the principle of least privilege by ensuring that permissions are granted only within the narrow scope needed for specific operations, thereby potentially resolving the reported user issues in a secure and controlled manner.
A company uses Business Central.
The company plans to use a translation file in an extension. The extension has a caption that should not be translated.
You need to prevent the caption from being translated.
What should you do?
To prevent a caption from being translated in an extension for Microsoft Dynamics 365 Business Central, you should add the Locked = true parameter to the Caption (C). This parameter explicitly marks the caption as locked for translation, ensuring that it remains unchanged across different language versions of the extension. This approach is useful for specific terms, brand names, or other elements within the application that should remain consistent regardless of the user's language settings. Unlike the other options, which involve manual manipulation of the translation file or properties, setting Locked = true directly in the AL code provides a clear, maintainable, and error-proof method to exclude specific captions from the translation process.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question set might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company creates a Business Central app and a table named MyTable to store records when sales orders are posted.
Users report the following issues:
* The users receive permission errors related to MyTable.
* Users are no longer able to post sales orders since installing the new app.
* The users cannot access the list page created in MyTable.
You need to resolve the user issues without creating new permission sets. You must use the principle of least privilege.
Solution: Decorate the event subscriber used for inserting data in MyTable by entering (lnherentPermissions(PermissionOb]ectType:TableDat
a. Database:MyTable. 'R')]
Does the solution meet the goal?
Using InherentPermissions in an event subscriber with the specified syntax could potentially resolve the permission issues related to MyTable, provided that the permissions specified (in this case, 'R' for Read) align with the minimum necessary for the users to perform their tasks. This approach allows the app to grant permissions dynamically based on the context of the event subscriber, which in this case is involved with inserting data into MyTable. By granting Read permission at the event level, it ensures that users have the necessary permissions to interact with MyTable in the context of the operations facilitated by the event subscriber, without needing to alter existing permission sets or grant broader permissions than necessary. This solution adheres to the principle of least privilege by ensuring that permissions are granted only within the narrow scope needed for specific operations, thereby potentially resolving the reported user issues in a secure and controlled manner.
You need to call the Issue API action from the mobile application.
Which action should you use?
In the context provided by the case study, when calling an API action from a mobile application, the correct format for a POST request to an action in Business Central typically involves specifying the entity (/issues), the ID of the entity (88122e0e-5796-ec11-bb87-000d3a392eb5), and the action to be called (/Copy). The action name should match the exact name as defined in the AL code, which is case-sensitive.
Option A is incorrect because it uses a non-standard format for the action call.
Option B uses the PATCH method, which is generally used for update operations, not for calling actions.
Option C is correct as it uses the POST method, which is appropriate for calling actions, and correctly specifies the entity, ID, and action name.
Option D is incorrect because the action name /copy is in lowercase, while AL is case-sensitive, and it should match the case exactly as defined in the code.
Option E incorrectly adds 'MicrosoftNAV' before the action name, which is not standard for calling actions in Business Central APIs.
Hence, the correct action to use when calling the Issue API action from the mobile application is given in Option C.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Currently there are no comments in this discussion, be the first to comment!