You are developing a mobile instant messaging app for a company. The mobile app must meet the following requirements: - Support offline data sync. - Update the latest messages during normal sync…

Question

Options

• ARetrieve records from Offline Data Sync on every call to the PullAsync method.
• BRetrieve records from Offline Data Sync using an Incremental Sync.
• CPush records to Offline Data Sync using an Incremental Sync.
• DReturn the updatedAt column from the Mobile Service Backend and implement sorting by using
• EReturn the updatedAt column from the Mobile Service Backend and implement sorting by the

• A
  14% (5)
• B
  71% (25)
• C
  9% (3)
• D
  6% (2)

Explanation

B: Incremental Sync: the first parameter to the pull operation is a query name that is used only on the client. If you use a non-null query name, the Azure Mobile SDK performs an incremental sync. Each time a pull operation returns a set of results, the latest updatedAt timestamp from that result set is stored in the SDK local system tables. Subsequent pull operations retrieve only records after that timestamp. E (not D): To use incremental sync, your server must return meaningful updatedAt values and must also support sorting by this field. However, since the SDK adds its own sort on the updatedAt field, you cannot use a pull query that has its own orderBy clause. https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-offline-data-sync

No community discussion yet for this question.