Microsoft Dynamics 365: Finance and Operations Apps Developer — Question 57

A company uses Dynamics 365 Finance.

The company deploys a custom table named LoyaltyCustomerTable. The table has a 1:1 relationship with a table named CustTable. Both tables contain a unique field named AccountNum and share the same data. Using event handlers, all edits to CustTable are reflected within LoyaltyCustomerTable.

The LoyaltyCustomerTable data is maintained by using the LoyaltyCustomerTable form. This form selects all data from both LoyaltyCustomerTable and CustTable and displays the records sorted by LoyaltyCustomerTable.AccountNum.

LoyaltyCustomerTable was mistakenly created with no indexes. A significant delay occurs when users open the LoyaltyCustomerTable form.

You need to improve performance by creating an index.

Which method should you use?

Answer options

• A. Create a foreign key relation on LoyaltyCustomerTable with Related Table set to CustTable and Index set to RecId.
• B. Create foreign key relation on CustTable with Related Table set to LoyaltyCustomerTable and Index set to RecId.
• C. Create an index on CustTable for AccountNum.
• D. Create a foreign key relation on LoyaltyCustomerTable with Related Table set to CustTable and Index set to AccountIdx.

Correct answer: A

Explanation

Option A is correct because creating a foreign key relation on LoyaltyCustomerTable with the appropriate index will help optimize data retrieval based on the relationship with CustTable. Options B and D do not directly address the performance issue for LoyaltyCustomerTable, and option C would not improve the performance of the form associated with LoyaltyCustomerTable, which is the main concern.