Test your understanding. Select the best answer for each question, then submit to see your score.
Question 1 of 3
What is the purpose of the sync-app-support service?
ATo monitor SyncApp health and restart crashed pods
BTo automate the entire SyncApp provisioning flow (validation, data source creation, settings, spin-up) triggered when an office integrates their PMS in WAM
CTo handle write-back operations from the Weave UI to the PMS
DTo store and retrieve SyncApp configuration settings from a central database
Question 2 of 3
When implementing a new PMS integration in sync-app-support, which interface must you implement?
AThe SyncApp Handler interface with methods: Start, Stop, Restart
BThe SyncApp Provisioner interface with methods: Name, Metadata, Provision, Steps
CThe Data Source interface with methods: Create, Delete, Update, Authenticate
DThe PMS Adapter interface with methods: FetchPatients, FetchAppointments, FetchProviders
Question 3 of 3
What is the SyncApp Tag in the data source creation step, and why is it important?
AA human-readable label for identifying the SyncApp in WAM
BThe initial version of SyncApp to spin up — the SyncApp will then auto-update to the latest version on its first check
CA security token used to authenticate the SyncApp with Data Service
DA metadata field that tells ICPA which PMS vendor to route API calls to