PL-400 · Question #97
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…
The correct answer is A. Yes. This solution - enabling change tracking on the relevant entities AND using the Data Export Service - does meet the goal of reducing synchronization time. Change tracking causes Dynamics 365 to maintain a log of only the records that have been inserted, updated, or deleted…
Question
Options
- AYes
- BNo
How the community answered
(19 responses)- A79% (15)
- B21% (4)
Explanation
This solution - enabling change tracking on the relevant entities AND using the Data Export Service - does meet the goal of reducing synchronization time. Change tracking causes Dynamics 365 to maintain a log of only the records that have been inserted, updated, or deleted since the last sync. The Data Export Service reads this change log and pushes only the delta to Azure SQL, avoiding a full-table scan or bulk re-export each day. Together, these two capabilities make large-volume daily syncs significantly faster and more efficient than querying all records every time. This is the correct architectural approach for this scenario, contrasting with the console-application approach in Question 6 which was deemed insufficient.
Community Discussion
No community discussion yet for this question.