Select the best answer for each question then submit to see your score.
Question 1 of 3
How does SyncApp trigger a full sync for an entity?
AA: It deletes all existing records in Data Service and re-fetches everything using the current timestamp
BB: It fetches all records using a date anchor set very far in the past, such as 2-3 years ago
CC: It signals the PMS to push all records to a Weave-managed endpoint
DD: It sets the scheduler interval to zero so the next partial sync covers all time
Question 2 of 3
In the Standard Batch Syncer pipeline, what is the purpose of generating a hash code for each transformed record?
AA: To encrypt the record before it is written to PostgreSQL in Data Service
BB: To determine the scheduler interval for the next sync of that entity
CC: To compare against the previously stored hash and detect whether the record has changed, avoiding unnecessary writes
DD: To assign a unique SourceTenantId to each record before forwarding it to Weave
Question 3 of 3
When debugging an on-prem PMS integration such as Eaglesoft 18 running inside a VM, which tool is used to inspect the SyncApp instance and verify connectivity?
AA: BART, Weave's internal Kubernetes deployment system
BB: The Darren Super Patch manual settings injection tool
CC: RPCs executed against the SyncApp instance
DD: The ICPA proxy dashboard, which throttles and monitors PMS API calls