Microsoft MB-820 Exam Dumps

Correct Answer:

Correct Answer:

Box 1: Permissions = TableData "POS Information" = RMDX

Define permissions on the table. Include Modify (M).

Scenario:

The company requires a codeunit called from a job queue to read the information from the POS terminal APIs.

The POS terminal information must be stored in a table named POS Information, have an ID 50100, and be editable on a page.

Incorrect:

*

Permissions = TableData "POS Information" = rdx

*

Access = Internal

Would be permission to use the code/module.

Note: Access Property

Sets the object accessibility level, which controls whether the object can be used from other code in your module or other modules.

Note: Permissions Property

Sets whether an object has additional permission required to perform some operations on one or more tables. The operations can be to read, insert, modify, and delete data.

Applies to

Codeunit

Table

Request Page

Page

Xml Port

Report

Query

Permission Set

Permission Set Extension

Syntax: Permissions = TableData 1221 = rimd;

Box 2: Procedure readAPI()

Incorrect:

* Procedure readAPI(PosNo: Integer) No mention of PosNo in the scenario.

Note: To declare a local method, start the declaration with local:

local procedure Mymethod();

To declare a global method, omit local:

procedure Mymethod();

Parameters (optional)

A parameter is one or more variables or expressions that are sent to the method through the method call. The parameter provides information to the method, and the method can modify that information. In the method declaration, you place

the parameters in parentheses ().

Reference:

Correct Answer: A

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.