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:

Include all records from TableA Header even if no matching record value exists in the linked TableA Line: LeftOuterJoin

Include only matched records from TableB Header: InnerJoin

In SQL and similarly in Business Central when defining table relationships in query objects, the type of join determines how records from one table are combined with records from another table. Here's what each join type means in the context

of the company's requirements:

LeftOuterJoin:

InnerJoin:

By using these join types, the company can ensure that their dataset includes the appropriate records from the document tables and document history tables according to their specified requirements.

Correct Answer:

Specify the value of the post options as Invoice:

Test

Perform calculations and values checking:

Handler

In the context of Microsoft Dynamics 365 Business Central testing, the 'Test' attribute is used to mark a method as a test method. This is where you would specify the action or the behavior you're testing ?in this case, setting the post options

as Invoice. It's within these test methods that you would simulate setting the posting option to "Invoice" programmatically.

For performing calculations and checking values, you would use 'Handler' methods to handle specific business events or conditions that occur within the system, such as before or after posting a document. These handlers can ensure that

calculations are done correctly and that all validation checks pass before the document is posted. The 'Normal' method would be a standard method that could be involved in the posting process, ensuring that all business logic is correctly

applied and that the calculations and value checks are as expected.

In a test codeunit, you would typically have test methods that call these handler and normal methods to verify the business logic in various scenarios, such as posting with different options or checking the results of calculations under different

conditions.

Correct Answer: D

When developing an app for Microsoft AppSource, it is essential to use an object range that is specifically designated by Microsoft to avoid conflicts with other apps and the base application. The correct object range to use is: An object range within the range of 70000000 to 74999999 that is requested from Microsoft (D): This range is reserved for AppSource apps. Developers need to request this range from Microsoft to ensure that the objects used in their extension do not conflict with those used by other extensions or by the base application. Using this reserved range helps maintain the integrity and compatibility of extensions published on AppSource. It's important to note that the other ranges mentioned (A, B, C, and E) are not suitable for apps intended for AppSource. Ranges 50000 to 59999 and 50000 to 99999 are typically reserved for per-tenant customizations or partner solutions, not for distribution on AppSource. The standard range 1 to 49999 is reserved for the base application objects, and using an object range divided by countries (C) is not a standard practice for AppSource apps.

Correct Answer: B

When updating the base application table using a table extension in Microsoft Dynamics 365 Business Central, certain properties of table fields can be modified to meet new requirements, such as regulatory changes. The DecimalPlaces property (B) is one such property that can be adjusted in a table extension. This property determines the number of decimal places that are displayed and stored for decimal fields in the table. Adjusting the DecimalPlaces property can be particularly useful when dealing with financial data and tax calculations that require precision to meet new tax tiers set by a regulator. It's important to note that not all properties can be modified in a table extension; for example, the CalcFormula property (A) cannot be changed as it affects how the field's value is calculated, which could have significant implications on the base application's logic.