A field-service app must let technicians complete job forms with no connectivity and sync when they get signal. Design the client side of that, including what happens when the sync conflicts.
Answer it out loud before you open anything. The value of the flags below is in comparing them to what you actually said.
The situation behind the question
Technicians work in basements and rural sites. A job form has a status, notes, parts used and photos. Two technicians occasionally work the same job, and dispatch can also change a job from the office while a technician is offline.
What it is really testing
Whether the candidate treats offline as a durable-queue and conflict problem rather than as a caching problem. The scenario contains a genuine concurrent-write case, so "last write wins" is a decision to be defended rather than a default to be assumed.