This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Use the following questions to check what you learned about change tracking, alternate keys, and the UpsertRequest message.
A developer builds an integration that needs only the Request records that changed since its last synchronization, without re-reading the entire table on every run. Which approach meets this requirement?
Enable change tracking on the Request table and use the Prefer: odata.track-changes header to retrieve and store a delta link.
Query the Request table with a $filter on the modifiedon column compared to the last sync timestamp.
Retrieve every Request record and compare it against a locally cached copy from the previous run.
A vendor's device code is unique only within a single warehouse, not across all of Contoso's warehouses. Which alternate key design on the Device table guarantees uniqueness for this data?
A single-column key on the vendor device code.
The existing GUID primary key, with the vendor device code stored as a regular column.
A composite key that combines the vendor device code and the warehouse code.
An inbound feed sends device availability updates, and the integration code doesn't know in advance whether a given device already exists as a Dataverse record. Which approach avoids a separate retrieve step before deciding whether to create or update the record?
Always send a CreateRequest and handle the resulting error if a matching record already exists.
Send an UpsertRequest with the Target entity identified by its alternate key values.
Send a RetrieveRequest first to check whether the record exists, then send a Create or Update request based on the result.
A nightly synchronization job stops running for longer than the change-tracking expiration window configured in ExpireChangeTrackingInDays for the Request table. What must the client do on its next run?
Resume with the previously stored delta link or data token, since it remains valid.
Disable and re-enable change tracking on the Request table to reset the expiration window.
Perform a new initial synchronization to retrieve a full extract and a fresh token.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?