nerdexam
Microsoft

PL-400 · Question #85

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 B. No. The proposed solution - enabling change tracking and implementing a console application that queries for changes - partially addresses the problem but is insufficient to fully reduce synchronization time for large data volumes. While change tracking in Dynamics 365 does help by…

Submitted by wei.xz· Apr 18, 2026

Question

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 have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. An organization has an Azure SQL Database instance that must be synchronized daily with data from Dynamics 365 Sales. A large amount of data might need to be synchronized on some days. You need to reduce the time required to synchronize data. Solution: Enable change tracking for entities that will be synchronized. Implement a console application that queries for changes. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(30 responses)
  • A
    20% (6)
  • B
    80% (24)

Explanation

The proposed solution - enabling change tracking and implementing a console application that queries for changes - partially addresses the problem but is insufficient to fully reduce synchronization time for large data volumes. While change tracking in Dynamics 365 does help by identifying only the records that have changed since the last sync (avoiding full table scans), a console application alone is not an efficient architecture for bulk, large-scale synchronization. A more appropriate solution would use Azure Data Factory with the Dynamics 365 connector, Azure Synapse Link for Dataverse (formerly Export to Data Lake), or the Dataverse Tabular Data Stream (TDS) endpoint - these handle large data loads with parallelism, retry logic, and scalability that a custom console application cannot reliably provide.

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-400 Practice