Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam MB-820 Topic 4 Question 17 Discussion

Actual exam question for Microsoft's MB-820 exam
Question #: 17
Topic #: 4
[All MB-820 Questions]

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 sets 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 lo 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: In the MyTable object add the property InherentPermissions = Rl. Does the solution meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: B

The property InherentPermissions is used to automatically grant permissions to the table object it is applied to, but setting it to Rl (which seems to be a typo and should likely be 'RL' for Read and Insert permissions) is not sufficient in this scenario. The issues reported by the users suggest that they need more than just read and insert permissions on MyTable. Since users are unable to post sales orders, they likely need Modify, Delete, or Execute permissions on certain tables or objects related to the sales order process. Additionally, the inability to access the list page created in MyTable could be due to lacking Read permissions on other related objects or pages. Therefore, merely setting InherentPermissions = RL on MyTable does not comprehensively address the users' permission issues, especially when considering the principle of least privilege. A more tailored approach to permissions, potentially involving adjustments to the app's code or configuration to ensure proper permissions are applied where necessary, would be needed.


Contribute your Thoughts:

Shanda
4 months ago
Ah, the old 'InherentPermissions' trick! This should do the trick and keep things simple. No need to make it more complex than it needs to be.
upvoted 0 times
...
Mari
4 months ago
No, I don't think that solution will work. We need to consider other options.
upvoted 0 times
...
Francine
4 months ago
This is a good solution. Applying the principle of least privilege, we can grant the necessary permissions without creating new permission sets.
upvoted 0 times
Beckie
3 months ago
This is a good solution. Applying the principle of least privilege, we can grant the necessary permissions without creating new permission sets.
upvoted 0 times
...
Lashunda
3 months ago
B) No
upvoted 0 times
...
Peggy
4 months ago
A) Yes
upvoted 0 times
...
...
Geraldine
5 months ago
Yes, this solution should work. Inherent permissions allow users to access the table without needing additional permission sets.
upvoted 0 times
Florinda
4 months ago
Yes, this solution should work. Inherent permissions allow users to access the table without needing additional permission sets.
upvoted 0 times
...
Edmond
4 months ago
A) Yes
upvoted 0 times
...
...
Flo
5 months ago
I think the principle of least privilege is important in this case.
upvoted 0 times
...
Gregoria
5 months ago
I agree, adding InherentPermissions = Rl should resolve the issues.
upvoted 0 times
...
Kathrine
5 months ago
Yes, that sounds like a good solution.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77