Q:

You need to optimize the data model for a new feature that tracks international trade agreements.

You need to ensure that the table design supports efficient data retrieval and storage. It must still maintain referential integrity between trade agreements and participating countries.

What should you do? Each correct answer presents part of the solution. Choose three.

 

Wrong: Remove all indices from the trade agreements table to reduce storage overhead.

Wrong: Increase the size of string fields in the countries table to accommodate longer country names.

Wrong: Duplicate country data in both the trade agreements and countries tables for faster access.

Adding a relation with delete actions ensures referential integrity and cascading deletes or updates where appropriate. Creating an index on frequently accessed fields improves query performance without unnecessary storage overhead. Implementing field groups optimizes data retrieval for user interfaces and reports. Increasing the size of string fields unnecessarily does not contribute to efficiency and may increase storage costs. Removing all indices would degrade performance. Duplicating data in multiple tables violates normalization principles and can lead to data inconsistencies.

Create tables and table fields - Training | Microsoft Learn

Add fields to tables through extension - Finance & Operations | Dynamics 365 | Microsoft Learn