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

Questions 6–10

1. 6expert · hard

   A developer is building a synchronization job that uses change tracking to sync Dataverse 'contact' records to an external CRM. The job runs every 15 minutes. The external CRM has a rate limit of 100 requests per minute. The developer notices that the job sometimes exceeds the rate limit when processing a large batch of changes. What is the best way to handle this constraint?

   • AUse UpsertRequest to combine multiple changes into a single request.
   • BImplement a retry policy with exponential backoff and honor the Retry-After header from the external CRM.
   • CIncrease the change tracking page size to retrieve more records per request.
   • DDisable change tracking and perform a full sync once per day to reduce request frequency.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which of the following is a valid use case for defining an alternate key on a Dataverse table?

   • AMatching records from an external system that uses a customer number
   • BStoring large binary data such as images
   • CControlling which users can view a record
   • DDefining a relationship between two tables
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A developer is designing a synchronization strategy for a large Dataverse environment with over 10 million records. The requirement is to sync changes to an external data lake every hour. The developer is considering using change tracking with a deltaLink. What is the most important consideration to avoid data loss?

   • AUse a large page size to retrieve all changes in a single request.
   • BDisable change tracking and use a full export every hour to guarantee consistency.
   • CUse UpsertRequest for every record in the environment every hour.
   • DStore the deltaLink in a durable location and handle the 410 Gone error by re-initializing the sync.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What is the purpose of defining an alternate key on a Dataverse table?

   • ATo allow multiple records to share the same value in a column
   • BTo provide a unique business identifier that can be used instead of the primary key
   • CTo encrypt sensitive columns in the table
   • DTo improve query performance on frequently used columns
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A company is designing a bidirectional synchronization between its on-premises ERP and Dataverse. The ERP uses a natural key (CustomerCode) and does not store Dataverse GUIDs. The sync must handle high volume, minimize data transfer, and avoid duplicate records. The team is considering a solution that uses change tracking, alternate keys, and UpsertRequest. Which aspect of the design is most critical to ensure the sync does not miss changes when the ERP is offline for several hours?

   • ADefine the alternate key on CustomerCode and use UpsertRequest for all records.
   • BUse a full initial sync each time the ERP reconnects.
   • CPersist the change tracking token after each successful batch and use it to resume.
   • DRun the sync every minute to minimize the window of missed changes.
   Reveal Solution Discussion Select an answer first