Practice: Syncing Two Record Systems and Sharing Data Without
Solve a two-system record synchronization problem from the Palantir FDSE decomposition round, sharing only the data a vendor needs. Separate source identity from employee identity, assign field ownership to each system, and design imports and mirror writes that handle duplicate, late and conflicting deliveries with revision checks and safe retries. Make inactivity and bad input visible, and enforce a server-side vendor projection that discloses only permitted fields.
We'll cover the following...
- What must you resolve about H17 and W62?
- What is the smallest useful plan for E41?
- Which records make field ownership executable?
- What survives duplicate, late and conflicting deliveries?
- What changes after inactivity or uninterpretable input?
- What may V3 receive for P501?
- Can your revised plan defend a denied P502 request?
HR record H17 says department Operations, active true, HR revision 10; Workplace record W62 says room R2, readiness pending, Workplace revision 7. A reviewed mapping links both records to employee E41. Your task is to make subsequent changes predictable while giving a preparation vendor only the information needed for assigned work.
A candidate-report compilation lists synchronizing two employee record systems as a decomposition theme; that supports this practice theme, rather than its constraints or a prediction of your interview.
What must you resolve about H17 and W62?
Before reading the answer packet, write up to four consequential questions about the operational user, identity, field authority and recipient needs. For each, state what an answer could change in your plan.
Pause and write, then use this answer packet:
User: A workplace coordinator needs reliable room-preparation work for one office.
Authority: HR owns display name, department and active status. Workplace owns room and readiness. Each system also stores mirrors of the other system’s fields.
Identity: ...