Implement Data Synchronization with Dataverse PL-400 Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A developer is synchronizing data from an external HR system to Dataverse. The external system sends employee records that may be new or updated. The developer wants to use a single message to insert or update records in Dataverse, using the employee number as the unique identifier. What should the developer use?

   • AExecuteMultipleRequest with both Create and Update requests in a single batch.
   • BUpsertRequest with an alternate key defined on the employee number column.
   • CUpdateRequest with a null GUID to let Dataverse generate the primary key.
   • DCreateRequest with a pre-query to check if the record exists.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A developer is building a synchronization job that uses Dataverse change tracking. The job runs every hour and processes changes from the previous run. After processing a batch of changes, the job crashes before it can save the new deltaLink. What is the most appropriate way to handle the next run?

   • ADisable change tracking and perform a full table load to guarantee consistency.
   • BUse the unsaved deltaLink from the crashed run to continue from the exact point of failure.
   • CUse the last successfully saved deltaLink to retrieve changes again, and process the same changes idempotently.
   • DStart a fresh initial sync using a new deltaLink to avoid processing stale changes.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A developer needs to enable change tracking on a custom table named 'Device' in Dataverse. The developer wants to use the SDK to enable change tracking. Which property should the developer set on the EntityMetadata instance?

   • AChangeTrackingEnabled = true
   • BIsChangeTrackingEnabled = true
   • CEnableChangeTracking = true
   • DTrackChanges = true
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A company is designing a bidirectional synchronization between Dataverse and an external CRM. The external CRM uses a 'CustomerID' that is unique. The developer needs to ensure that records created in either system are synchronized to the other without creating duplicates. Which strategy should the developer use?

   • AUse alternate keys on both systems to store the external ID, and use UpsertRequest with the alternate key for writes.
   • BUse change tracking only on Dataverse and push all changes to the external CRM.
   • CUse a single shared GUID as the primary key in both systems.
   • DDisable change tracking and perform full exports in both directions every night.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A developer is designing a synchronization solution that must handle a large volume of records and support offline scenarios. The solution uses change tracking to retrieve changes and UpsertRequest to write them. The developer is concerned about the performance of UpsertRequest when using alternate keys. What is the best way to optimize the write performance?

   • AUse a separate UpsertRequest for each record without batching.
   • BDisable change tracking to reduce overhead.
   • CUse CreateRequest instead of UpsertRequest to avoid key lookup overhead.
   • DUse ExecuteMultipleRequest or ExecuteTransactionRequest to batch multiple UpsertRequest messages in a single call.
   Reveal Solution Discussion Select an answer first