Question 1 of 3
What sync strategy does the recall sync use on its first run, and over what time window?
AA partial sync covering the last 30 days
BA full sync with a two-year lookback window
CA push-type sync that fetches all records regardless of date
DA full sync covering only the current calendar year
Question 2 of 3
Why is the GetAppointmentNewStatuses method classified as a push type?
ABecause it writes data back to the PMS rather than reading from it
BBecause it can only be called once per day due to API rate limits
CBecause it cannot be filtered by time and must always be fetched in full
DBecause it is only triggered by a webhook from the PMS
Question 3 of 3
In Open Dental Cloud, how are patient accounts populated during the sync flow?
AAccounts are synced independently via a dedicated account RPC method
BAccounts are derived from aging data, since no dedicated account sync exists
CAccounts are written back from Weave Forms during the write-back phase
DAccounts are fetched using a partial sync filtered by last-modified timestamp